But it isn't for everyone, as I already said there are people who will always like the react model no matter what comes out because they come maybe more from a programming background first, in programming you build an application by composing functions together that do a certain job. In react you use functions and each one returns a piece of UI and its logic which makes sense and people build UIs that ways easier.
@mellunar The React example is not a valid component ;) Maybe you should write an actual simple component as you are pointing to difference between state management only. This is more fair to compare
<script>letname='world';</script><h1>Hello {name}!</h1><buttonon:click={()=> name = "Hi"}>click me</button>
A javascript function body is your script tag in Svelte the javascript return is your svelte file for markup, some people like programming some like XML style.
we got hooked by the underlying philosophy that creating interactive UI doesn't need to be a chore :D
But it isn't for everyone, as I already said there are people who will always like the react model no matter what comes out because they come maybe more from a programming background first, in programming you build an application by composing functions together that do a certain job. In react you use functions and each one returns a piece of UI and its logic which makes sense and people build UIs that ways easier.
@mellunar The React example is not a valid component ;) Maybe you should write an actual simple component as you are pointing to difference between state management only. This is more fair to compare
vs
A javascript function body is your script tag in Svelte the javascript return is your svelte file for markup, some people like programming some like XML style.
Implying writing HTML isn't programming
Writing jsx is.
Im glad you feel superior for making your life harder 🤣
I'm sorry for you that your brain can't grasp it.