I’ve seen it successfully happen due to licensing costs and cloud migration (MSSQL->Spanner), as well as for scalability reasons (vanilla postgres->cockroach). The first one was a significant change in features, the latter did sacrifice some native plugins. In the first case the company was using vendor specific features, and rewrote the backend to fit the new vendor.
There’s vendor agnosticism, and then there’s platform agnosticism. Writing your code so that it’s not tied to one specific implementation of postgres is fine, and lets you use a compatible drop-in. Writing your code so you can swap MSSQL for Oracle or Aurora or whatever at will does not make sense. In every case of attempted platform agnosticism I’ve seen they ended up abandoning the project within a year or two with nothing to show for it.
If you remove the speeches from Trek, don’t you just end up with the kind of content everyone seems to be complaining about in JJ-Trek?
Would you say that the layman’s metaphor for this is like the brain suddenly living in a drafty house?
Corral, but put it there properly, not all askew as it it was a bloody kitchen drawer.
Plus other capabilities like injecting banners, caching, etc
Is rubberbanding still a significant issue? I used to play but took a break after the Iconian season. Then I tried going back around the time the new Terran season came out, and combat was very frustrating for to lag.
Sulphur is what comes to mind.
deleted by creator
Dredd and John Carter. In both cases the film was tanked by marketing (or lack thereof).
So TCP ACK is the backwash?