Of course, this is mostly specific to web development.
On the other hand, being old means you can quickly spot how trendy magpie technical stacks map to old patterns that the industry has been consistently reinventing over time.
It's also debatable just how many startups actually have much of the contemporary DevOps and data center infrastructure as part of their standard workflow, as opposed to all the volume of buzz that goes into discussing it.
spot how trendy magpie technical stacks map to old patterns that the industry has been consistently reinventing over time.
oh, gosh. That too. The other big problem we have with so many "new" programmers is you can get a critical mass of a few million users before a platform even makes sense. Go shouldn't exist (Erlang did it first). MongoDB shouldn't exist (no explanation needed). But, they scooped the kids early then everybody starts "thinking" that way and before you know it, the world is stuck in a broken mindset.
Now, with an army of 5 million unknowing people committed to your platform, the people with experience don't matter anymore. You have strength in numbers, not in correctness or long-term viability.
It's also debatable just how many startups actually have much of the contemporary DevOps and data center infrastructure
Startups, yes. Actual companies, no. Most "real" companies (older than 8 years) have legacy infrastructure, physical data centers, and are only now realizing what 'cloud' (or OS-level VMs!) could mean to them (continuous deployment, automated testing, application isolation, reproducible infrastructure, etc).
Actually as an Erlang programmer myself (one who actually uses it as, among other things, a web dev language, no less...), I have no problem with Go existing, as I've always been a fan of Rob Pike's work and the Plan 9/Inferno vibe can definitely be sensed in it. It's the finalization of the small ALGOL-like + CSP concurrency model that Bell Labs researchers have been exploring throughout the years.
Moreover, it's one of the few languages so far that have a near complete POSIX/Unix-like kernel(s) API so that one can do straightforward system programming tasks without C, without even using libc, much less meddling with FFIs, lousy wrappers and whatnot.
Also, I'm pretty sure OS-level virtualization has been popular for a while now. Hosting companies have sworn by OpenVZ and even Linux-VServer for ages. However, those aren't as straightforward to configure, nor do they have the marketing angle that Rocket/rkt and Docker do. They're also more system-oriented as opposed to app-oriented.
On the other hand, being old means you can quickly spot how trendy magpie technical stacks map to old patterns that the industry has been consistently reinventing over time.
It's also debatable just how many startups actually have much of the contemporary DevOps and data center infrastructure as part of their standard workflow, as opposed to all the volume of buzz that goes into discussing it.