Sorry, you’re the one who is misunderstanding.
Richard Kenneth Eng

Sorry about that, I didn’t see they regarded it as a framework as well. There’s a blurry line between what’s simply part of the runtime implementation and what’s extra for most environments of other languages (e.g the String object in a lot of languages). Regardless, your point about JavaScript being misunderstood is simply wrong. If everyone shared the opinion you have then it would be absurd that so many large companies use it. Unfortunately the JavaScript community sees the language as an end-all-be-all of programming. In reality there’s some middle ground that neither side is seeing here. JavaScript does have some great parts to it. It’s lambda system is great and it’s object literal notation makes for some very expressive programming structures. The inspiration for JSON is modeled after some of the really great parts of JavaScript. There are also a lot of really awful parts of JavaScript. Implied globals are messy for beginning programmers and the typeof functionality is bad at best. I could go on and on about why JavaScript has broken parts. But regardless I would still argue that it has a lot of great uses, especially for the web. Would I make my personal site on top of Express? That seems like a mistake for what I expect out of a personal site. Would I use Node.js as an engine to push information through websockets? Absolutely, the event driven model is exactly what I want for that. In all, the JavaScript community and those learning JavaScript often don’t pay their due diligence when considering the languages limitations, but the language is by no means inherently broken.

Like what you read? Give Josh McGrath a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.