When You See It...
-
-
DiscOS?
-
I'm going to assume that was snark, since the rest of it is.
-
The "NSA sponsored always ON mic" is missing.
-
I was wondering exactly what was meant by that... I mean, Discourse isn't actually a product of Stack Overflow, (it would be Stack Exchange anyway; +10 to pedantry) just some of the people involved as far as I know.
-
Maybe made entirely from SO code snippets
-
I was wondering exactly what was meant by that... I mean, Discourse isn't actually a product of Stack Overflow, (it would be Stack Exchange anyway; +10 to pedantry) just some of the people involved as far as I know.
You must not post here much.
-
Not for a long time anyway. Not that it's changed.
-
-
-
That generates XML just because that would be an enterprise feature.
jQuery and XML = enterprise? Ugh.
(Do not use jQuery for XML. Do not. It almost works, so you can get a long way before finding out that it fails horribly and you have to redo everything from scratch. Save yourself a lot of time and tylenol and don't let jQuery parse or build your XML. Though it's OK to shuffle XML around with jQuery's AJAX support.)
-
Does XML not work with the HTML DOM?
-
Does XML not work with the HTML DOM?
Not quite (and that's why it's such a dangerous trap). The big issues:
- The HTML DOM has different case sensitivity rules for element and attribute names to the XML DOM.
- The XML DOM supports namespaces which the HTML DOM doesn't.
The result is that things almost work, and may even work when you test, but will fall apart nastily if the other side tweaks something that shouldn't matter (such as changing the namespace prefix, or using elements or attributes that have anything other than all lower case names). At that point, all your nice jQuery code that handles the interface will need to be rewritten from scratch in raw XML DOM just so that things won't blow up in your face next time.
tl;dr: jQuery does HTML, not XML.
-
-
Yes, but good Belgium<m>ing luck in finding any implementations that make jQuery not crumble in your face if you try anything even vaguely off the single most common track of all. (The HTML5 may have namespaces specified, but its documents don't use them explicitly. That matters.) And there's the slight problem that jQuery doesn't let you specify what namespace you're interested in: you need to hope that you got the local prefix (which the XML spec says is arbitrary and subject to change on the document-author's whim) right since that's what you're really matching on.
http://i3.kym-cdn.com/photos/images/facebook/000/001/384/Atrapitis.gif
The problem is that it almost works. You can get a seriously large amount of code written and deployed before you find out just how much of a disaster is coming your way…
-
