The specific case is code that is technical debt for *two* steppings
(B and C2) of *one* instance of a CPU (P54C). There's no need to keep
that around, especially since, as pointed out in the CL, it's causing
trouble.
I +2'ed the CL based on this discussion.
On Wed, Oct 6, 2021 at 5:27 AM Peter S
ron minnich wrote:
> same applies to new software applied to antiques.
While you are correct for some software and some antiques I find this
premise completely unacceptable. This attitude may be convenient for
developers but it only further normalizes planned obsolecense. Not OK!
Software can mak
2 matches
Mail list logo
