XPost: misc.phone.mobile.iphone   
   From: jollyroger@pobox.com   
      
   On 2023-10-02, Alan Browne  wrote:   
   > On 2023-10-01 23:15, Frankie wrote:   
   >> On 1/10/2023, Alan Browne wrote:   
   >>   
   >>>> The only way Apple can lower the heat output is to lower   
   >>>> performance.   
   >>>   
   >>> Not at all.   
   >>   
   >> You believe in miracles.  You don't remember the pre-and-post   
   >> benchmarks with iOS 10.2 it seems.   
   >>   
   >>> What it means is after the bug fix is that the benchmarks will be   
   >>> pretty much identical.   
   >>   
   >> Apple will greatly chop performance as it was with the iOS 10.2   
   >> "fixes." Apple "fixed" that problem the same way Apple's going to   
   >> "fix" this one.   
   >>   
   >>>> Apple sold an inherently untested product which turned out to be   
   >>>> defective.  The benchmark results are on that defective product.   
   >>>   
   >>> In any new product and OS release, the chances of bugs is pretty   
   >>> high no matter how much testing was done.  These are consumer   
   >>> appliances and there are too many undetermined (undeterminable)   
   >>> cases to test them all.   
   >>   
   >> It's obvious that Apple only tested for overheating after it blew up.   
   >> Same as when the battery issue came up. It couldn't have been tested.   
   >>   
   >>>> It's fast. But too hot.   
   >>>   
   >>> See above.  Threads can be very fast and very unproductive.  Fix   
   >>> that and life goes on.   
   >>   
   >> Maybe you don't remember how Apple handled a similar issue in the   
   >> past.  What happened in the past, is what's going to happen in the   
   >> future.   
   >>   
   >> Nobody should buy oveheating iPhones until we see all new benchmarks.   
   >   
   > You're talking out of your hat.   
   >   
   > I used to write real time programs for a living.  It is all too easy   
   > to make mistakes and have a section of code run in circles doing   
   > nothing productive but consume power.  Fix that bug, and life goes on   
   > and no limits to the product are needed.  In a multi-threaded   
   > environment (and iOS is decidedly such), it is even easier to make   
   > such errors and harder to detect them.   
   >   
   > I guess Frankie=Arlen?   
      
   Might as well be. Both are woefully ignorant when it comes to software   
   and systems development.   
      
   --   
   E-mail sent to this address may be devoured by my ravenous SPAM filter.   
   I often ignore posts from Google. Use a real news client instead.   
      
   JR   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)