Quote from: The Heretic on December 18, 2020, 19:27:37
For most people, unless you are a pro/prosumer content creator of vids/photos/audio or someone like that, the speed advantage of a faster CPU platform is maybe not worth the cost...
I imagine people usually don't buy an Air to do heavy lifting. The performance is a nice bonus, but it's really the battery life that is of primary interest to me. It's really shame Apple didn't use a more efficient display.
Yes, you've got to keep in mind that native software is still coming and emulation might not be perfect. It's the first generation. But Apple is pretty good at driving developers to support new platforms. Anyone committed to Mac should get there sooner or later. If you're running on it only macOS, I think you can make the leap of faith. Unless you really need some obscure software where it's doubtful they'll support M1 anytime soon and you don't want to take risks with emulation.
I believe there is work being done on bringing x86 virtual machines to M1, but who knows when it will be available, how well it will work, what the performance will be like. Technically, it's feasible. But you need to build an emulator and that's not trivial. So, at this point, if you need x86, you should stick with x86 (but I would probably look for MBP13 for SW development and the like). There is also the Windows on ARM which will probably come officially at some point. Whether that's useful depends on whether what you need runs well enough on it.
While I use virtual machines a lot, emulated ones are of little interest to me. Fortunately, I write my software to be easily portable (of course, it gets more difficult with platform specific APIs). Even if I currently use only one platform. Exactly because it doesn't tie me to it. If I want to run something on an x86 machine, I can just connect to it remotely. And if I'm in a cottage in the middle of a forest with no connection to the Internet, I can just bring a box with me. You might get away with something the size of NUC. Often, I can get away with postponing the testing on another platform - develop on one and then just verify it works as well on another later. That way, I don't need constant access. It depends on what you do. I sometimes travel with three or four computers (not counting tablets). Besides questions from other travelers, looks from security personnel and squeezing into weight limits for carry-on baggage (as you don't want to check-in computers), it's not a problem for me.