4 ms·
Was it overengineered, or is this one of the rare cases where "too much" architecture upfront was actually a sound long-term investment? GCC is still around an
by pavlov 9y ago
Was it overengineered, or is this one of the rare cases where "too much" architecture upfront was actually a sound long-term investment?
GCC is still around and kicking and competes well with the much more modern Clang that has substantial investment from Apple and other industry giants. That's an amazing achievement for a 30-year-old open source project.
- rimliu 9y agoYou can look at this from other side: the fact that Clang was created and is quite popular tells that GCC had enough problems to warrant its creation.
- pavlov 9y agoIs there any major software project that doesn’t get competition after 20 years? (Counting from gcc’s release to clang’s launch.) This industry is constantly reinventing. Clang takes a different tack in both licensing and implementation, and that’s great for everyone.
- rimliu 9y agoIt depends if you are talking only about open source or all projects. In the latter case I'd say Photshop still has no competition. There are alternatives for some subtasks (photo editing for web), but for print work nothing comes even close, afaik.
- eru 9y agoThe Bloomberg terminal also enjoys an enviable moat these days. But that's mostly network effects.
- pmontra 9y agoGcc had competition in the form of proprietary compilers from hardware manufacturers. I remember I used the HP compiler on HPUX machines at university (8xx series?) We were using gcc most of the time, can't remember why.
- johannes1234321 9y agoWhile clang's creation doesn't root only n the fact of "wrong" engineering, but of different goals and politics. For the later: An important driver in clang are Apple and BSD communities who don't want to have GNU software (especially GPLv3) in their systems. Also parts of gcc's architecture are created for political reasons to make it harder to decouple, while clang's primary design was to build a library which understands C/C++ and also can be used as a compiler. The purely technical arguments (i.e. gcc has bad diagnostics and clang gives better errors) are minor (gcc, due to the competition, became way better, if equal time would have gone to gcc instead of clang it might be even better) All that said: I really love this cooperative competition which benefits everybody, where you have different options try out ideas and where for large parts contributors discuss ideas between competing solutions.
- dwc 9y ago> parts of gcc's architecture are created for political reasons to make it harder to decouple This was a major, long standing gripe about GCC, and it materially affected its quality and usability. This was not an orthogonal matter: bad technical decisions were made in the interest of political goals. > if equal time would have gone to gcc instead of clang it might be even better I don't think so. GCC's position as the de facto choice for a free/open compiler, coupled with some of the political/organizational decisions of the project, made it easy for developers to say "it's good enough!" on such things. Viable competition is one of the few things that will shake a team out of that.
- eru 9y agoPolitics bear a part of the blame for some of GCC's more questionable architectural decisions. They intentionally made the architecture hard to write plugins for.
- bkeroack 9y agoThe entire reason GCC exists is politics. The same can be said for the rest of the base GNU system.
- anitil 9y agoFor the ignorant: what decisions are you referring to? I've heard this a lot but am not sure what people mean.
- eru 9y agohttps://news.ycombinator.com/item?id=15408652 https://news.ycombinator.com/item?id=15408652 explains it better than I did. Basically, early on they didn't want GCC to be able to be used piecemeal with closed source compilers / plugins. Thus they made GCC hard to be used piecemeal. But using bits and pieces of your compiler is exactly what you'd want to be doing when you want to have good editor integration: eg syntax highlighting _should_ actually use the compiler instead of duplicating logic. Especially with a language that's Turing complete to even parse like C++; the logic just to figure out whether something is a type to be coloured eg blue or a variable name to be coloured eg green. (See http://blog.reverberate.org/2013/08/parsing-c-is-literally-undecidable.html http://blog.reverberate.org/2013/08/parsing-c-is-literally-u...)