4 ms·
The eternal question: why do you hate JavaScript?
- Mountain_Skies 5y agoOn the flip side: Why are some baffled by hatred of JavaScript, believing it to be random and unfounded?
- Jugurtha 5y agoIt may be due to the fact more people have opinions about something than first hand experience. "Python doesn't scale", "JavaScript sucks, what do you expect from something that was hacked together in a week", "The answer in one word: Scala", "Statically typed languages are the answer". Working on a machine learning platform, part of what I do is to talk with people who use the variety of tools involved. I interact with many people who say bad things about Jupyter notebooks, and I get into a conversation asking them about the reasons they're unsatisfied and what they've experienced. Most people will admit they don't really actually use Jupyter notebooks. Many people just parroting for a variety of reasons: to belong to something, to take the safe way and "build an audience" by repeating something they've read a lot. One reason I blocked probably the biggest data science blog from my search results is this. Mandatory disclaimer for people who'll understand this as saying that either JavaScript, Python, or Jupyter notebooks are perfect. It's not saying this.
- theamk 5y agoNot my experience - people usually start hating things after first experience with them... because if you never used it, hating it just stupid. So for example with Jupyter notebook, the easiest way to reuse code is copy-paste. Sure, you can open library py file in a separate window and keep reloading, but this is pretty painful and most tutorials don’t cover this aspect. So if I were an engineer trying to directly use code from jupyter notebooks? I’d hate them a lot. (Fwiw I personally don’t care, and even use them occasionally, great for demos!] And that answers why JavaScript gets so much hate: because it is forced in the face of pretty much everyone. Example: First time I encountered it, I was working on this nice C++ codebase.. and then I had to debug visualizer in JS and apparently global “array” class had some methods with generic unprefixed names injected that made buttons! And then it broke, because a different library also injected generic unprefixed names into global array class. This was the flagrant abstraction violation, and the stupidest decision I have ever seen in my programming carrier. In C, this problem was discovered and fixed decades ago, and those JS people just ignored those lessons from the past. And don’t get me started on non-existing error handling. So no, no parroting, just an outsider seeing the bad decisions with the fresh eyes.