I wouldn’t argue with him though. Middle-ware is necessary but not sufficient for an application stack.

It was also born in a time that lacked the maturity of other platforms, in my opinion the ability to provision resources dynamically.

It can be called cloud, or software-defined, or whatever one chooses.

Introducing another layer of complexity into the stack doesn’t solve the original problem.

Everything-as-code practice and general purpose languages are of great importance in the time of….

The real purposes of this post

I propose terming this time period of computing general ubiquity (GU?).

We see technologies are generally ‘stable.’ They are in a period of contraction (evidenced above).

Core technologies aren’t on the brink on the foreseeable limits. Most scale problems are solved but horizontal/parallel use of (now) the technologies that (were) developed in the previous time of non-GU.

The drive for cost is pruning the tech-tree.

The time period of general ubiquity (GU?) is marked by: contraction, parallelization, and stability (QoS, performance, costs). The GU period is marked by the introduction of some ‘game changing’ technologies. These game-changers are major leaps usually found and discussed in the non-mainstream. The periods during their introduction are marked by resistance, push against (throwing shade), or downright emotional response. This occurred around 2005 and then in 2012.

Evidence is the link above. This would have been lambasted by technocrats ~2-4 years ago, because those who supported it were in the lenses of the previous period of non-ubiquity. So they were mentally-vulnerable to a shiny object.

GU- versus non-GU.

Find the markers.

Back to the link

In 2012, I was trying to figure out how development environments could be more portable.

Yeah, exactly. Everyone else was struggling with everything else the same way. Not limited to just portable, but re-usability, and consistency across everything.

issues with SV and HR

No comment on this one.

The sudden change

Non-GU.

The real problem with Docker is a lack of coherent leadership.

This isn’t the first time a failure of leadership has been documented to cause a fall.

the brand’s cool factor that fueled its wild success.

Bubble.

It is said that, “Great civilizations are not murdered. They commit suicide.”

Respect, learn, study, respect more, then build upon, in that order, the lessons of the past.

Find the markers.

The 90’s was also a non-GU period. BBS’s and 56k protocols were still in flux back then.

UPDATE: This link here, they GET IT. https://outrunchange.com/2011/11/05/the-computing-pendulum-has-swung-back-to-dumb-terminals-and-service-bureaus-%E2%80%93-will-it-swing-back/