In my recent blog post, I shared my experience upgrading my portfolio site to the stable v1 release of the Kiru framework. The transition represented a major shift in my development workflow, as the framework moved away from a React-like hooks API toward a new reactive paradigm centered on signals, computed values, and closure-based components. I highlighted how this update simplifies state management by allowing component bodies to run only once, and I noted specific technical adjustments I had to make, such as handling the now-reactive path parameters with .value. While the change required some refactoring, I found that it significantly cleaned up my codebase and improved performance, leading me to highly recommend the upgrade to other Kiru users.