I like the no-build approach, but I'm afraid the problem is bigger.
For years, a new framework has appeared every week (it feels like every day) that promises to solve all problems with the latest buzzwords.
The mere fact that this happens shows that today's web development suffers from a plethora of unsolved fundamental problems.
Instead of fighting a problem with workarounds (and thus new problems), it would be nice if the community would sit down and ask itself how we can create a future that makes frameworks obsolete.
Sometimes I get the impression that we have more of a social problem than a technical one. If browser vendors, developers, managers, corporations, startups, freelancers and everyone else involved sat down at a table and talked constructively with each other, things would certainly be possible that would save everyone a lot of work, or am I wrong?
40-1; I use Rust for almost everything.
For smaller projects I always test SPA approaches (with Rust and WASM of course), but for long-lasting important projects I would always go for boring, reliable, server-side rendering. Other client-side things remain optional (keyword “Progressive Enhancement”).
Theoretically, there are no real limitations, as you can do everything with `wasm-binden` that you can do with JS/TS.
However, if you expect ready-made UI components or want to integrate any JS library, you will have to invest some time.
2) Yes and no, it really depends on your requirements. We have already created two customer projects with it and are very satisfied (although I personally still prefer the Elm approach to the reactive approach).
For years, a new framework has appeared every week (it feels like every day) that promises to solve all problems with the latest buzzwords. The mere fact that this happens shows that today's web development suffers from a plethora of unsolved fundamental problems.
Instead of fighting a problem with workarounds (and thus new problems), it would be nice if the community would sit down and ask itself how we can create a future that makes frameworks obsolete.
Sometimes I get the impression that we have more of a social problem than a technical one. If browser vendors, developers, managers, corporations, startups, freelancers and everyone else involved sat down at a table and talked constructively with each other, things would certainly be possible that would save everyone a lot of work, or am I wrong?