The stuff like Flash, Java applets and Silverlight it eventually replaced were arguably even worse. There’s a legitimate need to run client-side code at times, IMHO the mistake was making it so permissive by default. Blaming the language for the bad browser security model is kind of throwing away the baby with the bathwater.
Considering the community we are on, I assumed the criticism was more about the privacy problems surrounding the engine and browser security model than the quality of the language itself. If that was the intent, I mean… Yeah, its weak typing is a fucking mess.
That’s fair. I just assume most people who reflexively insult JS are like that usually because they’ve written something in it, rather than having dealt with the many vulnerabilities and annoyances browsers have made possible with it
It desperately needs interface types if we ever hope to make it a serious contender for general purpose web development. The IO overhead of having to interface with JS to use any web API is itself pretty slow, and is limiting a lot of usecases.
Ngl if you just don’t support the majority of modern browser features, it’s not hard to make a new browser.
Not as hard, I agree but reimplementing just CSS sounds like a very special level of hell.
But…that’s just a setting on all the browsers
W. JavaScript was a mistake.
The stuff like Flash, Java applets and Silverlight it eventually replaced were arguably even worse. There’s a legitimate need to run client-side code at times, IMHO the mistake was making it so permissive by default. Blaming the language for the bad browser security model is kind of throwing away the baby with the bathwater.
Browser permissiveness didn’t create implicit type coercion.
Considering the community we are on, I assumed the criticism was more about the privacy problems surrounding the engine and browser security model than the quality of the language itself. If that was the intent, I mean… Yeah, its weak typing is a fucking mess.
That’s fair. I just assume most people who reflexively insult JS are like that usually because they’ve written something in it, rather than having dealt with the many vulnerabilities and annoyances browsers have made possible with it
WASM is a better way to run code client-side, and has the benefit of not being a terribly slow, untyped mess 😌
It desperately needs interface types if we ever hope to make it a serious contender for general purpose web development. The IO overhead of having to interface with JS to use any web API is itself pretty slow, and is limiting a lot of usecases.
this is why i will write my blog from scratch with absolutely no JS or code execution of any kind
deleted by creator