News for hackers. Stuff that matters.
Re:Best Practices with CSS Grid Layout by mattmanser on Saturday May 26, 2018 @07:24AM (#17161450)
The tables bashing was because it resulted in tag soup, even though it was conceptually easy.

This doesn't suffer from the same problem.

Re:Best Practices with CSS Grid Layout by adventured on Saturday May 26, 2018 @08:36AM (#17161703)
The tables bashing was because of the common view that CSS and HTML, the styling and markup, should be separated. It wasn't due to tag bloat, which has remained common with HTML regardless (we still have a million div tags in the place of table/td/tr).

<table> is a rigid display value taking up an entire tag. So the argument is why not push that into the CSS eg in a div instead and get rid of an entire unnecessary tag. This is why display:table doesn't get the same kind of hate thrown at it that <table> does.

Re:Best Practices with CSS Grid Layout by digi_owl on Saturday May 26, 2018 @08:59AM (#17161778)
So in effect it was fashion mixed with politics disguised as a technical discussion...
Re:Best Practices with CSS Grid Layout by sureaboutthis on Saturday May 26, 2018 @08:36AM (#17161705)
Tables are not 'tag soup'.
Re:Best Practices with CSS Grid Layout by ggregoire on Saturday May 26, 2018 @11:17AM (#17162480)
10 tables to display 1 header, 1 footer, 2 lines of text and 1 image in an email is 'tag soup'.
Re:Best Practices with CSS Grid Layout by JimDabell on Saturday May 26, 2018 @11:36AM (#17162580)
“Tag soup” doesn’t mean “bad markup”. It specifically refers to when you write HTML as a series of commands and the result is a bunch of tags that aren’t nested properly and don’t result in a tree structure. Things like <b><i>…</b></i>.
Re:Best Practices with CSS Grid Layout by omribahumi on Saturday May 26, 2018 @07:30AM (#17161470)
So they should’ve added new tags for layout, instead of table,tr,td,th ?

Much like yield vs await in Python3 asyncio.

In the Python 2.7 days, people used generator functions to implement async in Python. When Python3 first came out, you couldn’t do both generator and async in the same function. I assume it’s because they used the same mechanism internally.

I think it was Python 3.5 which added support for async generators.

Re:Best Practices with CSS Grid Layout by gwillz on Sunday May 27, 2018 @08:09AM (#17166567)
I don't believe python 2.7 could ever do async. Async was only possible in 3.3 when `yield from` landed and then was bastardized into coroutines through decorators.

3.5 released true asnyc/await based on the `yield from` form and then 3.6 allowed for async generators.

You were close and your point remains. Although I don't think new tags are the right choice. I think HTML learnt a while ago that more tags doesn't solve everything.

I do really enjoy python async. It's cool to see a feature develop from a hack like that but a language first approach could have avoided some headaches. This is where Grid wins, it's a fresh take without requiring to maintain backwards compatibility with previous attempts.

Re:Best Practices with CSS Grid Layout by repsilat on Saturday May 26, 2018 @09:29AM (#17161897)
I think the philosophical difference is meant to be that in HTML tables the layout was part of the markup (and so had -- or should have had -- semantic meaning) whereas with CSS Grid the table layout is part of the styling. This is alluded to in TFA's section on accessibility.

For devs who don't care so much about accessibility, and are more just interested in getting the layout they want, I guess that argument may not resonate so much. I personally don't care much for taxonomic/teleological arguments around REST methods, but I'm a bit more willing to follow fashion with Grid if it means people on screen-readers will have a better time.