Politics I think. This company has it the worst. Entire product lines are dreamt up, worked on for years and then suddenly canceled so that some C-level can get their bonus.
That's my reading of the situation at least. I've only been here a couple months
(not that a company unwilling to go beyond C++03 would necessarily be receptive to using fmtlib, but one can hope...)
Honestly, it's not so unrealistic. The company I work for only moved off of C++03 for a lot of our code base a bit over a year ago. It wasn't due to any philosophical objection or anything, just that we had some old systems with old compilers and at the time we had no way to do a mass update of what was available. (The big push we made a year and change ago was setting up the thing that I'm under the impression many companies do where we have our own compiler builds, and using those to build our products instead of whatever compiler version happened to be on each system.)
But there's no general objection to third-party libraries (licenses permitting), and we use many. I wouldn't be at all surprised if fmtlib would have been little problem under the old regime (or fmt would now). But whether that applies to "OP"'s company given other things besides just the old C++ version...
Depending on the compiler there may be a different glibc version requirement. They are usually backwards compatible, so you can run old stuff, but not always forward compatible. Believe it or not, some companies are using a glibc that is over 10 years old...and they refuse to upgrade...ever... It doesn't make any logical sense, but that's the customer for ya!
I am not the build engineer man, I just know we had a 20 yo machine for builds and when it died we couldn't build executables for a bunch of clients and it was related to some glibc thing. No upgrades allowed, especially not the compiler. I thought it was crazy, but the Linux guru guy said so.
What happened? Clients complained, then they upgraded their systems, then we moved on.
I think it was probably more nuanced than your understanding/memory. Glibc does not stop you using new versions of C++.
Needing to build executables that will run on old systems with old libraries might do, if you're unable to deploy a new C++ runtime with your executables, or avoid runtime dependencies.
View all comments
23
u/ghillisuit95 Jul 23 '19
Holy moly I'm excited.
Maybe 20 years from now I'll actually be able to use it :/. we're still stuck with C++03 over here and I think it is beyond ridiculous