4 ms·

Re: Sapper -> Sveltekit, you might say the same thing for React Router users who adopted Reach-router, back to react-router and are now on remix-router or next.

Re: Sapper -> Sveltekit, you might say the same thing for React Router users who adopted Reach-router, back to react-router and are now on remix-router or next.js router. Also I found it weird that you mention Evan You WRT vite as a counter to why Rich might be up against stronger devs, but Rich made rollup, which was foundational to Vite's bundling.

preommr 4y ago
I don't doubt Rich Harris' skills as a developper. But project governance is very different from have strong technical skills. Things like communication, prioritizing features important for the community, dealing with idiots way beyond when it stops becoming fun, gathering money, writing good documentation, etc. Rollup is cool, but it's a very different beast from a f/e framework. For a lot of projects, migrating from rollup to webpack might be a few hours or a week. Migrating from svelte to react, is months if not many man-years.
- davidjfelix 4y ago
  What's wrong with svelte's documentation or the community interaction that's happening around svelete? My point is that you've seemingly taken points away from Rich for the same reasons you're giving Evan You validity. Migrating between react and vue would take probably the same amount of time -- I'm not really sure what your point is here. My point is that you've unfairly discounted Svelte on the same standards you're raising vue.
- fsociety999 4y ago
  > Migrating from svelte to react, is months if not many man-years. I’m not sure what your argument is here, but I’m pretty sure you have it backwards. The fact that it might take a while to migrate a svelte project to react is not because of poor documentation or tooling or communication or anything like that. It’s because so many things work out of the box in svelte, and to do the same things in react would take tons of boilerplate or third party libraries. Some things may not even be possible to port, at least not easily. This doesn’t show that svelte is bad though. It shows that react lacks functionality and is more difficult to use.

preommr 4y ago

I don't doubt Rich Harris' skills as a developper. But project governance is very different from have strong technical skills. Things like communication, prioritizing features important for the community, dealing with idiots way beyond when it stops becoming fun, gathering money, writing good documentation, etc. Rollup is cool, but it's a very different beast from a f/e framework. For a lot of projects, migrating from rollup to webpack might be a few hours or a week. Migrating from svelte to react, is months if not many man-years.

davidjfelix 4y ago
What's wrong with svelte's documentation or the community interaction that's happening around svelete? My point is that you've seemingly taken points away from Rich for the same reasons you're giving Evan You validity. Migrating between react and vue would take probably the same amount of time -- I'm not really sure what your point is here. My point is that you've unfairly discounted Svelte on the same standards you're raising vue.
fsociety999 4y ago
> Migrating from svelte to react, is months if not many man-years. I’m not sure what your argument is here, but I’m pretty sure you have it backwards. The fact that it might take a while to migrate a svelte project to react is not because of poor documentation or tooling or communication or anything like that. It’s because so many things work out of the box in svelte, and to do the same things in react would take tons of boilerplate or third party libraries. Some things may not even be possible to port, at least not easily. This doesn’t show that svelte is bad though. It shows that react lacks functionality and is more difficult to use.