We had a 7300 and it was pretty much one job at a time (submitted as card decks). The printer could push out a case of paper in under a minute. Shutting the printer down on a runaway job was perhaps the most exercise the attendants ever got.The CDC mainframes we had at Purdue in the 1970s had everything in memory and peripheral processors tapped into the memory pool to move data out to printers, tapes, and disks. The OS ran on a PP as well, basically managing a list of running programs and telling the CPUs which part of memory the instructions were located.
I'm not so concerned about the notebooks, but flexibility in the desktops would seem to be a real problem. Then again, I may be underestimating what people try with their notebook computers.The rumor mill has Apple releasing a 12-core SoC for the MacBook Pro 16 in 2021 with larger memory support and a better GPU.
I'm not so concerned about the notebooks, but flexibility in the desktops would seem to be a real problem. Then again, I may be underestimating what people try with their notebook computers.
I'm using the Xcode development tool and my code is written in Objective C. Swift is a newer Apple programming language that I haven't bothered to look at yet.Are you using XCode or Swift? Apple seems pretty intent on having all development for their platforms using these tools.
If you wrote code that followed all the rules, and then the rules were torn up and you were told to follow new rules, I can see why the third time that happened you’d wonder why you were jumping through hoops to support a minor platform.
On the other hand, I see a company like Serif who have both Windows and iOS versions of their Applications in addition to macOS and they are supporting M1 native code at launch.
Given how the memory footprint of browsers has grown over the years, I would personally go with the 16GB model. At the moment, FF is using 2.5GB of RAM on my mid-2015 MBP 15 with just 4 tabs open. Safari is probably better, but Chrome is definitely worse.The whole 8 Gigabytes vs. 16 Gigabytes question is one reason I haven’t pulled the trigger yet. But most of the reports so far seem to indicate that what I plan on doing with my new MacBook Air, 8 GB would be fine and I should save my $200.
The battery life improvement is the primary draw for a new Air M1, not performance. I see there are people trying to run the Folding at Home distributed computing application and they’re running into problems. I would load the Control program, not the actual compute client, but IMHO the FAH developers are not going to code an Apple Silicon client for the CPUs or GPUs anytime soon. They have enough problems keeping the back-end servers running to support a new, unproven architecture.