Not sure if that attention will end up on a different project or just chilling 😅 I've honestly been getting to a point after 7 years of OSS where I've either have too much to do or don't know what to do

Happy to hear that, I should really get onto publishing them!

Thank you, I tried to be understanding in case it was for translation reasons or something but at the end it got really difficult 😅

Hopefully it will improve with github.com/preactjs/.gi... as we can then just close the issue and warn the user

If you ever want to explore the depth of options hooks, preact signals/preact compat/preact hooks and prefresh (fast-refresh) all utilize them heavily and enable really cool stuff

I remember another cool experiment like this in github.com/jviide/flowp...

I doubt it 😅 also more referring to not doing as much platform-y and OSS things which was my initial goal for 2025. Creating something that benefits users directly

Your help is tremendously appreciated, you're a champ!

Congratulations Matt, that's an exciting role!

No offense towards the talk but the way it was conveyed it felt disingenuous, they used a really weird data model which if you leverage signals normally you should never arrive at. That being said, without the repository being public I won't attach any value to it.

Congratz, sounds like an exciting opportunity! Good luck