Somewhere out there, there must be a scale of Apple hyperbole. I wonder where "insanely great" ranks compared to "unbelievably great", "amazing" and "magical".
For those of you complaining about the quickstart up-and-running wiki tutorial, don't forget you can always read the related RFCs in the devchannel backgroup IRC log server dump.
Nice, but I'd really wish it supported a half-way decent transpiled CSS language, like SASS, LESS, JESS, GUESS, or ASS, that gets auto transpilezipped with a simple 'ant ruby merge push' command.
I work for a company that pulls in five million dollars in sales a day. I upgraded all our servers to HTML9 Bootsauce and it broke everything. What the fuck?! Cross dressed in a unitard compatible my ass! We're losing money by the character I type! How do I revert?! Can't trust anything these days.
Maybe it is just me, but it seems around the time that "responsive" became a term for layouts that adapt to screen resolution, the other term "reactive" which denotes UIs that represent some kind of live and changing data inline on the page was becoming a thing. It almost seems like that was the cool thing first and freaked out people, and now it is like there's an initiative to minimize "reactive" as a buzzword, and put the tamer "responsive" buzzword in its place... presumably while someone works on some kind of large "reactive" effort and then can announce their "big new thing" with their own term... anyway... i'm probably making things up :D
Well, it's very funny, but it also points to an important architectural bottleneck for modern web applications. There's a veritable explosion of combinatorial front-end projects: 'projects' which merely exist because of the ad hoc way in which these individual technologies can be combined. They add nothing in and of themselves.
For a traditional programmer, this is equivalent to a (very public) proliferation of "convenience" interfaces or methods, yielding one "convenience" method for every possible combination of real method calls. With such a proliferation, these methods cause a great deal more inconvenience then they alleviate, and the situation becomes absurd. (For some reason, Twitter's Boilerplate release has spawned an incredible number of mis-guided "me too" fork-projects that basically roll in <insert technology here> into the Boilerplate project and release it as new.)
So, the serious message is that a) people need to stop with the combinatorial responsive html5 boilerplate bootstrap projects, and b) there's a real architectural problem that needs solving on the front-end of the web. Basically, we need a module system for HTML, JavaScript, and CSS. (And it's shocking that such a thing doesn't exist, apart from ad hoc, essentially proprietary solutions like WordPress themes.)
Yea, when I was a wee programmer, I made a "class" for socket.h which was just a wrapper that mapped things to a class, so when you wanted to create a socket connection, you just created an instance of that class, and start using it. It was pretty dumb, but I thought it was cool at the time. I should have overridden the << and >> operators but I was just happy that my "send" and "receive" worked. That was when I was 21, about twelve years ago. Now you see these kids doing something similar, but they have a website on which to place their experiments. I don't hate on them because I was there once myself, but I don't pay them much attention either.
Yea I agree with you, I think we have enough html7 shits popping on twitter, do we really need that kind of stuff on hackernews? ... It does not bring any interesting discussion and does not show anything useful..
http://jsfiddle.net/N9TNy/