Lazarus / html dev 2026

Building web apps for fun and profit
Laravel, htmx, hypermedia, livewire, build & bundle optional
Host of hx-pod: Learn htmx through your earholes

[guillaume.ceo @guillaumeceo]

Somewhere along the way, we forgot how to write HTML.

It became a byproduct of frameworks, not the foundation of the web.

Thread 🧵

[Lazarus / html dev 2026 @all__hype]

HTML 4 life

[Howard Lince III @HowardL3]

The wildest change I've had with the exposure of AI to general users is that I see a lot more HTML files flying around.

[Lazarus / html dev 2026 @all__hype]

@ibuildthecloud I promise I won’t harass you if you aren’t interested, but check your dms if you’d like to talk hypermedia!

[Lazarus / html dev 2026 @all__hype]

@ibuildthecloud @kentcdodds @businesinsider @HughLangley If you’re on an iPhone, click the little icon in front of the url and then click “show reader” for the full article

[htmx.org / CEO of Bad Flags (same thing) @htmx_org]

speakers are up at https://t.co/Eri7HqKKdz

we are still looking for sponsors: we have multiple speakers coming from abroad this year and flying isn't cheap!

plz trick your boss into giving us money by saying our conference is very important 🥹

[Lazarus / html dev 2026 @all__hype]

@htmx_org Elaborate way to get @WarrenInTheBuff to delete his tweets

[Lazarus / html dev 2026 @all__hype]

Code Independence

[htmx.org / CEO of Bad Flags (same thing) @htmx_org]

vibependencies

go through your dependencies, figure out which ones are deep and which are shallow

tear out the shallow ones w/just the code you need, potential big savings on transitive deps, often removes layers of unneeded abstraction for your use case, etc

it's a thing

[Lazarus / html dev 2026 @all__hype]

@htmx_org would that it were so easy

[Lazarus / html dev 2026 @all__hype]

This allegation of unauthorized access or “hacking” is factually unsupported. The actions in question were undertaken with the explicit knowledge, authorization, and consent of the relevant party. Evidence of such authorization is documented in the referenced video recording.

[htmx.org / CEO of Bad Flags (same thing) @htmx_org]

sorry folks:

https://t.co/Mc59S037hf

[Lazarus / html dev 2026 @all__hype]

for anyone interested in the TRUTH, the full Pull Request and video has been posted publicly and without any admission of guilt or fault
https://t.co/4YB3r33B0Q

[Lazarus / html dev 2026 @all__hype]

@code_chimp Yeah I am a big fan of markdown and markup. Any mark is good with me

[Lazarus / html dev 2026 @all__hype]

Haven’t tried this yet but interesting read. html hierarchy is powerful

[Thariq @trq212]

https://t.co/MXt5XS4xBX

[Karri Saarinen @karrisaarinen]

What if we built better software, not just more of it?

[Lazarus / html dev 2026 @all__hype]

(This is specifically a question YOu, not me)

[Lazarus / html dev 2026 @all__hype]

Is it a mistake to curse your child with your sense of humor?

[Lazarus / html dev 2026 @all__hype]

Is it a mistake to curse your child with your sense of humor?

[Lazarus / html dev 2026 @all__hype]

@htmleverything The only practical thing I have found that helps:
Time. Building up robustness with each fix creates a more solid base. Eventually you can mostly rely on your processes to alert you, and trust that if they are t alerting you it’s actually fine. Becomes more true over the years

[Lazarus / html dev 2026 @all__hype]

reminder that the opposite of DRY is WET and it is actually very good and will save your ass many times over your career

[Raul Junco @RaulJuncoV]

Every time I see a team celebrating their new "shared module," I remember this lesson.

Reuse is a dangerous form of coupling.

They found the same logic in two places and did what good engineers do: put it in one place and called it a win. Clean, responsible, textbook.

Six months later, someone needs to change it.

Suddenly, a small update for one team's requirements breaks three services, blocks two releases, and triggers an emergency meeting between people who've never talked to each other before.

This is the cost nobody preaches about.

DRY is one of those principles that feels unquestionably right until you apply it across team boundaries. The moment you share a module between domains, you're not just sharing code. You're creating a dependency that nobody owns and everyone resents.

Before you reuse, ask:

Will this change often?
Does it belong to one domain?
Are the consumers truly aligned in purpose?
Will one team’s change surprise another team?

If the answer to any of these is "I'm not sure," stop. Duplicate it.

I know how that sounds. It feels lazy. It feels like the thing a junior developer does before they know better. But here's what nobody wants to say out loud: two independent implementations you control are almost always cheaper than one shared one serving masters with different goals.

Duplication is a local problem. Coupling is an organizational problem.

One of them you can fix in an afternoon. The other requires a meeting with five teams and someone's manager.

Reuse isn't free. Treat it like the trade-off it is.

[Lazarus / html dev 2026 @all__hype]

to everyone who told me i couldn't ignore 52,000 emails:

[Lazarus / html dev 2026 @all__hype]

@Austen One snag: it’s going to be increasingly costly to use the ai tools. Maybe to the point of a salary?

[Lazarus / html dev 2026 @all__hype]

There are much better reasons to ration code than because it’s expensive

[Jonathan Ross @JonathanRoss321]

For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews.

This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No, that's out of scope. No, we need a design doc first. The No Engineer was valuable for 50 years. Every "no" saved real money. Their judgment was the rationing system.

LLMs will be the end of code rationing. Code is cheap now. And while the No Engineer is explaining why something can't be done, the Yes Engineer has already shipped three versions of it.

If you're a Yes Engineer, the next decade is yours.

[Lazarus / html dev 2026 @all__hype]

@blognaointendo Here for the 75k bookmarks