![]() ![]() When it came to Big Sur and the Apple Silicon rollout, our team couldn’t qualify our gear until we had production hardware and software in hand. Apple has a nasty habit of hiding incomplete or broken functionality and quietly fixing it at some point in the future. Our hardware and software teams worked with the chipset manufacturer to resolve the issue until one day the iPad behavior spontaneously fixed itself following an iPadOS update. Everything else worked fine except the small stack of iPads in our office. I’m a hardware guy who spent several months this year fighting with issues enumerating iPad Pros with our gear. ![]() I’ll share some recent real-world experience with Apple. #Mac mini monitor plugin mac#Apple OS betas start in June at WWDC and the new OS gets released in the autumn like clockwork, for what, 10-15 years ? If you really can’t plan your workload around that and it always comes as a disruptive surprise, maybe you shouldn’t be in the business of making commercial Mac software. I have zero sympathy for the guys who got caught out with their 32-bit only software on Catalina and pointed fingers at Apple who gave them TWO years notice to do a 64-bit migration that was a thing on macOS for ELEVEN years ! Sorry again, that’s cool if you’re a one man shop but if you’re a team with an engineering manager it’s just part of their job to not wait until the s**t hits the fan. When you say “large mature codebase”, do you mean “I’m using frameworks that have been deprecated for 10 versions and have tech debt as high as the Everest that I never get around to fixing”. ![]() I don’t think that’s the case for most of those who are complaining, let’s be honest !ĭidn’t have the money for a dev kit ? Not as easy but you could still have done the bulk of the work and cross-compiled for ARM until your build passed, and by now you would have had a good chance that it just worked. And you shouldn’t have that many arch-related issues anyway, unless you have handcrafted assembly, do weird things with memory or use tons of binary-only frameworks. Except you would have started 5 months ago. You could have had your ARM dev kit since June and have solved 100% of architecture-related issues with it *just as well* as you can do with a production M1 today. So unless you’re VMWare or Docker, sorry, you don’t get to use that excuse. There is exactly one feature that production M1 Macs have that the dev kit CPU didn’t : hardware virtualisation support. ![]() I actually have 20 years experience in software dev but that’s not even needed to fact-check your reply. So, it’s quite possible that Apple will release in 2021 those amazing machines with M2 chips which can have a whole lot more RAM and a lot of ports. Two Thunderbolt ports is fine for some needs but we can easily imagine scenarios where a lot more would be needed. But there are cases where loading huge libraries in RAM might be essential. Sure, RAM needs are surprising a lot of people as being lower than on Intel chips in equivalent use cases. There’s also the stuff about RAM and ports. I love my MBAM1… and have been experiencing hard crashes, even to the extent that it rebooted itself unattended. Performance can be extremely important in some situations… and we’ll have to assess how robust and reliable that performance can be in stressful situations. In #MusicTech especially, Intel Macs are likely to remain relevant for a while. Wouldn’t be that quick on the first part. It feels almost unhealthy how much of a difference in my life this MBAM1 makes. But ‘Apple Silicon’ is starting to look like one of those ‘game changers’ that actually lives up to the term.Ĭheck out the video and share your thoughts on the new M1 Macs in the comments! Most will not want to switch to an M1 Mac until developers and software have a chance to catch up to the new systems. “But at present only really in true native mode can you expect this kind of performance.” “This little computer packs a lot of punch for the price,” he notes. He tried a variety of tests, creating 111 tracks with 444 voices and 555 plug-in instances (native) before the machine slowed to a crawl. In the video, host Nick Batt takes a look at the cheapest of the M1 Macs, a Mac Mini with an 8-core CPU, 8GB of RAM and 256GB hard drive. The introductions have upturned expectations for MacOS computers, because the M1 system-on-a-chip is optimized in ways that desktop users are not used to, and the company’s bottom-of-the-line Macs based on the new M1 perform at a level that beats or at least competes with last year’s top-of-the-line maxed out systems. The latest Sonic State Sonic Lab video takes a quick look at the new Mac Mini, one of Apple’s new entry-level MacOS computers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |