4 ms·
Is that supposed to be a bad thing? I like having only one implementation. Multiple compilers is annoying for users, have to write "portable" code which can onl
by zarzavat 5mo ago
Is that supposed to be a bad thing? I like having only one implementation. Multiple compilers is annoying for users, have to write "portable" code which can only target the lowest common denominator. Only when a feature ships in Clang, GCC and VC++ can you use it. Each compiler needs its own flags/project as well.
Loosely coupling a language to its compiler is 20th century thinking for when programming languages were simple. It works for C because C is simple enough to be implemented over and over again. But for today's hyper complicated languages, multiple implementations is a pain for everyone.
- asddubs 5mo agoIt's a bad thing if you want your language to be truly portable and be able to work on anything
- NooneAtAll3 5mo agoyes monopolies are always a bad thing
- zarzavat 5mo agoA programming language with a reference implementation is not a "monopoly", it's a standard. By having a common implementation to write code against we can avoid wasting time on pointless minutiae such as which features are portable in practice and which are not. When a programming language community fractures into multiple incompatible implementations everyone is worse off.