A lot of the positioning problems of CSS for the last 10 years would have ironically been solved with tables

Accessibility concerns could have been addressed using the same mechanisms we use today

E.G. role="navigation" on <nav> elements or aria-label="Home" etc...

The meager bandwidth savings also go away considering how large JavaScript libraries are by comparison

Not saying tables were good all along. Just saying, maybe they shouldn't have been thrown out so quickly

@cypnk i still hear demonisation of "they're slow, they're bad" etc despite them mostly benchmarking faster than flexboxes and them actually doing what i want some of the time. i don't know any js frameworks though, so i'm not a Real Web Dev

@majachai I think it's perfectly fine to call yourself a web dev even without knowing JS frameworks

There's a lot more to design than one specific tool

We still call someone who only uses hand chisels or planes a carpenter even if they don't own a single power tool

Julian Bond 🍸
Follow

@cypnk @majachai Couldn't agree more about tables.

Imagine the old /. layout.
Header
Left aligned, Fixed width left column
Variable width middle column
Fixed width right aligned right column
Footer floating below the longest column
The whole having a max-width and centered on the page.

I never did work out how to do this with just CSS, No tables and no JS. And I'm not sure anyone else did either. And yet it's almost trivial with tables+CSS.

Sign in to participate in the conversation
Mastodon

Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!