the reason i hate javascript is that t is not strictly typed. so a value can be boolean, null, false, undefined, empty strin and who knows that else. the reason i hate css is that sometimes some rules work in some places under certain circumstances in certain browsers. meaning, the ENTIRE web front-end is unpredictable in behavior and visualisation. in short, front-end is an epitome of the uncertainty principle and it in direct opposition of how computers work.
Yes, but you also hate Typescript and you probably also hate using wasm bridges so you're shit out of luck.
@UncleIroh i don't hate typescript, i just never used it. it's like coffeescript or scss which are merely syntactic sugar intermediaries trying to make things easier but in the end the product is the same. as for wasm, if it would allow interaction with DOM, we could use backend languages on frontend and be done with javascritp for good. but they purposely made it no so.
Typescript's a very usable superset of js. It just makes most of the arcane js bullshit that everyone hates go away. I don't understand how/why js devs aren't using it by default at this point.
As for wasm, yeah, I can see how not having direct DOM access is a deal-breaker. | just asked AI about this and it seems that the proposal of wasm Interface Types is the most promising solution.
Anecdotally, the pairing I'm seeing more of out in the wild is rust/typescript.
@UncleIroh TS use is going down. even at microsoft that came out with it.
That's not what my searches say at all. Nor does it have anything to do with my point.
Also, in order for your claim to make any meaningful sense you would have to look at those numbers alongside js since ts/js have to co-evolve.
What happens when I do that?
As of 2025, the trend in JavaScript vs TypeScript usage is shifting towards increased adoption of TypeScript, particularly for large-scale and enterprise applications.
