|
|
|
|
|
by skydhash
1315 days ago
|
|
No real standard library. You have the web API or the Node API to work with, and both are inconsistent. The language is very permissive, making it not only easy to shoot yourself in the foot, but in the head as well. There is no easy way to say that your code is semantically correct because JS will allow it to digest anything. So, unless you do thorough review, bad code can easily get through. Dependency hell if you're using NPM. I'd be happy if the community was focusing on implementing some kind of default set of libraries, instead of adding syntactic sugar now and then on top of JS. I remember switching from Java to Kotlin, and the collection API was a real pleasure to work with. But in JS, everyone wants to use their set of libraries. Creating a starter project will get you hundreds of dependencies that you can never vet. |
|
"The language is very permissive, making it not only easy to shoot yourself in the foot, but in the head as well. "
But I am actually not aware of much footguns of the language itself.
That is, if you stick with "the good parts" (even though I share not all the views from the book).
" Creating a starter project will get you hundreds of dependencies that you can never vet."
And it is possible to write clean vanilla js, or stick to limited frameworks. You have to maintain strict discipline though. And nowdays I would use typescript for a new project.