-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port frontend to Svelte 5 and SvelteKit #524
Conversation
Look, I'm still torn between:
Both are nice. But I think Svelte is more mature and will probably be faster and easier optimizable (especially since WASM for the browser isn't really easily splittable into smaller chunks) And I feel like there are a lot of open-source frontend devs that like Svelte and would rather contribute to a Svelte codebase than to a Vue or Rust codebase. So it's also about appealing to potential contributors that help me fix up the mess that is the frontend (because, surprise surprise, I'm not a frontend dev) |
Leptos and Dioxus are still ostensibly in the R&D stage, so Svelte gets a +1 from me. I say that even though we’re using Leptos in one of my own projects, but that’s because we specifically needed a WASM-based frontend, so it is itself a R&D project. Leptos is aiming for a stable release of its major new 0.7 version around July, so that could be a good time for another look if the itch for complete oxidizing doesn’t subside 😆 |
Handing the progress on this over to @vesdev (at least partially). I'll merge their progress once they tell me they are ready. |
54ed269
to
190c5ba
Compare
+1 for Leptos personally :P |
190c5ba
to
1fbce89
Compare
5d41499
to
7e20d69
Compare
31010e3
to
5500f03
Compare
Should make things faster and hopefully more maintainable through simpler APIs.
Also SvelteKit is a nice DX improvement over raw Vue (and Nuxt).
Closes #443