Live data from Hacker News

Apple will announce move to ARM-based Macs later this month

theverge.com

151–160 of 174 posts

Re: Apple will announce move to ARM-based Macs later this month

#151

Earlier quoted context omitted.

You can run your own code on an iPhone if you have a developer account. They could easily do the same for the Mac.

...for 7 days. Then you have to plug your iPhone back into your Mac and re-compile the software and reinstall it. It’s an extremely shitty limitation that Apple put in place to give the appearance that they allow sideloading.

They don’t claim it’s to allow sideloading.

Re: Apple will announce move to ARM-based Macs later this month

#152

Earlier quoted context omitted.

> And Apple needs a development platform, for people to develop iOS/macOS apps on, and for its own OS developers to use in developing iOS/macOS. Have they shown developers much respect in the past? You can't even compile for the mac on other OSes, from what I hear.

> Have they shown developers much respect in the past? I totally agree Apple is not the most developer-friendly company, and I wish they'd focus on developer needs more. They should copy a page out of Microsoft's book and take Steve Ballmer's "developers, developers, developers" to heart. > You can't even compile for the mac on other OSes, from what I hear. I can compile Windows software on Linux or macOS using MinGW…

Why would you need mingw on a Mac?

Re: Apple will announce move to ARM-based Macs later this month

#153
post #152

Earlier quoted context omitted.

> Have they shown developers much respect in the past? I totally agree Apple is not the most developer-friendly company, and I wish they'd focus on developer needs more. They should copy a page out of Microsoft's book and take Steve Ballmer's "developers, developers, developers" to heart. > You can't even compile for the mac on other OSes, from what I hear. I can compile Windows software on Linux or macOS using MinGW…

Why would you need mingw on a Mac?

Suppose you have an application written in C, which is designed to be portable to macOS, Linux and Windows. Using your macOS laptop, you can compile it and run it under macOS. You can also compile the Windows executable from your macOS laptop, although you still need to move the executable to a Windows VM or machine to actually test it. But it means you can at least check your code change compiles correctly for Windows (which does have various differences in APIs, headers, etc) without actually having to go the Windows machine/VM.

(You might try testing the Windows executable under Wine on either macOS, or even a Linux Docker container with Docker for Mac – however, that doesn't work well in practice, because Wine is full of bugs and gaps, and a lot of the time the executable doesn't work properly under Wine due to Wine bugs/gaps but works fine on real Windows. So you still need the Windows VM for testing. But you can stay away from it during compilation.)

Re: Apple will announce move to ARM-based Macs later this month

#154

Earlier quoted context omitted.

I think the worry is a locked bootloader.

That and Apple being able to introduce security via obscurity means we'll probably never see a non-Apple OS on the platform.

It's already quite difficult and unideal to install a non-Apple OS on a Mac, aside from Windows via Bootcamp. Not being able to install a custom OS is a long way from "not owning your hardware". Apple OSes are part of the sum package; if you don't want that, you aren't the kind of person who's buying Apple hardware in the first place.

Re: Apple will announce move to ARM-based Macs later this month

#156
post #154

Earlier quoted context omitted.

That and Apple being able to introduce security via obscurity means we'll probably never see a non-Apple OS on the platform.

It's already quite difficult and unideal to install a non-Apple OS on a Mac, aside from Windows via Bootcamp. Not being able to install a custom OS is a long way from "not owning your hardware". Apple OSes are part of the sum package; if you don't want that, you aren't the kind of person who's buying Apple hardware in the first place.

3-4 years ago it wasn't difficult at all to replace macOS with pretty much any EFI-enabled OS. Moving to a proprietary ARM CPU/GPU will probably result in not being able to write applications unless it's using Apple's toolchain. If you have no say over what software you can run on your computer, you no longer own that computer.

We really haven't seen such a large technological separation like this. At least back in the old days you could still run what you want.

macOS moving to the iOS route where you have to jailbreak your device to get any sort of usability out of it is not a space I want to participate in, and yet it seems that's how the entire Apple line is moving. They're almost the complete opposite compared to Microsoft these days.

Re: Apple will announce move to ARM-based Macs later this month

#157
post #154

Earlier quoted context omitted.

It's already quite difficult and unideal to install a non-Apple OS on a Mac, aside from Windows via Bootcamp. Not being able to install a custom OS is a long way from "not owning your hardware". Apple OSes are part of the sum package; if you don't want that, you aren't the kind of person who's buying Apple hardware in the first place.

3-4 years ago it wasn't difficult at all to replace macOS with pretty much any EFI-enabled OS. Moving to a proprietary ARM CPU/GPU will probably result in not being able to write applications unless it's using Apple's toolchain. If you have no say over what software you can run on your computer, you no longer own that computer. We really haven't seen such a large technological separation like this. At least back in t…

As long as developers continue buying Macs for building non-Apple-native software, there will be ways to get them to run whatever you want, because that's required for a dev machine. If Apple ever decides it no longer cares about selling Macs to developers, well, I guess that's a possibility but it would be incredibly stupid, because that's a significant fraction of their current market.

Re: Apple will announce move to ARM-based Macs later this month

#158
post #152

Earlier quoted context omitted.

Why would you need mingw on a Mac?

Suppose you have an application written in C, which is designed to be portable to macOS, Linux and Windows. Using your macOS laptop, you can compile it and run it under macOS. You can also compile the Windows executable from your macOS laptop, although you still need to move the executable to a Windows VM or machine to actually test it. But it means you can at least check your code change compiles correctly for Windo…

Ah, ok. Fair enough, I misunderstood what you were trying to do.

Mingw on mac is evidently in homebrew. I've never used it, no idea how well it works. I don't write Windows software if I can ever help it.

Re: Apple will announce move to ARM-based Macs later this month

#159

Earlier quoted context omitted.

And they'll continue to say that right until the moment they yank the rug out from under you when all the pieces are in place.

The trop that your logic falls into is there's no way to disprove Apple will ever do this . 10 years from now, we'll probably be having the same argument, and people will be pointing to the latest release of macOS and complaining that surely this one means the end is nigh.

But there is an easy way to prove that they will and that 10 year horizon is short enough that I believe it will happen. Apple never cared about developers, they care about moving units and profits. Right now they are not getting a slice of the action of all software sales for the Mac and that must be a temptation they find hard to resist.

Remember how they turned their backs on the creative people that kept them alive for over a decade when everybody else had switched to windows? Similar story, similar ending.

Re: Apple will announce move to ARM-based Macs later this month

#160
post #158

Earlier quoted context omitted.

Suppose you have an application written in C, which is designed to be portable to macOS, Linux and Windows. Using your macOS laptop, you can compile it and run it under macOS. You can also compile the Windows executable from your macOS laptop, although you still need to move the executable to a Windows VM or machine to actually test it. But it means you can at least check your code change compiles correctly for Windo…

Ah, ok. Fair enough, I misunderstood what you were trying to do. Mingw on mac is evidently in homebrew. I've never used it, no idea how well it works. I don't write Windows software if I can ever help it.

> Mingw on mac is evidently in homebrew. I've never used it, no idea how well it works. I don't write Windows software if I can ever help it.

Well, it works just as well as MinGW on Windows does. If something isn't working with MinGW on macOS/Linux, it isn't going to work in MinGW on Windows either.

And MinGW on Windows works pretty well, but occasionally you hit some odd problems you might not have had with the Microsoft SDK (e.g. [1]).

[1] https://stackoverflow.com/questions/57885666/mingw-localtime...

Post reply on HN