Re: Why Bloat Is Still Software's Biggest Vulnerability

 Don Y <blockedofcourse@foo.invalid> wrote:

On 2/15/2024 3:13 AM, Peter wrote:

Graet to see you Don after all these years - 2006!!

>
Hey there, Mr "Pool"  :>

Haha hello :)

The pump packed up; turned out that the 25uF (400V AC) starting cap
degraded to 15uF.

I trust all is well, remodel long completed, kids now grown
(which of them was first to make you "Gramps"?  and wasn't your
youngest looking for his pilot's license?), thus PBfH having
less of an impact on your life, etc.

Divorced the witch in 1999, then the next one (2003-2023) sadly ended
in 2023.

Youngest has a PPL (UK and FAA) and flies, both mine and his RV6.
Chases females on Tinder and Hinge, like everybody else :)

I had a customer many years ago who did write a ton of code in hex. To
enable modifications they had a bit of space after each function, so
edits to a function did not need shifting everything after it :)

>
But what was their *reason* for this?  I had an employer (*had* been
an engineer and deluded himself into thinking he could still *do*
engineering) who was stuck in the past -- as if the tools and
techniques he had used were still relavent, even a few years later!

Stupidity - assemblers have always been around.

When it took hours to assemble, link, burn images, it made sense to
have mechanisms to support minor tweeks to the code (overwriting
instructions with NOPs and filling in a "0xFF" postamble with new
code).  But, nowadays, make world on even large projects is just
a coffee break -- and, you can dump your code into RAM to watch
it run (assuming you have to run on a target and not in a
simulator).
>
[Nowadays, I netboot images just for the savings that one step
makes possible!]

Indeed.