Sure – with a first-class LLVM backend for WebAssembly, we could absolutely compile to it, which would mean running fully in the browser, which is something Emscripten can't quite manage at this point. That would certainly be very cool (and useful too). See https://github.com/JuliaLang/julia/issues/9430.
ES6 is groovy. Many features are in the runtime and not the syntax, and just work as-is. As other syntaxful features start to come into existence and then universal implementation in most active browsers, CoffeeScript should begin offering them -- at least the ones that align with the mission statement.
Some will be troublesome because of intentional syntax conflicts, like "for of" and perhaps classes. It'll just take a bit of design work to make things copacetic.
Nice talk. Given how you end the talk, have you looked at Elm? If so, what are your thoughts and do you think it satisfies unifying HTML, CSS and JS? (Putting aside the uphill battle of gaining adoption as a static typed, FRP language)
We do, indeed, hope to keep interactive articles working and available over the long term. But you can't always predict the technical choices of the future web.
For example, there are plenty of past Times graphics done with Flash, which may not be easily viewable within the next 5 years.
Now, the "before" panoramas are actually "way after" shots. We'll need to go back and fix it somehow.
But it's not all Sisyphean. The standard operating procedure for any interactive article page is to live somewhat inside and somewhat outside of the CMS -- with the page's own baked-out HTML base, and individual copies of any JS libraries and CSS it needs (apart from the super common ones). With a little foresight, this should be resistant to breakage from future site redesigns, even if the page continues to look a little "old" ten years from now.
As @frik noted, it uses "I'm feeling lucky" feature of Google. It requires the page to be indexed to work. If the page isn't indexed then it won't work. But since the pages you'd like to see are indexed almost always, it shouldn't be a problem.
No, that's not what I mean. I mean that the bookmarklet is working intermittently for me on any page. I'll click it, and sometimes get redirected through, and sometimes end up on a blank white page. That doesn't happen to you?
That's interesting, I see a white page for a second or two and I get redirected. If something else is happening for you, would you mind sending me a DM on twitter @umurkontaci? I might be able to fix it.