Javascript has a number of issues that make static analysis hard. It also has implicit conversions and other oddities which mean that code often keeps on trucking after a programmer error, rather than failing where the initial problem was.
These problems were solved in other languages decades ago - which is why many developers "hate" switching to Javascript. It's coding on a tight-rope without a safety net.
The meme: "You're just a hater, because you don't know how to use it", is a joke. Javascript has issues, hopefully they can be fixed, but fixing them without breaking compatibility is difficult. Being honest about Javascript's flaws doesn't make you a "hater".
For the record my first JS project was Netscape 2 compatible. So I'm pretty sure I know how to use it.
How diferent browsers implement the language? How diferent sucky the communication with the DOM is? How verbose it is? How there are 4 ways to do anything and 3 of them are wrong and the one correct way has changed according to time?
I guess nothing.
So it's horrible for its most common use case.
It's type system is also a total joke. Typeof returns a string? Array.isArray()? ===? Just wow.
In general, programming tools get worse as they near the UI layer. It's like a passive aggressive way for programmers to say they hate writing user focused things. At least that's my armchair theory about why UI libraries, the DOM, etc. are so badly designed and hard to use compared with systems software or algorithmic code.
Like other posters in this thread, I remember back to the "browser wars" between IE and Netscape. There is a gigantic thick book on my bookshelf called Dynamic HTML and it had notations on what methods, elements, etc. worked in what browser. It was much more painful back then to use JavaScript.
It is a tool and necessary for web work. You can go crazy with it though and write entire apps using just JS, not sure that would be recommended though, seems hard to maintain.
-They want to create a class by calling class.
-If they call 'this', it should be always from Object context.
....
There are many cases which Javascript ruin their concepts from them. Although few years ago I switched to JS from Java, I infact not a fan of new ES6 introductions like class, extends, let.
There's absolutely no way you can code and dodging JS.
thanks for the links elviejo
Dart is just clean. Javascript is just the unfortunate mess we are stuck with.
And to answer your question: I love it, it's like a virus: everywhere.
i've learned from experience that "people" who use generalized statements like those will never be the superstars that make real shit happen. they're far too insecure, attacking perceived weaknesses of the tools used rather than the work output and very often, results achieved. elitism by attacking toolsets is insecurity driven by lacking experience and ultimately, lack of skill, nothing more. who the fuck cares what tools are used? did the project get results?
that's the lowest common denominator.
I've seen plenty of spaghetti javascript.
My gripe about javascript is in part that all the browsers support it in significantly different ways, and that a great deal of JS is written by web designers who really don't understand computer programming.
My reason is that I am very good at debugging, and so have the idea I could score a lot of consulting contracts by offering to fix broken javascript code.