loopless

Thanks goodness. Although deployment with XCode has got much easier since the early days it is still painfully obvious that the whole process needs a rethink, and it should be much simpler for first time developers.

These lawsuits are total BS and AppleInsider should stop giving them such prominence. Especially with comments from people who think Apple should be producing a flip phone with a pop-out battery.

Users are unlikely to notice slowdowns - but artificial benchmarks will show issues and only with phones will degraded batteries. I would MUCH rather my phone slowed down bit than suddenly "quit". 

Lawsuit is rubbish. When the battery performance drops to a certain level the choice for Apple was to let the phone crash under heavy load ( aka artificial benchmarks) or throttle the phone. They made a choice most consumers would agree with. From my understanding a bad battery shows as yellow in settings. 

rob53 said:

tipoo said:

That's...Honestly not as high as I expected it would go! The tower Mac Pros and Power Mac G5s could get well into decent car territory. 

My only wish is it was more configurable, I need a lot of CPU for my big data workload, but Vega Pro is a wasted cost, while someone training Metal 2 neural nets would go max GPU. Hope the Mac Pro provides that ability to min/max different components. 

Maybe you need to look at your data workload and see if a change in program will allow you to use more GPU computing power. Most of the supercomputers are using GPU processing anyway so I'd look into your workflow and see what can be changed.

 
Wrong. Many algorithms are not suited to GPU computing. GPUs are not the be all and end all for HPC. Most HPC clusters are vanilla Linux box’s without GPUs. 

Actually x86 32-bit code is less efficient. 64-bit x64 code can take advantage of an instruction set with many operations not present in legacy x86 instruction set. But would a user ever notice - unlikely. Any computationally demanding code would have been 64-bit for a long time.