Posts by spireite 669 publicly visible posts • joined 15 May 2015
When i went to the affectionally named 'Nobby Green' school (S41 Newbold area of Chesterfeild), I cut my teeth on BBC Bs and Commodore PETS. BBC used rimarily for Chuckie Egg and copious minutes of Revs and Elite.
My first homer was a C64, andf then I graduated to mudslinging to ST owners at college when I had an Amiga 500.
Happy days of linking by cable with friends for Stunt Car Racer, Populous et al...
Completely overlooking the fact that customers are currently pinned in because they can't get off the driverless bus towards a cliff in the short term.
Rest assured those same customers are probably all bringing migration away to the top of the to-do list.
When that time comes to pass, Broadcom will see VMWare revenue drop off the proverbial cliff with the bus, but the passengers will be safely off it.
Yes, but isn't it the case that these are multi-year contracts?
If that is the case, then you've just received a few windy days, before the hurricane really rolls in.
No amount of storm chasers will save you when the bulk come in for renewal later.
Some will renew, simply because they haven't yet got a plan to migrate in the short term.
They will have one long term for sure, unless your product has no competitors.
Some will (are?) treat it as a priest no matter what, and listen to its ramblings.. much like a regular service then!
Many would argue, and I will poke the bear (not the kids), that it has more intelligence than those who go to Church regularly and then think it does them good.
I'm now going to hide in a corner and see the results of stirring the Jesus Hornets.
I keep arguing this.
Conversation runs like...
Moving on-prem SQL to Azure- we'll save money.... ha, yea right
Want to get data in it? Use ADF - while the rest of us want to be agnostic - Aitflow/Prefect/Mage etc... to avoid that lockin
Of course, after a few years, moving from Azure (or any other cloud) back to on-prem - or to a competing cloud is damn night impossible, or very costly.
This - you are not wrong.
My background in MSSQL highlighted this..
In MSSQL, (for those that didn't know).generally you could detach the DB, then attach it to the newer version and stuff would just run pretty painlessly. It would default to the 'compatibility' of what it came from, and you might want to update statistics etc.
When I was lumbered with Postgres and needed to upgrade, it felt like I was pulled back 20 years.
For some reason , many believe it stands for Artificial Intelligence.
For me, my usage suggests it should stand for Artificial Incompetence.
After all, if it cannot correctly tell me how many Rs are in Strawberry (or others), then why should it be trusted to write your code/analyse your docs??
Given Dockers recent announcement where they are lifting the cost of licencing by 50% ?? , people should be leaving in droves.but we know many won't.
It has become so ubiqutous that many devs can't see outside that box. So, alternatives like Podman still remain almost a 'side project' for many.
The reason this does not happen more often is 'money'....
In the long run , it will save money, but many C-suites/beancounters look at the fact that in the short term they don't believe migration work is productive, and therefore an unnecessary expense.
They are wholly incapable of looking at long term.
Meanwhile the techies who have to maintain the current POS are costing significantly more that the migration would in real terms. The C-suite can't see that though.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
