5 ms·

> I'd use it again for personal projects, maybe not for large company projects if I was the architect. Questions about large projects always arise when talking

> I'd use it again for personal projects, maybe not for large company projects if I was the architect. Questions about large projects always arise when talking about Svelte. Did you / would you use it and why not? I would certainly NOT suggest using Svelte on enterprise projects. Why not? Because other people don’t do it, and that means that it is very likely that there are no (not many anyway ) experienced Svelte devs that are willing to work at/for some large company. React and Angular are safe bets in THAT space. On the other hand, would I use it for personal projects or in a startup - absolutely. It's simple, it is fast and it is fun to work with.

nailer 4y ago
> React and Angular are safe bets in THAT space. But they weren't always. And a lot of people that 'know' React don't feel entirety comfortable using React because of complexity - ever seen someone want to know how to store a variable and watched the life drain out their eyes as they read a Dan Abramov essay on what true reactivity means?
- ttfkam 4y ago
  React never was truly reactive. Even according to its devs. https://legacy.reactjs.org/docs/design-principles.html#scheduling https://legacy.reactjs.org/docs/design-principles.html#sched...
TehShrike 4y ago
> Because other people don’t do it This isn't true, I build enterprise software with Svelte (and have for years), and I know others who do too. We just don't contribute to the technology hype cycle.
ttfkam 4y ago
With all due respect, the majority of large React projects I've encountered devolved into non-uniform big balls of mud that only the original authors can (sometimes) understand. React's "non-opinionated" stance constantly leads to a non-opinionated code base without a strong technical lead with a very firm hand. When talking about other frameworks (sorry, "libraries"), React folks should really avoid throwing stones from their glass house. I'm not fan of Angular by any means, but I totally respect how opinionated it is and how that translates out to development teams in the wild.

nailer 4y ago

> React and Angular are safe bets in THAT space. But they weren't always. And a lot of people that 'know' React don't feel entirety comfortable using React because of complexity - ever seen someone want to know how to store a variable and watched the life drain out their eyes as they read a Dan Abramov essay on what true reactivity means?

ttfkam 4y ago
React never was truly reactive. Even according to its devs. https://legacy.reactjs.org/docs/design-principles.html#scheduling https://legacy.reactjs.org/docs/design-principles.html#sched...

TehShrike 4y ago

> Because other people don’t do it This isn't true, I build enterprise software with Svelte (and have for years), and I know others who do too. We just don't contribute to the technology hype cycle.

ttfkam 4y ago

With all due respect, the majority of large React projects I've encountered devolved into non-uniform big balls of mud that only the original authors can (sometimes) understand. React's "non-opinionated" stance constantly leads to a non-opinionated code base without a strong technical lead with a very firm hand. When talking about other frameworks (sorry, "libraries"), React folks should really avoid throwing stones from their glass house. I'm not fan of Angular by any means, but I totally respect how opinionated it is and how that translates out to development teams in the wild.