prokopton

I checked out before getting to that. He even wrote his own HTML variant called EHTML.

https://e-html.org

Well played. You got me to visit your version of the thing you complained about. :clapping-emoji:

It’s been a minute since someone ranted about frontend frameworks. Take a shot.

Most likely it'll try to rewrite the whole world's CSS and get the custom properties wrong.

I bought the first version for far less. I couldn’t believe how much they wanted this time around.

On social media?

Now direct the teens here instead of TikTok.

We bring back Geocities and use the Net like it’s the mid 90s again. No social media required.

I remember being greatly annoyed you couldn’t skip the train rides.

Can hardware became more obsolete?

Adam always did say best practices don’t work.

Always happy to see a Tailwind/no-Tailwind flame war.

I sell stuff on Mercari a lot and people buying through Buyee are great.

I was going to do something like this but turns out it was my baby the whole time.

Is every video about being arrested in Japan sponsored by SquareSpace?

The real crime is adding fade ins on scroll for a blog post.

The problem is long-running projects. Projects are too large in scope. They lasts for months to a year with nothing being delivered. Meetings don’t fix that.

Great for me in Japan.

If I had a nickel for every time Htmx popped up on HN…

I asked Claude’s opinion and it disagreed. :)

Claude’s response:

The article’s central tension is real - Burke went from skeptic to believer by building four increasingly complex apps in rapid succession using Opus 4.5. But his evidence also reveals the limits of that belief.

Notice what he actually built: Windows utilities, a screen recorder, and two Firebase-backed CRUD apps for his wife’s business. These are real applications solving real problems, but they’re also the kinds of projects where you can throw away the code if something goes wrong. When he says “I don’t know how the code works” and “I’m maybe 80% confident these applications are bulletproof,” he’s admitting the core problem with the “AI replaces developers” narrative.

That 80% confidence matters. In your Splink work, you’re the sole frontend developer - you can’t deploy code you’re 80% confident about. You need to understand the implications of your architectural decisions, know where the edge cases are, and maintain the system when requirements change. Burke’s building throwaway prototypes for his wife’s yard sign business. You’re building production software that other people depend on.

His “LLM-first code” philosophy is interesting but backwards. He’s optimizing for AI regeneration rather than human maintenance because he assumes the AI will always be there to fix problems. But AI can’t tell you why a decision was made six months ago when business requirements shift. It can’t explain the constraints that led to a particular architecture. And it definitely can’t navigate political and organizational context when stakeholders disagree about priorities.

The Firebase examples are telling - he keeps emphasizing how well Opus knows the Firebase CLI, as if that proves general capability. But Firebase is extremely well-documented, widely-discussed training data. Try that same experiment with your company’s internal API or a niche library with poor documentation. The model won’t be nearly as capable.

What Burke actually demonstrated is that Opus 4.5 is an excellent pair programmer for prototyping with well-known tools. That’s legitimately valuable. But “pair programmer for prototyping” isn’t the same as “replacing developers.” It’s augmenting someone who already knows how to build software and can evaluate whether the generated code is good.

The most revealing line is at the end: “Just make sure you know where your API keys are.” He’s nervous about security because he doesn’t understand the code. That nervousness is appropriate - it’s the signal that tells you when you’ve crossed from useful tool into dangerous territory.

We age gate other things that are genuinely useful but can be harmful when used incorrectly or with malice.

Given how much trouble you can cause with an Internet connection, I’m surprised this hasn’t happened already.

The egg is canon. Joker sings this version in the BtAS Christmas episode.

https://youtu.be/DpV9f4Tv8kA?feature=shared

Svelte does not allow that.

htmx hasn’t had the piss taken out of it enough.

I’ve been doing ssr for so long I can’t fathom why you’d build a table using JS.

Rich Harris of Svelte often mentions Knockout when talking about Svelte’s signals.

Hey lets you mute a thread.

The $1 hotdogs at Riverfront Stadium were a lot better than the $7 dogs at Great American Ballpark.

I see it as a negative. Too many games are lost because a reliever gives up a couple fly ball outs and the Manfred Man comes round to score. I’d rather see ties than these fake wins.

I think Steve would’ve packed it in and retired if he was still around today.

Client-side validation is a progressive enhancement. You always have server-side validation. The validation in the browser exists to provide additional feedback that lets users have realtime feedback about their input.