Not only is the code last updated in 2018, that code is so unreadable that I think the person who wrote that would even overengineer a Svelte solution like that. It even still uses `React.createClass` in places, haha. Contrast that with the Svelte code written by the maker himself, of course that's gonna look amazing!
Here is a more recent TodoMVC compare( still doesn't use React's functional components and hooks): <https://github.com/vuesomedev/todomvc-react> and <https://github.com/vuesomedev/todomvc-svelte> Now I'd say the Svelte code is still cleaner to read here, but with functional components and hooks, I'd say the difference is neglible. Of course there is a lot of really really bad React, especially in 2018 apparently, code out there, and I think Svelte is doing great work, but maybe what I didn't convey well enough is, that for Karax to grow, I'd rather see a focus on different parts(easier ways to contribute, docs), rather than following $webframework. Of course these things can be done separately but the community is not that big (yet). I like <https://github.com/solidjs/solid> and no VDOM solutions, but how I see it, is that choosing your frontend framework is a tradeoff game. Do I trade in the ecosystem of React for Svelte's productivity? Or do I go full Nim and have a language to rule them all, but most likely have to do a lot from scratch without any documentation? Karax has to compete with so much that it's a hard road. (this is all just simply how I think about it)
