
I'm working on my dream frontend framework, and recently released 1.0 π
Check it out here: Kiru I also wrote a little article I wrote about how I landed here: Making Web Development Easy Again - rausten.dev Kiru actually pivoted a little while ago from maintaining a React-like api with hooks etc to going all-in with signals. A small example: function Counter () { const count = signal ( 0 ) return () => ( < button onclick = { () => count . value ++ } > Click Me! { count } </ button > ) } State, lifecycle hooks and variables are created in a setup scope. If your component doesn't create any local state, it can just return JSX. This removes the inherent complexity of interpreting or mutating state across renders like how we do with React. I really think this component model makes a lot of sense and naturally leads to better decisions about how to build complex apps. Let me know what you think!
Continue reading on Dev.to Webdev
Opens in a new tab

