![]() I was bummed at first they didn’t release a new mini but after thinking about it, this is exactly the machine I’ve wanted for a very long time, especially since I used Mac laptops for most of my career but they were in clamshell mode most of the time. I’m more excited about the increased “bandwidth” I’ll have and not having to worry about closing apps/tabs all the time. I already saw insane jumps going from my maxed out 2016 15” MBP to the base M1 mini so I’m not worried about more speed (even though I’ll take it). I feel confident this will be a machine that lasts me fro several years (which is why I signed up for the perpetual apple care option) and should just make everything I do smoother if not also faster. I also run 2 4k displays which may also contribute to the issue. However, the memory demands of my daily needs seemed to just continue to climb which is why I’m most excited about the 64 GB memory. The mini was fine when it came out although the Java VM for Android was super heavy and I had to run docker on a remote machine. I purposely bought the base model mini when it came out because I knew I’d want to upgrade once they came out with something like the studio. I work on front end web apps, backend server apps, and mobile apps for Android and iOS. My M1 Max Studio w/ 64 GB RAM arrives on Monday to replace my base model M1 Mac mini. Oh, I should also specify we’re giving devs who work at this scale 64Gb RAM minimum which is why we recommend the m1 max. And since there’s no tangible difference between the Max in the MacBook or the Studio, we’re giving devs the MacBook for versatility reasons. We’ve discussed the studio and the m1 Ultra, but our developer tooling team has asserted that we’d see diminishing returns from the increased memory bandwidth, and the rest of the gains are in multi core performance, of which the Max already offers in sufficient quantities to meet and exceed the current demands of our codebase. Most devs don’t even see their fans turn on unless they’re compiling frequently back-to-back. The M1 Max handles our flow pretty handily and allows for plenty of additional apps running without stutter or freezes. ![]() What we’ve found is that a good deal of our mobile pipeline on Intel machines was limited by single threaded performance and memory bandwidth. We even have distinct grade flavors and cocoapods for different subsections of our app just so that we don’t have to sync the IDE with the entire codebase all at once. We have multiple enormous repositories with thousands of internal and external dependencies. So the company I work for develops mobile apps at a fairly ridiculous global scale. Looking forward to reading your experiences. Since I'm working from my desk at home already for years now, I'm thinking I need more power 99% of the time and I can always use the MBP when on the road. The fans are going insane, WindowService is pulling 20% CPU already when not even doing anything (I guess some MacOS bug when running my 4K monitor). ![]() With my MBP 2019 with my 4K monitor, I just create a meltdown. I'm talking about running Docker with like 8 containers running, having heave applications open all the time, such as Datagrip, Goland and Visual Studio for Mac, listening to Spotify and at the same time compiling Android / iOS app, running simulators, in the mean time being on a Slack video call while having 200 tabs open in Firefox. I'm more interested in using the machine as a software developer. Some people love it, some people wonder if that is worth the price tag. I see a lot of people looking at the Mac Studio and post about it trimming a couple of minutes from their rendering time.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |