Virtualbox Mac m1

oliver_berger wrote:

Valid questions. If they do not resolve this fast a lot of people (me included) will choose a different hardware setup in the future and just run a Hackintosh for their MacOS needs.

Which, if found out by Apple may lead to a very costly Court appearance and whatever the Lawyers fees involved. That is before any Court decisions of guild or innocence on the charges,

Considerably more that the cost of a new Apple M1 computer

Barney-15E wrote:

It isn't particularly useful. I've got one I almost never use. Occasionally I tap the OK button when I enter a PIN because it is right there. It never provided any value for me. That's why it is dead.

I had the problem that I use the ESC key frequently and moving a finger toward the ESC key brought it close enough to activate whatever was on the left side of the touch bar, and there's no way to reduce the touch bar's sensitivity or shut it off altogether.

Exactly. That’s a pretty big capability to lose. In my dreams we’d have mbp with Intel cpu, 64GB ram and GeForce gpus for machine learning.

This current crap is making think about going elsewhere for my new laptop and that’s upsetting cause their hardware is my problem. I feel like this M1 thing is a bad decision

For people like you, Dell or HP anxiously await your business.

For those who just want to get a job done or who develop for iOS or macOS, the M1 is a minor miracle, freeing Apple from Intel’s delayed timelines and the heat budgets that caused past MBP 16 owners to complain incessantly about fans.

I’m thrilled with the increase in performance and lower heat generation the M1 Max brings.

I’ve never needed to run x86 VMs on my

iPad, and I don’t need to on my MBP.

Oh ya, remember Touch Bar? How about dumb chicklet keyboard? These things come and go. Rosetta v2 is v2 for a reason, Apple already did this like 20 years ago and went back to Intel.

Lol, guess we’ll see where things wind up in a few years. The M1 doesn’t seem ready for developers not focused on iOS or MacOS dev.

I’ll buy a 32GB MBP from Apple refurbished site next and wait 3 more years and see.

I wish Apple was more upfront with all of these shortcomings instead of acting like they totally solved all of the problems, this makes customers lose trust in Apple.

Apple didn’t “go back” to Intel.

The very first Macs were based upon the Motorola 68000 CPU.

That was later replaced with processors based upon the Motorola/IBM PowerPC architecture but the processor transition was somewhat painful as you needed to procure new applications that would work on the new processors.

When Apple decided to switch from PowerPC to Intel, the first version of Rosetta was introduced to allow execution of PowerPC binaries on x86 to ease the transition to Intel, as it would allow most PowerPC binaries to run on x86 Macs.

With the transition to Apple M, Rosetta v2 will ease the transition to that architecture.

You keep thinking the primary audience for Macs is developers of any type, and that’s not necessarily true, it’s anyone who needs to get work done without having to put up with Windows.

The vast majority of Mac users are not developers in any way.

Again, how was Apple less than straightforward about the shortcomings you describe when the article I linked to was first posted in March, 2021?

Of course Apple continues to make a variety of Intel Macs - the 27” iMac 5K and the tower Mac Pro are two notable examples - but both of those will someday transition to Apple silicon as well.

You’re right, I guess changing things so dramatically created this response in me. I need to work the way I do, and so do many other developers.

If you don’t research enough you’ll find yourself unable to work holding a brand new laptop, cut off from capabilities you didn’t necessarily think you’d be missing!

I agree, that’s why it’s amazing Apple offers their 14 day refund policy.

You can order a maxed out $6K MBP M1 Max, and Apple will gladly refund you in full even if you don’t like the feel of the keyboard.

Dogcow-Moof wrote:

I don't know why there would be an issue with VMWare given Parallels proudly advertises Windows will run on their product for Mac, either x86 or Apple Silicon, provided you have the appropriate version of Windows, of course:

Hi @Dogcow-Moof,

For sure, Windows for ARM runs on Parallels, and they make it easy by automating the process to get the necessary Windows Insider images, but the licensing is a bit "iffy" as technically Windows ARM is only licensed by Microsoft for distribution through OEM's who preload it ONLY on ARM machines based on Qualcomm CPU's.

By manually downloading the Windows Insider images, and with a bit of help from QEMU (to do the VHDX to VMDK conversion) you can get it to run in vmWare Fusion too, but there are currently problems with networking that need to be resolved.

Since vmWare don't officially support running ARM Windows in Fusion (probably due to the Microsoft/Qualcomm ARM license situation) its not clear if they will add the installation helpers that are in Parallels, and fix the network driver issues any time soon. There are however some workarounds involving the kernel debugger which I've read about, but haven't investigated/verified.

Thanks for the link to the docker docs. I read this and still have some pretty solid questions about why.

How can any serious developer use an M1?

I write ansible playbooks, run/build docker images locally and do lots of dev using node, python 3.7.4, dotnet, postgres, blockchain (Cardano, solana) and more. What I’m saying here is that Apple can’t predict the usecases that developers use their mbp’s in.

If I can’t use x64 VM’s locally and can’t use docker for the most common software components out there how can I work?

Again, I’m stating this as a huge Apple fan, I love all of their products (except HomePod). Most developers I know prefer MacBook Pro’s too, some even use bootcamp and windows.

These new M1’s aren’t even close to capable of supporting most developers needs.

Apple is famous for creating amazing hardware and software combos, no vendor has come close to this.

I feel like the lack of x64 architecture is a step too far too quick. It’s like Apple gets into an argument with companies like Nvidia and bam, only AMD graphics, this hurts developers options for machine learning cause CUDA is the most flexible and widely adopted.

I realize I’ve been ranting about this for a while now. Sorry. I just haven’t seen a single person agree, unless they purchased one and found all of these shortcomings themselves.

Well, I agree and I'm actually a bit unnerved at the way Apple is scaling back things that support business users as well.

I believe Apple thinks that everything should be done "in the cloud" (as SAS and HaaS is more lucrative than allowing privately run servers). And maybe they now see the future of the Mac as more of a thin client.

I started programming in the 70's on a mainframe and up until the last maybe... 5 years, the available tools, the internet, and technology were always expanding. Every year there were more and more things an individual could do and create. But lately, since the idea of cloud computing and SAS has taken over, the opposite is happening. Big-Tech is slowly squeezing us into doing things "their way" (with a monthly fee).

The voice of the shareholder is much louder than the developer (or the end users). Rather myopic in my opinion.

I'm worried that it is beginning to stifle creativity.

dangoulet1 wrote:

How can any serious developer use an M1?

Because you assume “serious developers” all develop in the way you do.

• Anyone that develops for iOS or macOS uses Xcode, which works out of the box and generates binaries for both x86 and Apple silicon.

• People who develop for other operating systems often already have procedures they use that continue to work as before as they connect to other machines or launch other instances via local tools or remotely after using ssh to login to another system. None of that has changed.

Thanks, my feelings exactly.

I always run the systems I create in the cloud but I develop them locally often not using cloud tools.

Development workflows are usually local with deployments to the cloud.

I feel like Apple is leaving us developers out again so they can lock people into their ML, CPU’s and such. It’s such a shame cause I love Apple products and this will change.

dangoulet1 wrote:

I feel like Apple is leaving us developers out again so they can lock people into their ML, CPU’s and such. It’s such a shame cause I love Apple products and this will change.

Again, you keep making "developers" a monolithic group, so no, Apple is not "leaving developers out."

If you really feel that way, feel free to pick up generic PC hardware.

I personally work with hundreds of developers on a regular basis, and the ones with an M1 MacBook Pro have zero issues because none of them work the way you do.

Hundreds?? Come on man. None of the developers develop and execute their code on their local machine?

You work with hundreds of developers working on M1’s? Does that mean you work at Apple? Lol.

I love how you try to blame me for saying I expect to accomplish the same types of tasks with a newer version of the same product.

Do these hundreds of developers you work with just use XCode?