wild_egg

Very similar to how LLMs work but at much higher frequency

I did similar and gave ours a 15 year old laptop that boots straight into DOSBox with a dozen old games. They aren't dopamine injectors so he naturally chooses to do something else after 30-60 minutes. Great contrast to iPad or YouTube that he can be glued to for 10 hours straight if we let him.

> but without static types

So add static types.

https://github.com/coalton-lang/coalton

Very cool. Also a bit surprising — two of my matches are people I know IRL.

> This section is for you: https://overreacted.io/jsx-over-the-wire/#html-ssi-and-cgi

Strawmanning the alternative as CGI with shell scripts really makes the entire post that much weaker.

> nobody refers to except in these arguments.

Be the change, maybe? People use REST like this because people write articles like this which uses REST this way.

Deja vu with this blog. Another overengineered abstraction recreating things that already exist.

Misunderstanding REST only to reinvent it in a more complex way. If your API speaks JSON, it's not REST unless/until you jump through all of these hoops to build a hypermedia client on top of it to translate the bespoke JSON into something meaningful.

Everyone ignores the "hypermedia constraint" part of REST and then has to work crazy magic to make up for it.

Instead, have your backend respond with HTML and you get everything else out of the box for free with a real REST interface.

Something about that mp3 actually feels disturbing. Is it normal for that type of model to attempt communication that way?

Struggling to find the words but the synthetic voice directly addressing the prompt is really surreal feeling.

Who said you were selling something?

My point is that the entire approach is architecturally far more complex than is suitable for the vast majority of projects. You have influence and people will make real world decisions to choose unnecessary complexity because of this article.

Why do 150 lines when 10 lines of PHP is functionally equivalent to the user? The user doesn't care about your execution model. They just want some information or to submit a form. Adopting an RSC-like technology makes development more complicated and take longer.

If you're building Figma or something then sure, go nuts with the complicated things. The tradeoff probably makes sense.

For the other 99% of us, this model just gets in the way.

The need to wax philosophical really shows how complex and overengineered RSC is compared to solutions from other ecosystems that are just as effective but far simpler to work with and understand.

The APIs have docs. The agent can go read them and build against them.

Many countries have this in various forms and it works out fine. Generally illegal to interfere with the press and a good way to lose the next election

Sounds like you're assuming all software is SaaS that requires the provider to keep it available?

Software used to all be lifetime purchases by providing you with the actual program. If you bought a copy of WordPerfect in the 90s it will still work fine today even though no one is offering it anymore.

Thanks for sharing. I was planning on building something like this in April after hitting too many issues with Jina and Tavily but it looks like you've already done the hard work!

What does this mean? I have no idea what niche you're even working in

At the end of the day, most consumer software boils down to simple CRUD apps with various skins. Sure people have been able to make those for years but it was still time consuming to wrangle the no code tools. Now people can do it in an hour or two with simple English instructions.

I've been working on exactly this. Great to know there's some demand for it.

It's now my daily driver for web access. It monitors for content I'm interested in (that's how I found your comment), handles all my searches and feeds, can dynamically adapt its interface, and is working on integrations to submit content for me so that I don't have to leave that interface to write these replies.

Hoping to release it early March but I'm a bit stuck on how to position it. I'm not a marketer and I think it'll just get drowned in the sea of "agent" slop.

Having a full-on buffer between yourself and the internet is a breath of fresh air but I have no idea how I would have found such a thing if I hadn't made it.

Maybe a curator or a bouncer or something. Open to suggestions if anyone has some.

Thanks for this. I've a passing interest in those older expert-level interfaces and input buffering wasn't on my radar but is completely vital. I remember relying heavily on that functionality back in the day and yet it's non-existent in most modern interfaces.

> It is not good for "and these other related elements need to update"

That seems a bit backwards, no? Why can't those other elements manage their own updates? You can have the server respond with an `HX-Trigger` header to dispatch an event and any elements that care about that event can listen for it. Far simpler than trying to coordinate surgical DOM updates in a single HTTP request.

Events form the backbone of the browser environment and leaning into that model makes a lot of things much easier

You can do that with HTMX through events and hx-trigger but it just sounds like HTMX isn't the right tool for what you're trying to do. I've seen a lot of instances of people trying to use HTMX to replace react/vue/etc. and not understanding that they're trying to solve for very different things.

HTMX highly encourages client side scripting for dynamic updates if that's what your UI needs. It's very pro-JavaScript even though a lot of people get confused and try to use it to fully replace JavaScript

A FOSS alternative to Rewind that works on both MacOS and Linux would be a dream come true tbh. Thanks for working on this, I'll be trying it out sometime next week

Look like very nice tech but unfortunately the operational overhead of postgres is too high for my use case. Will keep it in mind for future postgres-backed projects though

I've been using DuckDB similarly and loving the simplicity. What sort of latency are you seeing with your setup? I'm hitting 300ms to query against 10M vectors and could see that becoming a bottleneck if going into the hundreds of millions.

How much are you willing to pay though? Full privacy means powerful enough hardware to do everything else on the list on-device and _quickly_. I don't know that most people have the budget for that

Ladybird is pretty far from approachable for most folks at this point but one day will hopefully be a great option in that space

> My only issue with Go is getting the old bootstrap C version compiled for a new port

Genuinely curious — how often have you had to do that? What platforms are you running that Node has binaries for but Go doesn't?

I've been writing Go for 12 years and it's never taken more than a couple minutes to download and install the latest version.

Neither of those examples apply to or impact the bulk of HTMX projects. I've worked on a bunch of these and have never seen `makeFragment` used in the wild. The `hx-on` attribute is similarly rare — I've only used it twice myself and it took longer to open my IDE than to update those to the new syntax.

> So your brain must've just ignored the code diffs above when responding, because it likes htmlx so much.

It's less about whether someone likes HTMX or not and more has to do with none of those points in the upgrade guide being relevant to, or impacting, the author or most other people.

That's Go's out-of-the-box experience. Maybe you're looking for something to scaffold projects? There are plenty around, I've been using https://gowebly.org

If they really are that complex, then use react for them. One of the biggest issues I have always had with react proponents is the "well if I need react for X then I might as well build the whole thing in react."

Islands Architecture is really not complicated. The bulk of your app can be very simple hypermedia exchanges and components and when you need a really fancy widget, load it and mount it where it needs to be.

Seems not right for the comments here to be empty but I don't have much to say other than this looks incredibly nice. Hope I have an excuse to use it at some point.

Thanks for sharing!

I've been using zig's toolchain in CGo projects for a couple years now and cross compilation _just works_. Maybe there are libraries it doesn't handle well but so far all of my use cases have been covered perfectly.