I usually just do a folder for a component if it gets to big, but I posted 
those links because the Svelte version uses the exact same structure: 
<https://github.com/vuesomedev/todomvc-svelte/tree/master/src/components> and 
thus it's a bit more of apples-to-apples example. I personally wouldn't do 
things like this, but then I never needed fancy state management like Redux 
with React.

> I'm not critisising React, used it for couple of years, it's a good and 
> robust framework. And it's possible to use React in a way that's short and 
> compact. Yet, it won't be as compact and clean as Svelte.

I get you, and Svelte is great. Personally I'm more productive in React, for 
some reason JSX is really easy for me to parse and enjoying to work with. This 
of course won't be the same for everbody and that's okay! But for Karax 
specifically I'd be careful with trying to go for a Svelte-ish route and 
changing the way Karax does things suddenly, if you think there is nice way 
Karax can learn from Svelte, then a RFC of sorts could be useful.

Reply via email to