5 ms·
I think it is promising and long overdue, too. It also is clear to me that this will win, because Apple pushes it into LLVM, and has a head start at it. On the
by Someone 14y ago
I think it is promising and long overdue, too. It also is clear to me that this will win, because Apple pushes it into LLVM, and has a head start at it.
On the other hand: if someone would do the equivalent to their browser, people would call it fragmentation.
It will be interesting to see how gcc reacts to this. If this decreases compilation times significantly, I think they will have to follow suit.
- micampe 14y ago> On the other hand: if someone would do the equivalent to their browser, people would call it fragmentation. I haven’t seen many people calling Dart, Pepper, Native Client or the Chrome Web Store “fragmentation”.
- Someone 14y agoWith "the equivalent" I wasn't thinking about creating entirely new ecosystems; I was thinking of tweaking the existing ecosystem to favor one's own tool chain. The moment somebody writes the first module, the world sees the first 'best compiled with clang' code. Once that code uses #import to improve compilation speed, that could become 'must be compiled with clang'. That, IMO, is similar to adding an extra tag to your browser's HTML dialect and then promoting its use. I expect Apple is aware of the risk and wants to to prevent this (the fact that they plan a 100% compatible middle step is an indication of that), but the risk is there. Also, people have argued that the effort spent on Native Client should be spent on improving JavaScript performance because of the fragmentation issue. Responding to another comment: people also have complained about the gcc-isms present in lots of open source libraries.
- micampe 14y agoThe ecosystem is the www, not Javascript and HTML, so those are all tweaking and extending the ecosystem. The moment somebody writes the first Dart or NaCl based website or the first Pepper plugin, the world sees yet another (not the first) "must be viewed with Chrome".
- munificent 14y agoWebsites written in Dart work just fine in any standards-compliant modern browser. You just compile it to JS the same way you do CoffeeScript. This makes sense because no widely deployed browser, not even Chrome, has the native Dart VM in it. You can download a build of Chromium with the Dart VM in it, but Chrome itself doesn't have it (though we hope it will when the time is right). Check out api.dartlang.org. If the site works for you then your browser supports Dart just fine. :)
- micampe 14y agoRight, I forgot about that, thanks.
- aidenn0 14y agoThere is almost no way this won't decrease compilation times, particularly with non-aggressive optimizations. With optimizations off, the vast majority of compilation time in C++ is processing the standard header files over and over again.
- msbarnett 14y ago> On the other hand: if someone would do the equivalent to their browser, people would call it fragmentation. This happens all of the time in browsers. See: Dart, vendor prefixes, JavaScript, etc, etc. This is also absolutely nothing new in compilers. GCC has had a bucket load of its own C extensions for years (decades), as have many other compilers from many vendors. Vendor-specific extensions are par for course. In fact, they're a good thing! The first step in moving a standardized language forward is to have the vendors designing and adding non-standard extensions so that they can experiment with ways to "scratch the itch" they're feeling. Good extensions get taken up in committee, and if they can be made palatable to all involved, they get standardized. Bad extensions die on the table. Having tried-and-tested features drive standardization allows hindsight and experience to strengthen resulting standards. We call the opposite, where the standards body invents a feature out of whole cloth with no example implementation having been tested in the real world, "Design by Committee". This strategy does not have a high reputation for quality and success.