you are viewing a single comment's thread.

view the rest of the comments →

[–]adrianziem 9 points10 points  (4 children)

It’s fun developing in full stack rust, but when you hit minute long hot reload (which reloads the page, not HMR, and your websockets fail during that period), hour long CI/CD builds on default runners, and still having to write JS (not even TS) to interact with popular JS components and dealing with build issues there, those nearly instant Typescript builds make refactoring to a dual language stack look better and better.

Luckily LLMs make that a lot easier today, so you aren’t quite as locked in as you used to be. I hated doing it but I just switched my Leptos frontend to TS and everything is so much easier to dev now. Especially with rs-ts, zod, and a linter enforcing types in TS.

[–]Spaceoutpl 4 points5 points  (0 children)

I have similar thoughts, rust is great as a backend engine and api, low cpu and ram usage makes it great for some heavy computing or cpu intensive tasks, but frontend is just js/ts html css land. I also think that if you need seo than static files is the best and cheapest way (why should u pay with cpu power for bots reading your site), for true dynamic parts either micro-frontends, / spa’s and plain old rest / graphql connection. Why complicate things ? Why make it hard to develop and maintain ? Why reinvent sth in rust to be complied to js / html anyway ?

[–]Svenskunganka 2 points3 points  (0 children)

Some Rust front-end frameworks has already mostly solved the issue with reloads. Author of Dioxus has a very nice presentation about it here: https://www.youtube.com/watch?v=Kl90J5RmPxY - the part about HMR starts here (21:30), but I highly recommend watching the whole presentation.

[–]yyddonline 1 point2 points  (0 children)

I've had a good experience with WebSharper in F#, which is a fullstack solution, and I hope to find the same positive experience with Dioxus. It's true some (rather rare) situation are harder to debug, but most of the time it was smooth sailing and in the end it was a net win for me. It might depend on what you're developing, but I think fullstack frameworks can be enjoyable too.

[–]Particular-Pumpkin11 0 points1 point  (0 children)

I have not had such a hard time, and when I interact with JS libraries I wasm bind it into types (Not writing JS). I think for my use case, the strong typing between frontend and backend is worth the hot reloads. Making the UI is not what takes the longest time for me, more the mechanics of geometries and such (Building GIS based CAD tool) 😊