curiouskoala

I have a slightly different approach on my blog https://ezeugo.dev where my entire thought process (edits, original ideas, rewrites are a part of the actual essay). By making the event stream part of the product, it shows the process and output as one.

The project seems super interesting and I've been following since the creator went on an effect podcast I listened to. My only gripe/concern is the fact that the docs are so glaringly AI (likely claude) generated which is something I've come to not expect from technical documentation writing specifically. All in all though, the verbosity tradeoff for explicit design choice here is the right one and I think it does better than elm by remaining in javascript land rather than building a nicer abstraction layer on top that often needs to reach in to do interesting things with the web apis.