| Not my problem, is it? I have to use the same tools as the rest of my team and those tools are as fickle as a teenager's mood. There are ways around those problems but nobody from the core team even attempted it (one example: have a stable set of sub-commands that get translated to now-modified-in-next-version internal APIs; is that really so hard? almost every commercial dev has to do it). But no, let's throw the devs under the bus every time we change our minds. See, that's why a lot of people hate the JS ecosystem, and that's why this perception will not change anytime soon. All languages have idiosyncrasies. I'd be an idiot to hate on JS in particular because literally all languages I ever used have strange and weird deficiencies. But that's not it. The ecosystem and the tooling (and for some languages, like Erlang/Elixir, the runtime is also included) make all the difference to novices or casual dippers. If that experience is bad, then the JS ecosystem will remain the same old meme of youngsters experimenting at the expense of everybody else like it has been viewed for 6+ years now. --- Don't think I am blaming you for anything. I just ranted and vented. A lot of devs lack the insight to be able to look from the outside and say "hey, if I was coming here for the first time I'd be puzzled by this" -- and that grows to be a big problem when enough time has passed. |