5. With kernel drivers *in the hardware itself*, one would never have to worry about getting the correct driver, etc...
You mean I'd never have to worry about getting the LATEST driver, with the LATEST performance improvements or the LATEST bug fixes? Hummmmmm... fascinating!
I'm not sure if this is a recent change, but I use T-Mobile in the US and am able to send text messages up to 1000 characters. I confirmed this a few days ago by texting my wife (also uses T-Mobile). I used all 1000 characters and she received the entire text in one message. I don't remember being able to send such large messages in the past, so perhaps this is somewhat new.
AFAIK concatenated SMS http://en.wikipedia.org/wiki/Concatenated_SMS have been around for a while. It may look like a single long message, but it's really just a series of SMSs (each billed individually, usually) split and concatenated by the cell phones. Just try sending it to one (really) old cell phone and you'll see the magic undone (and several messages)
Because supporting a property in JavaScript that returns the HTML string with in an element isn't going to break anything else. Just because something doesn't come from a standard doesn't mean it's not a good idea to adopt it. It's only when you adopt something that breaks a standard or is in conflict with a standard that it becomes a problem. Supporting extensions on top a standard that break nothing else isn't a problem.
Not completely true. I don't blame Firefox implementation, after all, HTML was designed with extensions in mind (including ignoring unknown tags). But it gives support to those extending standards (on a non standard way!). And surely, extending standards (even with non breaking stuff) is a BAD thing. It creates vendor lock-in. (Think about Visual J++)
How many Bavarian Illuminati does it take to screw in a lightbulb? Three: one to screw it in, and one to confuse the issue.
