It is the true teacher who leaves the class knowing they have learned the most.

Tucson, AZ
Joined September 2006
Filter
Exclude
Time range
-
Near
Replying to @KeriHenare
@KeriHenare Why is that even necessary in a non XML document? If you want to use XML notation you can, but yeah, must serve as XML.
Replying to @elpie
@elpie Exactly. I like it when folks challenge the status quo, but I will almost always default to clean, semantic markup and CSS.
Replying to @KeriHenare
@KeriHenare No, you CAN close elements! You just can't use XML notation. <p>...</p> is fine.
Replying to @adactio
@adactio I agree with that too. I'm not adamant it go in the spec. I am concerned that we promote best practices. That's all :D
Replying to @KeriHenare
@KeriHenare which do you mean re: Misinformation? Am confused, multiple conversations going on here!
Replying to @awoods
@awoods no, I had /nothing/ to do with the W3C redesign. The people involved are acknowledged on the home page article.
Replying to @elpie
@elpie @yatil @stubbornella's ideas are interesting. I don't agree with OOCSS at all, but I like that she's challenging the status quo.
Open Letter To WHAT-WG, http://bit.ly/1iShTW via @cgrymala. I agree we should keep to rigorous syntax in HTML5. It's pragmatic that way.
@fraying If I may be tongue-in-cheek, "Consider the Source" - your article was spot-on.
ooh, sorry. I meant @stubbornella's Object Oriented CSS. Typing too fast.
Replying to @dstorey
@dstorey Actually, I'd like to see TV implemented more too. But still :D
By the way, those odd class names on W3C site are from @stubornella's Object Oriented CSS - very controversial but interesting no less.
Replying to @dstorey
@dstorey yeah, that's how I want my W3C specs - on TV.
Replying to @keranm
@oo00_Mr_K_00oo Are you sure about that? I seem to recall having had to pay a lot for a few of my dreams ;)
Replying to @dstorey
@dstorey Are you NEVER EVER satisfied child? My god. Give you screen, handheld and print and you want TV? You are the Geordie Jerry Seinfeld
"and it almost validates" @kevinmarks on W3C redesign. Classic.
1
Replying to @brucel
@brucel I will happily agree with that, particularly in light of backward compatibility. So we agree, as usual ;)
Replying to @judson
@JudsonCollier As I said, long time coming. The wheels on the W3C go round and round, just very very slowly.
Replying to @brucel
@brucel XML isn't the evil beast you seem to think it is. But I'm not gonna step in that with you now. Oh no.
Now if the W3C can redesign its bureaucratic infrastructure I'll truly be impressed (she says, with love and kisses)