: I've used CSS since 1998. At no time in the last 18 years has it been "easy"
-
-
Replying to @slightlylate
: ...and I understand layout pretty deeply at this point. Still sucks.
2 replies 0 retweets 1 like -
Replying to @slightlylate
so you'd rather go back to sematic font tags for styling? Or is it using CSS for layout that bugs you, not necessarily styling
2 replies 0 retweets 0 likes -
Replying to @gregwhitworth @slightlylate
a more XAML type approach if you will
1 reply 0 retweets 0 likes -
Replying to @gregwhitworth
no he's saying it's ossicular good at neither I think. It's hard to judge what good would be tbh
@slightlylate2 replies 0 retweets 2 likes -
Replying to @briankardell
: good is layered. Good is not having to appeal to capricious gods who neither care nor will divest themselves.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @briankardell
just so we're clear, when you say gods you're referring to the working group at this point, or using CSS?
1 reply 0 retweets 1 like -
Replying to @gregwhitworth
: the WG + browsers + their legacy. Users need an out and the WG promises castles in the sky. Burn it down.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @briankardell
"Burn it down" So Web 3.0 it is ;)
2 replies 0 retweets 2 likes -
Replying to @gregwhitworth
: nah. WICG + Houdini is enough for now. I'm patient. But new work at CSSWG is a bug
2 replies 0 retweets 1 like
: there's a reason that Googlers must now use WICG for new work. CSSWG is half of it. So much #fail
-
-
Replying to @slightlylate @gregwhitworth
and that is the hardest time to use wicg too
1 reply 0 retweets 1 like -
try the dogfood, it's delicious.
0 replies 0 retweets 2 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.