Fair enough. I do agree that JS-based libraries, frameworks, and tools tend to have bad docs and questionable API designs, compared to equivalents that I've used in other languages. There is some cultural issue there that I don't understand.
But... this is an embedded scripting environment! You aren't using any of that stuff.
Yes and no. You're definitely less exposed to JS ecosystem, but it's often the same issue with available examples, code snippets, docs.
I've similarly bad experience with for eg. plugins for VS Code. I wanted to add more supported syntax to org-mode plug in, at which point I found that their test suite is messed up.
Of course none of this is inherently fault of JS as a language, but current development culture around it promotes use of lots of silver tape, which makes me nervous, when I have to use anything JS-based.
Comments
Fair enough. I do agree that JS-based libraries, frameworks, and tools tend to have bad docs and questionable API designs, compared to equivalents that I've used in other languages. There is some cultural issue there that I don't understand.
But... this is an embedded scripting environment! You aren't using any of that stuff.
Yes and no. You're definitely less exposed to JS ecosystem, but it's often the same issue with available examples, code snippets, docs.
I've similarly bad experience with for eg. plugins for VS Code. I wanted to add more supported syntax to org-mode plug in, at which point I found that their test suite is messed up.
Of course none of this is inherently fault of JS as a language, but current development culture around it promotes use of lots of silver tape, which makes me nervous, when I have to use anything JS-based.