3 ms·
Two highlights for me that were useful: 1) keep expectations low in terms of compatibility. Most non apple apps will take time before they are ported to run na
by xiwenc 6y ago
Two highlights for me that were useful:
1) keep expectations low in terms of compatibility. Most non apple apps will take time before they are ported to run natively on M1
2) related to point 1, the great battery life being marketed is not applicable if your apps arsenal is not native yet.
These two might sound trivial to some but i did not think of them initially. I was ready to get the M1 if there’s a good deal next weeks. But now i’m not sure.
What are your thoughts?
- mirthflat83 6y agoIt’s not that hard really. Just look up if the apps you’re planning planning to use has battery or compatibility issues. https://isapplesiliconready.com/ https://isapplesiliconready.com/ I personally have not experienced any issues and the M1 is a marvel. Also, the return window is through January. I sure as hell am not going to return mine.
- S_A_P 6y agoTo point 1- some native Mac apps are not Big Sur compatible yet. It could be 2 separate issues. I held off from upgrading to Big Sur on my audio/daw iMac Pro for this reason. 2- claim seems slightly dubious as it depends on the app. Some translated software is more cpu intensive than others. So maybe? Just like the native stuff will be.
- ianai 6y agoI’ve used some non optimized stuff and it didn’t seem to hit the battery. I’d be curious if people are tracking this somewhere.
- qppo 6y agoIf you're doing audio production you should never upgrade MacOS immediately. I get almost as many emails from developers telling me not to as I get notifications from Apple telling me to upgrade. This has been true for at least the last 15 years, MacOS upgrades always screw something up. Usually iLok
- S_A_P 6y agoabsolutely- and I never do. Was mostly stating that there are legitimate reasons to not upgrade and that some software doesnt work with the latest OS that isnt necessarily related to M1.