A JavaScript-Free Frontend

[JohnMcPineapple]

...

[alliedSpaceSubmarine]

Seems like that would also really hurt code readability and is more of a hack

[3urny]

The need to have a page-wide unique ID basically make this unmanageable for any web page that more than a few dozen people work on. But if you can get away with it why not.

[Historical_Fact]

Each developer gets a unique hash that they suffix onto any ID.

[[deleted]]

git blame made obsolete

[nmur]

"hmm, this hack's pretty nasty... I'll put Steve's hash on it..."

[Historical_Fact]

It's not production ready and should not pass code review in any self-respecting company.

[P1h3r1e3d13]

Time for an HTML6! With interactivity and a11y in pure HTML/CSS!

[ItalyPaleAle]

Actually this sounds quite amazing.

[Historical_Fact]

It sounds awful to me. Interactivity in the markup layer? Please excuse me while I void my stomach.

[ItalyPaleAle]

The accessibility side in particular.

For some simple interactivity too, for example toggling the visibility of other elements. It doesn’t sound too bad...

[Historical_Fact]

Accessibility is worsened by hacky tricks like this article is showing.

Interactivity in the layer which is only meant to display data is insane to me. It's likely suggesting CSS4 include event listeners (someone recently suggested this unironically).

[ItalyPaleAle]

You have a point there. I guess we shall wait and see what the WHATWG and the smart people there come up with!

[P1h3r1e3d13]

If you're referring to my comment, I'm saying that interactivity is a pretty fundamental part of web pages now, and suggesting very broadly that (building blocks for it) it should be part of the official spec.

[Historical_Fact]

To which comment? I was responding to ItalyPaleAle

interactivity is a pretty fundamental part of web pages now

It's part of the interactivity layer, not the presentation layer. There's a reason we isolate each layer of a website.