I’m still amazed that NPM bent over backwards just to please the (extremely sleazy) Kik app and willingly screwed over one of their best package contributors.
It’s really not a great situation with package management in Js land, and having two predatory companies own major tools and package repositories certainly doesn’t help things.
Definitely, it’s sadly hard to avoid entirely with it being the main driver for the web. Stuff like ClojureScript is nice since it’s pretty much its own ecosystem and you can opt into Js stuff if you really need to.
Kotlin can also compile into JS and is more familiar to most JS developers. More options are good as a general rule and we’re starting to see more players in this space.
You know it’s bad when you’re using a lower level bytecode or native language to compile to a high level interpreted language just to avoid said high level language.
Honestly, production JS is so obfuscated and processed and hard to read as an outsider that it’s essentially bytecode. Reverse engineering JS in a webpage is a common security CTF challenge.
I’m still amazed that NPM bent over backwards just to please the (extremely sleazy) Kik app and willingly screwed over one of their best package contributors.
Oh wait, no I’m not!
NPM is basically hot garbage
And now that it’s owned by Microshaft, it’s a raging dumpster fire that’s apart of the broader landfill fire.
Honestly, between NPM owned by MS and Yarn owned by Facebook, JavaScript straight up has no good package manager option.
It’s really not a great situation with package management in Js land, and having two predatory companies own major tools and package repositories certainly doesn’t help things.
All the more reason to not use JS. Being a terrible language is one thing, having a terrible ecosystem is worse.
Definitely, it’s sadly hard to avoid entirely with it being the main driver for the web. Stuff like ClojureScript is nice since it’s pretty much its own ecosystem and you can opt into Js stuff if you really need to.
Kotlin can also compile into JS and is more familiar to most JS developers. More options are good as a general rule and we’re starting to see more players in this space.
You know it’s bad when you’re using a lower level bytecode or native language to compile to a high level interpreted language just to avoid said high level language.
Yeah, it’s kind of an amusing situation. I literally just treat Js as bytecode nowadays. I haven’t had to write a line of it in years.
Honestly, production JS is so obfuscated and processed and hard to read as an outsider that it’s essentially bytecode. Reverse engineering JS in a webpage is a common security CTF challenge.