Why is XHTML bad?
-
All I want is HTML, but with a different syntax, semantics and use case and variables and functions. Why is everyone so down on this?
OH SHI-
-
I think that will be slightly more entertaining and productive than convincing @Bort that he doesn't know what attributes are for.
I'd rather argue with @blakeyrat frankly.
-
Yes, what I was proposing was the hammer. Thank you for the analogy.
No, child elements (in this conversation) are kind of like a sledge hammer, lots of power. Try to use that to hang a picture, and you'll end up with a hole in your wall.
Attributes are a plain hammer. Perfect for hanging pictures.
-
-
I was about to say "not in his analogy", but then he liked your post. So I guess you're right.
-
+92
Liking this didn't seem to be enough. Plus, I'm sure @Onyx appreciates the crowbar mention.
-
-
html needs more metal:
-
Hands up if you remember HoTMetaL.
-
Jesus christ, I walk away for like an hour or two and you guys slam out nearly 90 replies to this topic. What the fuck guys.
-
Jesus christ, I walk away for like an hour or two and you guys slam out nearly 90 replies to this topic. What the fuck guys.
I think I've gotten everyone used to
spammingrapid-fire posting in my threads.
-
Pointless arguments focusing on technical minutia and pedantic dickweedery wait for no one.
-
Just breathe. You'll catch up.
-
Hands up if you remember HoTMetaL.
That depends on your definition of remember. My only experience with it was 15-ish years ago. I was indexing journals for a group I belonged to. I sent them an HTML file ready to be published. They ran it through HoTMetaL and broke it.
-
Jesus christ, I walk away for like an hour or two and you guys slam out nearly 90 replies to this topic. What the fuck guys.
You didn't get the memo? This is the new likes topic. The only difference is now you only like the posts you actually want to like.
-
Make a big announcement about the discontinued support. People who care about being accessible will update their pages. Screw the rest.
This works with most standards, but HTML is an entirely different behemoth.
Filed under: I'm a licensed standardologist
-
XHTML isn't bad!
It's just misunderstood!
Haters just need to open their minds to it's beauty!Imagine all the web tags
Closed or as flags
Yoooouuuu
Might say I'm a retard
But there are lots of other retards, too
W3C's what they call us
And we'll all shit on you
-
Just how drunk are you? (Or maybe how many medications you're currently on)
-
+1for vb then.
-
The Internet isn't broken, but it's definitely crippled, by the fact that the HTML standards are so loose. The barrier to entry would be higher, but that wouldn't necessarily be a bad thing.
That being said, I've noticed that if you have a
<br />
in your document and View Source in Chrome, it will render as<br>
.Also, this:
http://what.thedailywtf.com/t/any-bool-will-do/1549
-
The Internet isn't broken, but it's definitely crippled, by the fact that the HTML standards are so loose. The barrier to entry would be higher, but that wouldn't necessarily be a bad thing.
That being said, I've noticed that if you have a <br /> in your document and View Source in Chrome, it will render as <br>.
I really need to stop closing my br with the />, but it's such an ingrained habit at this point.
-
That being said, I've noticed that if you have a <br /> in your document and View Source in Chrome, it will render as <br>.
Chrome likes to show you the DOM tree, which is usually more useful than the raw source. I think the actual source is available only by reading the raw content of the response that delivered the source to you. As if you cared.
-
The concept of XHTML2 was that it's always strict, and so web browsers can be made "simpler" by just using off-the-shelf XML parsers instead of HTML parsers! Except they can't, because there are 300,000,000 websites that don't magically disappear just because the W3C thinks that should-- in fact the W3C made web browsers more complicated, because due to XHTML1 Strict, they all needed XML parsers in addition to their existing HTML parsers.
Having the XML support in the browser is nice for working with complicated webapps. But yes, XHTML was a fucking disaster, mostly because of the “delete all the useful stuff!” attitude. If it had just been an XML syntax over the same basic DOM tree, it would have been not too big a problem, and its real purpose — allowing viewing of XML by using XSLT to spit out XHTML — would have worked fine. But nooooo...
The W3C are collectively a bunch of mouth-breathing morons. (I work with someone who's rather deeply into the W3C standardisation process. He's smart, but hard to keep focussed.)
-
If they made html fully XML compliant from the start, that would have been great.
That would not have been possible without a time machine; HTML preceded XML by years.
-
Breaking poorly-coded sites would probably benefit humanity as a whole.
-
I would say: thinking XML and HTML are the same language based on some cosmetic similarities is bad.
They are, though:
-
From the W3C's documentation: HTML checked Attribute http://www.w3schools.com/tags/att_input_checked.asp
TRWTF is thinking w3schools is a W3C site.
-
TRWTF is thinking w3schools is a W3C site.
Never said it was, but it parrots this info:
-
I really badly wanted to cling onto XHTML forever when I saw that the W3C had finally tried to fix up the web and make it properly structured. However, I have to concede that HTML5, along with its CSS3 and JS API friends, have actually improved the web, despite still being crappy SGML. It's a bit sad, really. I would have liked to see XHTML 2.0 look like HTML5.
-
semi-column inference in javascript
Yeah those half columns drive me crazy.
@cartman82 said:You can't push toothpaste back into the tube...
Of course you ca-... You just, uh. Hm. Well, fuck.
Filed under: What do you mean I can't decrease entropy?, He said, a full week later.
-
Of course you ca-... You just, uh. Hm. Well, fuck.
Filed under: What do you mean I can't decrease entropy?, He said, a full week later.
Well, smartass, tell me how it got in the tube in the first place then? Huh?
#Checkmate!
-
They freeze the toothpaste, wrap the tube around it and then let the toothpaste thaw.
-
@cartman82 said:
You can't push toothpaste back into the tube
Of course you ca-... You just, uh. Hm. Well, fuck.I guess this explains your absence.
-
I guess this explains your absence.
I eventually solved the problem by reassembling the tube around the paste.My personal life recently got very active, and in a couple weeks I'm going back to college (while still working). Expect to see less and less of me.
What I meant to say is: I'm immolating myself in protest of infiniscrolling.
Filed under: That's still a thing it's popular to be angry about, right?, Are tags still cool?
-
Filed under: That's still a thing it's popular to be angry about, right?, Are tags still cool?
Those are so July.
-
Never said it was, but it parrots this info:
Wow. That page is straight out of my 1999 clan page for a video game. I was also 11.
-
Wow. That page is straight out of my 1999 clan page for a video game. I was also 11.
So you're saying they were 2 years ahead of their time?
-
Maybe, it depends on how much you attribute to an 11 year olds web design expertise.
-
Still...that page doesn't seem outrageous for 1997.
-
That background can't be called anything other than outrageous.
-
Oh boy, I have vague memories of searching for a "nice background texture" for sites I was making as a teen. WTF was I thinking?
-
I was a big fan of fixed backgrounds back in the day. Fixed background, moving text that was often low contrast to some of the background.
Evil or bad ideas thread, anyone?
-
Can you imagine the nightmare of trying to find a missing
)
though? No thanks.Even debugging first year uni LISP was horrendous
-
+100 for S-exps.
-
I think the actual source is available only by reading the raw content of the response that delivered the source to you. As if you cared.
You can get the source with ctrl-u. But yeah, the dev console is way more useful.