211–213 of 213 posts
I'm using Svelte/Sveltekit for a project with about 80 pages (as the designer conceives them -- there are repeated patterns of course... there might be 30-40 sveltekit pages, though some are fairly complex.) It's been great. I have no experience with Vue, but I'd rather not work more with react.
Earlier quoted context omitted.
>I imagine most folks who love React syntax have Stockholm Syndrome at this point. And I'd imagine that most folks who are advocating for Svelte never had to build up a startup before. If everything was done for performance, then python or ruby wouldn't be used as web server languages today, and yet python and ruby web servers comprise of a significant amount of webservers. And besides, most performance improvements…
Re-read my comment. I was not talking about app performance, though Svelte is indeed lighter and faster for various reasons. I made the analogy to assembly vs C. It's not about raw speed. Many APIs and (frankly) hacks have been added to React that developers have learned over the course of years. APIs and hacks that simply aren't necessary for Svelte. I totally agree that the community behind React is absolutely mass…
I don't agree that they will match React's community and environment in the near future, if at all.
Earlier quoted context omitted.
I think you've missed something fundamental. Imagine you're using a spreadsheet app. You put data into a column. Then in another column you write a formula referencing the first column. Then you write a sum formula to put it all together. Oops! One number is wrong in the first column, so you update it, and everything updates automatically. No muss. No fuss. This is the model that Svelte works in BY DEFAULT. The compi…
>I imagine most folks who love React syntax have Stockholm Syndrome at this point. And I'd imagine that most folks who are advocating for Svelte never had to build up a startup before. If everything was done for performance, then python or ruby wouldn't be used as web server languages today, and yet python and ruby web servers comprise of a significant amount of webservers. And besides, most performance improvements…
>Svelte is a great choice for personal projects, but extremely impractical for a startup.
> What about the hiring pool?
> Svelte for the web client is fine, but now you have to manage a different team for the mobile client.
These are interesting assertions and run contrary to my experience. I work for a successful startup and our front-end team uses Svelte. We've had nothing but success. We run a production-grade mobile app (Cordova) on old low-powered client-provided devices including RF guns (Android 5 to 9) with multiple thousands of concurrent users in stores/logistics warehouses, and a web app running on desktop (Chrome/Firefox/Safari). And, every front-end developer we have (including myself) learned Svelte on-the-job within a few weeks.