4 ms·
> The section about layout starts with...This history lesson is not really relevant for newbies. so folks know what we're talking about: https://web.dev/learn
by magicalist 5y ago
> The section about layout starts with...This history lesson is not really relevant for newbies.
so folks know what we're talking about:
https://web.dev/learn/css/layout/#layout:-a-brief-history https://web.dev/learn/css/layout/#layout:-a-brief-history
It's four (pretty short) sentences that give a small amount of context pretty quickly and then links to another resource if you want to know more. I'd agree with you if it were a page or two's worth of history, but there's not much to find distracting here.
More importantly I think you're focusing on the newbies who are coming in with nothing but ignoring the newbies who are looking at existing code and a whole bunch of tutorials and stackoverflow answers out there written over the last two decades. Acknowledging that things have changed in CSS quite a lot in that time and pointing to where they can learn more means you don't distract the really new newbies much but you also don't confuse the other ones, leaving them with lots of questions ("but I read [this] about CSS...") and no idea where to look to reconcile some old advice ("use jquery for all styling!") with what they're learning now.
But it's also four sentences in the eighth chapter of a tutorial. It's not going to solve all confusion but it's also not a derailment.
- goto11 5y agoBut there are many generations of cruft. Table-based layouts is just one thing, how about font-tags, quirks-mode-triggering doctypes, frames, float-based layouts, <!--[if IE]> and so on. Each of these might by necessary to understand in some very specific cases of legacy code. I'm just saying: Don't put this up front in a tutorial. Don't explain GOTO before explaining if-else blocks.