Re:Reading and Writing a File in Javascript for Win 8 Apps
by PommeDeTerre on Wednesday December 26, 2012 @12:11AM
(#4968228)
JavaScript had a bad reputation far before Node.js was introduced. It was blatantly inferior to begin with, and it hasn't really improved since, but for whatever reason people don't recognize the inferiority like they used to.
While its prototype-based nature may have some theoretical benefits, in practice it has obviously been disastrous. I suspect that it is the cause of more terrible code than JavaScript's numerous other serious problems.
In order to make something truly usable out of JavaScript, you essentially have to discard all of its core features and syntax. At that point, one should ask why there's even any point in bothering. If JavaScript basically needs to be twisted into something resembling C++, Java, C#, Ruby or Python to be truly useful, then why not just go with those languages instead?
What on this green Earth does that even mean? JavaScript and Silverlight could hardly be less related other than they're both available in some browsers. Timeframe, etc, don't support your [conspiracy] theory.
JS is different in that it's a prototype-based language. That and the sometimes errant recent love-obsession with Node.JS has given JS an undeserved and often non-specific bad reputation.