3 ms·
This is not a product launch.
by cromwellian 15y ago
This is not a product launch.
- skrebbel 15y agoThe lack of browser support implies architectural choices that will always make old browsers lag behind. It means that the generated JS uses modern JS features. If it would be easy to support older browsers, they would've done so already - at least to some extent. The fact that it compiles only to JS for the very latest versions of a small number of browsers gives me the impression that a lot of language/compilation choices are closely tied to these new JS features. This, in turn, implies that supporting older JS versions is non-trivial. Maybe I'm wrong, that'd be nice.
- cromwellian 15y agoOr maybe they've only been working on this thing for a few months and were slavishly fixing bugs right up to the announcement, and IE6 support wasn't really a priority? Except for Isolates -> WebWorkers, there's not really anything that can't be emulated in IE6. GWT has to handle a significantly more complex set of semantics and still works on IE6. But personally, I prefer if there wasn't IE6 support, or any non-HTML5 browser support for that matter. If you're going to do a new VM, do a clean-break, because legacy support is another factor which makes web development a pain.
- munificent 15y ago> It means that the generated JS uses modern JS features. I believe it compiles to ES 3, which is isn't exactly "modern JS features". IE6 is ten years old. At some point, you've gotta cut the cord!
- arctangent 15y agoGoogle officially started phasing out support for IE6 in January 2010. It's reasonable to assume that new languages (etc.) released by Google would be aligned with their general policy on which browsers are to be supported and which are not.