Had a friend in college who was redoing nuclear decay calculations written in Fortran so they’d work as C++/C# libraries. The calculations had been a historical standby for decades, and people were coming up with increasingly elaborate daisy-chains of dependencies to get them to work properly in modern environments.
There’s definitely a point at which the physical hardware and modern network/interfaces need you to catch up your code with the current technology. But there’s also this terror around trying to touch code that’s got an archaic datestamp on it, particularly if you’re working in a language or dealing with a particularly baroque procedure where the guy who wrote it retired 20 years ago.
Old doesnt mean bad.
Unreviewed Code is bad code unless proven otherwise. Maybe that latest iteration really is time tested and bulletproof. Or maybe Microsoft Execs simply won’t allocate time/money to the kind of routine review and maintenance a codebase needs from time to time.
“I converted my studio into a 3 story mansion and the foundation sunk into the ground. The foundation is still solid, it’s just the 3 story mansion that’s the problem.”
A foundation that can no longer support what it needs to support is not a good foundation and should be replaced
Most mobile devices use ARM processors, a tech developed by Acorn in the early 1980s.
Old doesnt mean bad. If it ain’t broke, don’t fix it
Had a friend in college who was redoing nuclear decay calculations written in Fortran so they’d work as C++/C# libraries. The calculations had been a historical standby for decades, and people were coming up with increasingly elaborate daisy-chains of dependencies to get them to work properly in modern environments.
There’s definitely a point at which the physical hardware and modern network/interfaces need you to catch up your code with the current technology. But there’s also this terror around trying to touch code that’s got an archaic datestamp on it, particularly if you’re working in a language or dealing with a particularly baroque procedure where the guy who wrote it retired 20 years ago.
Unreviewed Code is bad code unless proven otherwise. Maybe that latest iteration really is time tested and bulletproof. Or maybe Microsoft Execs simply won’t allocate time/money to the kind of routine review and maintenance a codebase needs from time to time.
Found the person never having to use Win32.
ARM was based on 1975’s MOS 6502, star of the NES, Apple ][ and Atari 2600.
And c64 :')
…and PET…
It kind of annoys me that ARM is a second order abbreviation. IDK why.
Surely there’s an acronym where the A stands for ARM, which would be sure to annoy you even more.
Except it broke
Later additions have broken it, the foundation is still solid.
“I converted my studio into a 3 story mansion and the foundation sunk into the ground. The foundation is still solid, it’s just the 3 story mansion that’s the problem.”
A foundation that can no longer support what it needs to support is not a good foundation and should be replaced
A better analogy would be that the mansion fell down but the foundation is still standing. Because the foundation is the solid part.
Sure, If there are no better alternatives and competition.
RISC is the Alpha of the CPU field.