Deleted Comment
It's something i've been struggling with quite a bit. Conceptually i love Polymer, and really want to switch, but React's serverside rendering is just hard to beat. I'm scared of showing users page load spinners while my 20 Polymer components all load their data heh
Aren't you tired of having to query the DOM tree and manually manage the structure to create UIs? Web Components doesn't solve this at all, it just tries to encapsulate the work. The problem is that building apps is building components, so you inevitably are forced back into the manual DOM management to create your app-specific components (like how you constantly have to create directives in Angular). You also need to jump into JavaScript to configure and wire up any Web Components you used. It's a very messy abstraction, and fools you into desiring a pure HTML-based declarative way to write apps, which is like wanting steak but eating liver.
See http://jlongster.com/Removing-User-Interface-Complexity,-or-...
Questions were raised as to why Malaysia Airlines had continued to fly over such a volatile region, where separatists were known to be shooting at aircraft. Qantas, the Australian carrier, said it had been steering clear of the area by 400 nautical miles for several months. Malaysia Airlines said that after the crash it immediately altered its flight paths, while other airlines either did likewise or emphasised they had already been taking alternative routes.
"With immediate effect, all European flights operated by Malaysia Airlines will be taking alternative routes avoiding the usual route," said a statement from the airline. It added: "The usual flight route was earlier declared safe by the International Civil Aviation Organisation. International Air Transportation Association has stated that the airspace the aircraft was traversing was not subject to restrictions."
http://www.theguardian.com/world/2014/jul/18/mh17-pressure-o...
It's always irritating to be reminded of how the rest of the world sees my country: as a series of (mostly correct) stereotypes.
It will, however, run (...) on the platforms that support SIMD. This includes both the client platforms (...) as well as servers that run JavaScript, for example through the Node.js V8 engine.
...and:
A major part of the SIMD.JS API implementation has already landed in Firefox Nightly and our full implementation of the SIMD API for Intel Architecture has been submitted to Chromium for review.
...and:
Google, Intel, and Mozilla are working on a TC39 ECMAScript proposal to include this JavaScript SIMD API in the future ES7 version of the JavaScript standard.
So, yes, there's definitely an intention there to put it into V8/Node.js/ES7 (guess, it will be in this exact order).
Ironically and to my surprise, as I'm far from being any sort of an art buff and this stuff usually bores me, at Rijskmusem I really enjoyed those typical descriptions put next to the paintings, with short notes about art history and some details about described work of art. There they really are filled with interesting info. To each his own I guess. Or maybe it is unexpected side-effect of the "Art is Therapy" project.