It's what you consider central in a framework. For React, JS/TS is king. All markup and all CSS is subsumed in JS/TS.
In Svelte, HTML/CSS is king, with the bare minimum of JS/TS necessary for any given task.
With that in mind, of course React tends toward type definitions. Also explains why Svelte tends toward markup-oriented definitions.
Re:Thoughts on Svelte
by robertoandred on Monday March 27, 2023 @02:13PM
(#35330169)
React doesn’t care where or how you have your CSS.
Right, because it has very poor component-level isolation for styling. React basically punted on CSS, and that's truly not a blessing in its favor.
Re:Thoughts on Svelte
by can_center_divs on Wednesday March 29, 2023 @02:23AM
(#35353347)
Doesn't it? I can't put a class name on a HTML Element and then style the said class inside the same file. It seems to me that it cares more about where you have it, than Svelte
The main one for me is typing props for a component feels extremely wack. In react I have a function, that function takes a type, I export that type and can import that type. In svelte I'm exporting the props individually? It's annoying to get the type declarations in one spot and make that easy to import for other components to use as intermediate typing. This is one of those things that I didn't even think twice about until my project reached a medium size and had multiple developers building out different portions -- it's inconvenient to scale and none of the workarounds feel good.