2 ms·
Not more resistant to new tech at all, they love tech and they certainly look very deeply at new self-proclaimed breakthrough tech. But they are probably more
by rurban 7y ago
Not more resistant to new tech at all, they love tech and they certainly look very deeply at new self-proclaimed breakthrough tech.
But they are probably more resistant to the current hype train, and they experienced the various pitfalls of hype-driven marketing. "Fake it till you make it".
E.g. as with the current safety hype around Rust, they probably know more about the three fundamental safeties Rust proclaims to support (Note: it does not). E.g. That Java proclaimed memory safety for a long time, and just last year really started to remove their memory unsafe API.
The maturity argument is relevant to managers only, not technicians. Older technicians love improving approaches to build and maintain software, be it more abstract, more elegant, shorter or just better. Older technicians love the new CI/Deploy pipelines, simplier OO or FP paradigms, better garbage collectors, better type systems, better concurrency approaches.
And maturity does not say that much. POSIX is pretty mature I would say, but has completely broken string (unicode) and concurrency support. Blocking IO does not help neither.
GCC and GLIBC are still a horrible mess. Linux/Windows/FreeBSD also.