Re:The Costs of Programming Language Fragmentation
by tomjakubowski on Tuesday October 02, 2018 @12:15PM
(#18122987)
Well, to me it's like the way Shakespeare, e e cummings, and Kool Keith all write in the same language.
Context switching between working on work codebase, Chromium code base, and various third party C++ codebases is a headache as much for their basic differences in coding style (use of whitespace, capitalization, naming, etc.) as for their wildly varying build/metabuild processes.
And of course, each implements and then extensively uses their own library features like reference-counted pointers, managed GC pointers, collection data structures, iterator-like abstractions, etc.
Re:The Costs of Programming Language Fragmentation
by nescoiquid on Wednesday October 03, 2018 @08:01PM
(#18135886)
> their wildly varying build/metabuild processes.
Boost? I'm sure there's good reason for the -- sui generis -- build system. Always been too underwater to spend much time wondering about why that's a yak I'm shaving.
I strongly disagree. This may have been the case 20 years ago, but most current projects use C++, not some weird -fno-rtti -no-stdinc -fno-whatever sub-language. Maybe they don't use all the features of the standard library, but which project in Java or Python would ?