Don’t ask me, all these one-line packages are ridiculous, cause greater issues than whatever they solve, and are (part of) the reason why js and it’s ecosystem are not considered seriously by other developers.
Don’t ask me, all these one-line packages are ridiculous, cause greater issues than whatever they solve, and are (part of) the reason why js and it’s ecosystem are not considered seriously by other developers.
Well javascript is the default language of the web, so no surprise it attracts a lot of newbies.
It feels dirty having to add “!g” to every search.
Just for the record, I think you’re conflating git and GitHub. They are not the same thing, even if GH would like you to think so.
Got it, but if you expect people to switch from JS to Rust , you’re going to be disappointed. That’s like asking people who just got their driving license to hop into a fighter jet just because it’s faster. JS is a simple language. Its widespread adoption is not due only to it being ubiquitous, but also because it’s pretty easy to learn. Rust, on the contrary, not so much.
Isn’t DOM manipulation notoriously tedious with WASM? That seems quite a showstopper for most client-side js I’d say.
Exactly, it was pretty useful until ~2015 imho. Then JS got better, and coffeescript did not follow these evolutions.
Imho there’s no reason to change or upgrade if your current setup works and you’re satisfied with it. Keep your money, you’ll see what the market has to offer when you need it.
The best tool is the one you have and are familiar with. That being said, it also depends on the task at hand. There’s no silver bullet, and anyone telling you this or that language is THE best without context is a fool.
You mean coreJS, not standard JS, right? But yes, it’s a sad story.
Useful tool that helped more than once finding the performance bottlenecks in my code.