6 ms·
As I am reading this, my reaction is "Don't let perfect be the enemy of good"
by hsileng 10y ago
As I am reading this, my reaction is "Don't let perfect be the enemy of good"
- noir_lord 10y agoWhich would be fine if you consider JavaScript good, I don't, it's at best passable if you avoid most of the land mines which is an art in and of itself and that's just the language, if you include the ecosystem it's pretty much all landmines.
- talmand 10y agoSo, if I take your favorite language and somehow manage to cause its ecosystem to get as bad as you claim Javascript's is, does that mean your favorite language is now bad?
- emodendroket 10y agoI think it would, yes.
- talmand 10y agoThat's really sad.
- emodendroket 10y agoWhy? No matter how great the language itself is it's a small part of what you actually end up needing to spend your time working with.
- talmand 10y agoIt's sad because that's judging a language based on external things that don't directly relate to the language itself. It's like blaming tools for the misuse of the tools instead of the people actually misusing the tools.
- emodendroket 10y agoI mean, I'm not holding Brendan Eich personally responsible for the toolchain or anything, but it's not pleasant to work in a language whose ecosystem sucks.
- talmand 10y agoI work in Javascript every day, its ecosystem has very little influence on its usage in my job. I guess it varies from job-to-job.
- horrido 10y agoBut why did the ecosystem get out of hand so easily? Because the sloppiness of the language encouraged it or made it easy to abuse it. JavaScript's ecosystem is notoriously bad in this respect (cf. with Java or Python or Ruby).
- talmand 10y agoI totally disagree with that, but that's just my opinion.