Why you might choose Svelte over React (according to Rich Harris)

if i'm like starting a new project like why should i start it with spelt versus react like today the short answer is you'll ship faster that's what we believe and there's caveats to that obviously if you're someone who is already experienced with react then it's going to take you a bit to learn how to use felt but overall the the argument for spell is that because of the design decisions that we're taking like the foundational design decisions that we have this compiler-centric mentality where we're essentially designing a component language as opposed to trying to express

user interface semantics in a language which is fundamentally ill suited to them namely javascript because of that you can express concepts much more concisely and idiomatically in a stock component than you can using react and a lot of people will just disagree with me vehemently on that but my observation has been that for example if you convert a react component to a fault component it will be about 40 smaller in terms of the bytes of code that you have to write

and that has real consequences obviously how fast you can write the component because you're physically writing less stuff but it's also more readable less code is more readable than more code and also maintainable it is more maintaining easier to change too right easier to change i've heard you often say something that i personally take with me as like my new mantra which is like optimized for change you know and yeah less code is easier to change