this piece was an article relevant to that certain point in time. where at that time - java had slow velocity - because it was tied up in marketing speak - and

this piece was an article relevant to that certain point in time. where at that time - java had slow velocity - because it was tied up in marketing speak - and enterprise jargon. however reading in between the lines - languages or ecosystems that are not shaped up by hype / marketing to do tend to encourage faster velocity and an uncanny advantage. in this day and age though - maybe due to resume driven development - influx of vc funding. keep in mind - when YC started it was just a seeder fund - which encouraged companies to reach ramen profitability as soon as possible, not survive on the next round of funding. what you now experience in the present - is rubber gum / viscous velocity amongst startups due to marketing i.e things like k8s, cloud tools etc which reach the complexity of J2EE tools of back then; when only the appointed prophets could show you the right true path. now every company big and small - talks about doing things at scale. yet if you take a step back - no one has a definition of what scale is. at $job - the talk of scale is prevalent - yet we're reaching for tools to solve human problems. that wouldn't need tech at all. good luck finding a place that shuns complexity, isn't afraid of letting servers fail - to make sure they're robust and reliable enough. where the presentation layer - isn't going through a yearly ritual of sacrificing hours dealing with dependencies.