From: ldo@nz.invalid   
      
   On Tue, 4 Nov 2025 06:18:02 -0000 (UTC), David LaRue wrote:   
      
   > On Tue, 4 Nov 2025 04:56:39 -0000 (UTC), Lawrence D’Oliveiro wrote:   
   >   
   >> On Tue, 4 Nov 2025 04:41:48 -0000 (UTC), David LaRue wrote:   
   >>   
   >>> If the tech builders weren't forced to use upgraded technology the   
   >>> support could stay stable for many generations of products. Often it   
   >>> was suggested/demanded by the developers because some tool in the   
   >>> newer cycle eased the job of the developer.   
   >>   
   >> Even if the developers of the product didn’t want to use Windows 11,   
   >> what are they supposed to do once Microsoft says it’s not going to   
   >> support Windows 10 any more?   
   >   
   > You first need to know what your products depend on in say Win 10.  Then   
   > use only those Win 10 features or older that are supported going into   
   > Win 11.   
      
   Doesn’t matter what features you do or don’t use, you still have to test   
   everything just as thoroughly. Which, in heavily-regulated, safety-   
   critical fields like industrial control and healthcare, can be a pretty   
   expensive business.   
      
   Which brings us right back to where we came in: the companies offering   
   these upgrades want to charge hefty fees for them.   
      
   The users could have seen this coming, decades in advance, given this is   
   not the first time such a situation has occurred with some version of   
   Microsoft Windows. And plan their long-term support contracts accordingly.   
   That’s the way to cushion the blow.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)