3 ms·

What would be your motivation to pick React? I'd say the ecosystem. You're really hitting a point there with the animations. Framer is cool and all, but animat

What would be your motivation to pick React? I'd say the ecosystem. You're really hitting a point there with the animations. Framer is cool and all, but animating exits still sucks.

pcthrowaway 3y ago
I think mainly the tooling is much better in React. I can get by with "sort-of typescript" for Svelte, but it's a bit annoying that I can't get VS code to provide type hinting everywhere, and to also enforce "no-implicit-any". In smaller projects I'm probably not touching files I've completely forgotten all the time, so it's not too much of a problem I can deal with the fact that the tailwind extension intellisense might not work in Svelte (or it didn't last time I tried it); for smaller Svelte projects I'm happier to use component-scoped styling 90% of the time. At that point I probably haven't typed the same combination of styles enough times that I want to share them across the project. When the project grows, these become much more of a pain. I end up with lots of small to medium sized components, and I want to compose these along with mixins defined elsewhere (utility functions that can be pulled into them, etc). At that point I really want Typescript to be as strict as possible, and I want the Intellisense on tailwind partial class names. I'm sure there are plenty of other similar tooling issues that I'm forgetting right now. React also has many more libraries, as you said, including the wonderful Tanstack query (I know there's a Svelte engine now, though I haven't tried it yet) But the actual framework is so much easier in Svelte, enough so that I'd almost always choose it for smaller projects. React has its pain points even at medium scale, whereas with Svelte they really hit me harder as the project gets bigger. So it probably comes down to what I'm doing. But yeah, I'm still going to reach for Svelte the majority of the time

What would be your motivation to pick React? I'd say the ecosystem. You're really hitting a point there with the animations. Framer is cool and all, but animating exits still sucks.

pcthrowaway 3y ago

I think mainly the tooling is much better in React. I can get by with "sort-of typescript" for Svelte, but it's a bit annoying that I can't get VS code to provide type hinting everywhere, and to also enforce "no-implicit-any". In smaller projects I'm probably not touching files I've completely forgotten all the time, so it's not too much of a problem I can deal with the fact that the tailwind extension intellisense might not work in Svelte (or it didn't last time I tried it); for smaller Svelte projects I'm happier to use component-scoped styling 90% of the time. At that point I probably haven't typed the same combination of styles enough times that I want to share them across the project. When the project grows, these become much more of a pain. I end up with lots of small to medium sized components, and I want to compose these along with mixins defined elsewhere (utility functions that can be pulled into them, etc). At that point I really want Typescript to be as strict as possible, and I want the Intellisense on tailwind partial class names. I'm sure there are plenty of other similar tooling issues that I'm forgetting right now. React also has many more libraries, as you said, including the wonderful Tanstack query (I know there's a Svelte engine now, though I haven't tried it yet) But the actual framework is so much easier in Svelte, enough so that I'd almost always choose it for smaller projects. React has its pain points even at medium scale, whereas with Svelte they really hit me harder as the project gets bigger. So it probably comes down to what I'm doing. But yeah, I'm still going to reach for Svelte the majority of the time