4 ms·
Well, if the 74 in my username doesn’t give it away, quite awhile. But just to give you a hint, my first professional contract in college was writing a Gopher s
by scarface74 7y ago
Well, if the 74 in my username doesn’t give it away, quite awhile. But just to give you a hint, my first professional contract in college was writing a Gopher site. My first hobby projects involved writing 65C02 assembly in the mid 80s.
As far as IBM, if someone had chosen to get “locked-in” to IBM in the 70s, they could still buy new hardware that could run their old software unmodified. Isn’t that an argument for using AWS?
In the scale of decades, most of the time you will be performing heavy rewrites anyway, are you really trying to optimize now just in case in 20 years you might want to move to something else?
Are you using the same language and frameworks you were using 20 years ago? When I first started developing I was writing C programs on DEC VAX, Stratus VOS mainframes.
If you are just using AWS to host a bunch of EC2 instances and as an overpriced colo, sure you could find much cheaper options now.
No matter what you do, more than likely you will have to migrate. Just changing infrastructure if all you’re doing is moving to VMs on another provider, reconfiguring your network if you are using a hybrid, etc is going to be a heavy lift no matter how much you try to avoid lock in and you’re spending money now for an amorphous future where you may want to change vendors instead of using your vendor of choices features that can save you money and/or time.
I would make the same argument if we were talking about Azure or God forbid Oracle.