4 ms·
My main concern which made me switch back to NextJS was debugging with useful error messages, given the Svelte system does different things; when I played with
by bionhoward 5y ago
My main concern which made me switch back to NextJS was debugging with useful error messages, given the Svelte system does different things; when I played with it for a graph visualization thing, it hadn’t had all the edge cases found so I felt like getting into bigger project I had trouble finding where my bugs were when I was using Svelte;
that was at least a year ago so if those issues are resolved then it’s a compelling framework to play with for sure, I like how Svelte feels just like HTML/CSS/JS and Svelte performance could be superior to React if certain claims are true about disappearing framework vs virtual dom. Not sure how SSR impacts those performance pros and cons between Next and Svelte so it’d be interesting to find published and updated latency benchmark numbers for both.
React hooks can be different to reason about though because of immutable state patterns vs two-way data binding; I actually really like the hooks and immutability ideas, but two way binding is much more elegant and simple sometimes. Edit: also those don’t have to be exclusive
- StefanWestfal 5y agoGood point, maybe this is an issue in bigger projects. I don't have experience here yet. Regarding debugging and errors, it feels that less code and so much features being already included, and thus out of "one hand", seem to reduce bugs for me. Having a complier could also open doors to catch bugs at compile time.