2 ms·
> "And this is really the biggest contradiction of them all. Tons of people have invested countless hours to build these VMs, these new languages, these compile
by vanderZwan 13y ago
> "And this is really the biggest contradiction of them all. Tons of people have invested countless hours to build these VMs, these new languages, these compilers, these optimizations. Yet somehow, they all seem to agree that it is impossible for them to sit down and define the most basic glue that binds their platforms, and implement a shared baseline for their many innovations. We really should aim higher than a language frozen after 10 days, thawing slowly over 20 years."
It's kind of hard to redesign an airplane in flight, and because of the way the web works, that's a problem that applies to browsers a lot more than some other pieces of software.
- dgregd 13y ago> It's kind of hard to redesign an airplane in flight It is true that IE6 was 5 years in flight. However that has changed. Google replaces Chrome plane each 6 weeks. JavaScript it is new IE6. I really would like to see Dart in Chrome stable release. Sometime ago I thought that pure VM, like JVM, would be better. Now I think it is safer to leave scripts loaded as plain text. Just like HTML, CSS. It is hard to guess how whole web ecosystem would work with scripts loaded as bytecode.
- jheriko 13y agohot swapping and migration are extremely well solved problems in software... the reason you see it screwed up so much as that few people actually care about it at all. i'm convinced that fear and lack of understanding are the genuine problems here... browsers and the webstack are fantastically shoddy and poorly engineered though and that is a serious obstacle... but it doesn't make the problem intractable or hard. 'just' effort.