@janriemer I watched it yesterday. A very good documentary!
I watched it while migrating some JavaScript to TypeScript. Suddenly, my scripts were a bit more sane!
I made a transition for frontends with these stages:
No JS!
Maybe I have to use JS somstimes, but keep it minimal. Still I hated my life
TypeScript makes this mess a bit more sane. It still sucks because its basement is fragile, but I don't see a better alternative for some interactivity in the web.
@janriemer Don't get me wrong, WASM is very promising with Rust, but it is not there yet for my small use cases.
Sure, for web games and similar computing intensive stuff you should use WASM. Even Web UIs like the web backend of egui. But for simple but interactive plots for example, nope. A JS/TS library is much easier and even more lightweight.
I think WASM is great for logic heavy stuff (not only compute-heavy). But for interactivity, like you've said, JS/TS is a great fit.
I've used WASM to build a transpiler, but haven't used it yet to build the entire frontend. I'd like to do something with leptos someday, but I can imagine it being somewhat "heavy" (compared to JS/TS).
@janriemer@mo8it so was Java Webstart during the Sun Microsystems era. “Write Once, Run Anywhere”. Then Microsoft took offense to Java, embraced and extended it so it wasn’t compatible anymore, Sun lost the battle and was acquired be Oracle, and Java was relegated to the server. The rest is history.
@janriemer@mo8it It's never exactly the same for every incarnation of "web enabled applications". Webstart missed on standardization, but also adoption. If you look one level of abstraction back, the web browser is an application that allows others to run their business logic within it. That concept has been through iterations.
It will happen again when the followup to WASM comes around.
Also... arguing? Just thought we were discussing technology similarities.
Add comment