this post was submitted on 02 Apr 2024
13 points (100.0% liked)
JavaScript
2323 readers
4 users here now
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay glad I'm not insane. I gave up trying to learn JS because of that.
The problem is that browsers all decided to solve problems differently, then nodejs came along with ideas that browsers couldn't implement easily (modules for example). To get around that, people wrote "polyfills" but each polyfill did it differently again. So, javascript builders were introduced that automatically inserted polyfills or rewrote javascript code to work on the server and in the browser and they had different solutions.
Of course browsers work differently and have different features, so libraries specialised in exploiting those differences came up and became popular.
Now in an effort to reduce differences, the "best" solutions (aka the most widely used which of course doesn't mean best) are being integrated into the language. Promises, modules, String functions, classes, typing, etc.
It was a grand mess long ago and it seems to continue to be that way.
CC BY-NC-SA 4.0
Jesus fucking christ...sounds difficult enough. I've literally had an easier time learning Mandarin.
I'd rather learn mandarin too than get up to speed with JS 😂
Ha. Like I said, there's a reason I straight up quit trying to learn JS. I see other devs working in it and I'm just over here like "what the fuck is that sorcery?"
@SatouKazuma @onlinepersona
Just read The Good Parts. No really, There's a book called JavaScript: The Good Parts and its still the foundational text of the language.
Thanks for sharing!