> actual typed languages
lol, those type systems are garbage comparing to typescript, if you even understand what a type system is, it's not the same as making toy hierarchies in OOP
> Rust compilers and interact with your DOM
> pick the right hoe for the job
More evident of you knowing nothing of what you're talking about. There is a push for Rust to do this kind of thing, but it's far fom the right tool for the job.
Rust's focus is memory safety, not expresiveness (eventhough it can be), so it's never the best tool for the job of making applications, on the DOM or otherwise. You can try to do it but it's best fit for system programming.
The best programming language to make application on the DOM is Java/C#
/s
It’s alright dude, I’m not even hating. Don’t let a type system destroy the style of a language though.
Nothing makes me lol more than?.a?.conditional? null check in a ‘type safe’ language. Just stop it, use C# Blazor to write your Frontends and call it a day. JS is not (your) tool for the job (because oh god, what if you don’t know a param is a string, lord have mercy, how did the web even make it this far without this type safety brilliance?).
Enough.
> Nothing makes me lol more than?.a?.conditional? null check in a ‘type safe’ language. Just stop it, use C#
And get null pointer exception? No one forces you to be stringent on typescript, use a nullable type if you want, but saying TS is crap because it's actually better than C# at static analysis?
Edit: is it so much to ask to not want to write code that looks like gibberish? I don’t care what the benefits are, it looks like gibberish code. Can type safety be accomplished without gibberish code?
I think in Java it goes something like this:
Function (String s, int num)
Ok, I’m on board. You Typescript bastards are writing gibberish code and I don’t care who disagrees.
The most important part of all that code is the part in the prisma calls, which would handle all the caching and request logic.
The rest is literally just making sure you name your stuff correctly and render it.
If you want actual type safety for your large client-side app, use rust/wasm. If your client side app is small, why do any of this?
The belief in WASM as a method to build client-facing software is an amusing self own. There is literally no production examples because it is not production ready for dom-heavy stuff.