5 ms·
> Nobody Writes JavaScript Any More This is how "delightful" it is, and is the reason I'm waiting for it to die. Every couple of years we decide on the 'no no
by ghusto 3y ago
> Nobody Writes JavaScript Any More
This is how "delightful" it is, and is the reason I'm waiting for it to die.
Every couple of years we decide on the 'no no, definitely this time we have it all figured out, trust us, just use X' "solution" to the problem of JavaScript. We have the definative 'this is how you do it', until the next one.
- mathgladiator 3y ago> I'm waiting for it to die I'm there with ya, but I wouldn't hold your breath. I'm trying to minimize my JavaScript exposure by using streaming, and it's going well enough with a minimal JavaScript "runtime". However, I still find myself with thorny edge cases like "I need a better date/time picker", "color picker", or a drag and drop calendar planner. I find myself frustrated with the ecosystem, and I'm debating how large the set of exceptions are to my ideology.
- superchroma 3y agoThis. It fucking sucks. I just waded back into it and I hate everything about it. VSCode barely copes, Visual Studio doesn't even try and Rider was the only thing that worked which hasn't helped my mood.
- danielvaughn 3y agoI don't know enough about WASM to know why it can't be exposed directly to the DOM, since in theory the DOM should be a language-agnostic interface. If that were to happen, I think the floodgates would really open on WASM and we'd finally start to see JS die.
- rafark 3y agoExactly what I thought a few months ago. The DOM and the HTTP api (or pretty much all browser APIs for that matter) should be interfaces that can be implemented in WASM code. I have no idea why this hasn’t been proposed let alone implemented. I mean, why give us the ability to use other languages if we can’t implement the (browser) APIs?
- crubier 3y agoIf having access to all browsers API had been a prerequisite to getting WASM on the browser, we’d still be decades away from having that, and we’d still be debating what the APIs should like in WASM. I’m grateful that people went for the pragmatic approach.
- danielvaughn 3y agoSure but what I’m curious about is why? I looked it up after I made my original comment, and it has something to do with the fact that several DOM APIs are specific to JavaScript. I can see why that would be difficult, but not “decades” difficult.
- dwaltrip 3y agoI think this is pretty much all of programming. Or life in general. There’s plenty good and plenty bad. It’s no use fixating on things you can’t change. Focus on what you can do.
- potta_coffee 3y agoJavascript is not going away anytime soon, probably. Personally, I'm waiting for React to die.
- steve_adams_86 3y agoAs much as I love React and it has been a positive part of my career, I'm starting to think there really are better alternatives. Its staying power may just be the sheer number of people supporting its ecosystem and competent enough to build things with it. I'm content to keep working with it, and I'm so familiar with it that for small tasks it's kind of my go-to. If I was building something I wanted to be long-live a future-friendly, I might be hesitant to run with React at this point. To be honest though, I'm not sure what's better than would be a clear contender for having similar staying power. I wouldn't complain if that turned out to be Solid.
- ghusto 3y agoLoL, and so it begins ...
- leptons 3y agoThe only real problem with Javascript is people's lack of understanding of it - and it's not even that difficult.