What? If you wanted to make snapchat more successful then there wouldn't be a medium at which your snaps would go through. A one way encrypted app would send the picture to one party. I wouldnt expect the nsa not to be able to see them... at least in time. I made snap-wall.asmallgrin.com and check out /send.html for some fun.
I think the question should be what is it that you're trying to develop? Then we can answer why or why not a particular language or technology would be good or bad.
node.js is probably the most fun.. if i "had to" write some crappy "web app", it'll most likely be in php. because it's fast, easy, whatever. if i want to have fun doing it, i'll make it in node.js.
what i won't do is tell you about all the crappy java toolkits i use on the weekends and tell you about how awesome comicon or whatever was this past year.
Don't worry about it, I got used to occasional trolling on HN. Basically if you are not talking about the newest hottest community approved thing or you have a slightly different opinion than the HN standard you get down voted. Making which programming language is the best for web applications sound like "node.js is the silver bullet of web apps, it also cures cancer and aids at the same time" is laughable. I enlisted several technical details why Java (besides Erlang and Go) is the best for scalable web applications while the other guy was just "java sucks node.js rocks". If I get down voted, it tells more about the people reading this site than anything else.
My advice is to treat downvotes as editorial feedback in regard to the quality of your writing.
Yes, down votes can express disagreement. More often they represent a misunderstanding - rewriting a post can fix this - or they represent a conflict with community guidelines/standards - rewriting can also fix this. Sometimes the best edits are deletions.
It's the tone, particularly the opening line that is likely to cause downvoting of your post. It's demeaning and PHP trolling and unsubstantiated, and therefore, poorly written for HN. The technical discussion which follows, though fine, can't fix it.
Thanks for the feedback. I still think that if you go the a cooking website and you suggest to people to eat mud you can't expect a serious discussion about the nutrition values in mud as meal. This is called common sense. You don't dry your kid in a microwave, you don't eat dirt, and in certain circles you don't use PHP. This is my opinion and I am not going to change it just because HN editorial stuff does not like it. Hope that help. :)
You use programming languages for the features they provide and the requirements they can accomplish. This is why I called you a joke. Most people can build anything in any language but requirements are what should dictate it.
