In general I like Svelte and SvelteKit although there's 3 problems I don't fully like:
1) The getter trap - if you forget to export hooks via getters you don't get reactivity and it's not easy to figure out (Svelte)
2) The async data fetching - for example fetching data async is currently coupled to views which it shouldn't be - was frustrating a lot (SvelteKit)
3) That reactivity system is not runtime only (Svelte)
I am also not a fan of adding these new things like remote functions - most of apps need multiple frontends and this coupling isn't needed. This will be fad same as GraphQL
There are no signals, proxies, or decorators, or any compilation. You just use plain data. Though the trade-off is that you have to call render() yourself. I prefer it that way though.
machiaweliczny · · focus · HN ↗
1) The getter trap - if you forget to export hooks via getters you don't get reactivity and it's not easy to figure out (Svelte)
2) The async data fetching - for example fetching data async is currently coupled to views which it shouldn't be - was frustrating a lot (SvelteKit)
3) That reactivity system is not runtime only (Svelte)
I am also not a fan of adding these new things like remote functions - most of apps need multiple frontends and this coupling isn't needed. This will be fad same as GraphQL
EricFrost · · focus · HN ↗
<a href="https://eric-frost.github.io/solarite/" rel="nofollow">https://eric-frost.github.io/solarite/
There are no signals, proxies, or decorators, or any compilation. You just use plain data. Though the trade-off is that you have to call render() yourself. I prefer it that way though.