4 ms·
We've switched to Svelte for new projects at work, from React. It feels like a significant improvement, especially regarding unnecessary complexity and verbosit
by erokar 6y ago
We've switched to Svelte for new projects at work, from React. It feels like a significant improvement, especially regarding unnecessary complexity and verbosity. The UI component libraries for Svelte are still lacking in maturity, that's the one drawback I can think of.
- vanderZwan 6y ago> It feels like a significant improvement, especially regarding unnecessary complexity and verbosity. > The UI component libraries for Svelte are still lacking in maturity The typical counterargument usually made at this point would be "those two points are related" (to paraphrase Bjarne Stroustrup: "every ship gets barnacles as it ages"). So let's anticipate that: do you have any reasons to believe that Svelte will avoid adding accidental complexity/verbosity to it as it/the surrounding ecosystem matures, and if so, how do you think that will be mitigated?
- throwaway894345 6y ago> to paraphrase Bjarne Stroustrup: "every ship gets barnacles as it ages" Enough time has passed to firmly conclude that Stroustrup was wrong on that point. Other languages have withstood the test of time better than C++<11 and C++>=11 has dramatically improved the language by copying features from those other languages. C++'s issues were poor design choices, not simply some "maturity" force that causes a language to accumulate incoherent features.
- TehShrike 6y ago> do you have any reasons to believe that Svelte will avoid adding accidental complexity/verbosity The maintainers are very paranoid about adding complexity, and are not being funded by large corporations paying for features to get added.