It got me to buy my first Mac, at least (iMac). I figured if OSX didn’t work out I could just run Windows on it.
Maybe ironically, the new ARM Macs make me a little hesitant to buy a new MacBook because I’d be pretty much locked in to OSX (with all due respect to the Asahi folks who are doing great work - I fear Apple is going to pull the rug out from under them though.)
I don’t think so. There’s been support for “other OSs” from the start with the M line. I was actually pleasantly surprised by this.
I don’t think they will change their minds. It brings value to the platform while offering little threat.
I think we’ll be seeing a boot camp version of ARM Windows as soon as Microsoft solves its licensing issues.
> "Okay, it's been over a year, and it's time to end the nonsense speculation."
> "I have heard from several Apple employees that:"
> "1. The boot method we use is for 3rd-party OSes, and Apple only use it to test that it works, because"
> "2. It is policy that it works."
> "Hacker News peanut gallery, you can drop the BS now. It's not an "assumption" that this stuff exists for 3rd-party OSes. It couldn't "be something internal Apple uses that could go away any minute". That is not how it works, it never was, and now I'm telling you it's official."
> "And this isn't even news because @XenoKovah (who invented and designed this entire Boot Policy 3rd party OS mechanism) already tweeted about this whole thing a long time ago, but apparently it needs to be restated."
If Microsoft don't port Windows ARM to Macs, Apple might decommission the "core technologies". Even if they do, there's nothing stopping Apple from changing their mind down the lane, like they have already done on other topics, whatever the intentions of developers that developed them were.
Ultimately it leads to a discussion about the competition. When you buy an ARM based Surface, can you put Linux on it? Is Microsoft clear you can? Are they providing drivers?
> Besides, even if Apple did come out and say it, you'd still trot this nonsense out.
No. Apple saying, unofficially, they welcome Microsoft, and Apple coming out and saying they love Linux and want it, would be different. That wouldn't be any guarantee that they won't change their mind or are just hypocrites, but it would still be more meaningful than "technically it's possible, there is no official anything (only an official welcome to MS Windows, but sure, Apple absolutely want Linux on Mac to be a thing".
Between my big Linux desktop and M1 Macbook Air I'm not even sure what to do in Windows anymore. I don't need to run any Windows applications per say, and everything I do really need runs on MacOS. I still have a VirtualBox Win10 install on the Linux box, but honestly I'm not sure why, besides habit.
I don't think it's a coincidence that Intel Macs coincided with the release of Core/Core 2 Duo cpus. At the time there was nothing close to them by any metric. Remember Intel enjoyed a generational lead in foundry tech for decades.
You forget about Atom?
> ... Atom?
Indeed! The Motorola RAZR i was Atom-powered.
I then remembered why it was in the junk drawer.
The strangest part of that setup was that it used a 32 bit UEFI and a 64 bit operating system, so I couldn’t use regular Linux images. But hey, you could configure the UEFI settings using only the touchscreen!
Naturally the battery life was terrible and it lasted fewer than 12 hours in sleep mode, so it spent little time outside the junk drawer too.
Atom based phones exist, but they're not good at anything in particular.
I don't think there's any reason X86 has to use more power than ARM - it's simply not the focus of most implementations, however. As I understand it, most processors at this point are an interpreter on top of a bespoke core. Intel used to get quite a lot of praise for low power consumption back in 2012-2015 with Ivy Bridge and so on - rather coincidentally, that was also when they had a process advantage (rather like AMD and Apple today enjoy).
But from what I’ve read, having different length instructions makes extracting parallelism way harder. That’s why Apple can make such crazy wide machines.
I wonder if we'll see Intel or AMD try to make another somewhat-backwards-compatible ISA jump to keep up with ARM.
x86_32 --> x86_64 --> x86_512?
But it is much easier to simply chop off a stream of instructions at every X bits than to evaluate a portion and decide what to do later and that difference get larger the wider you go.
Variable length instructions in general do have a code density advantage, but x86 is a particularly poor example. For historical reasons, it wastes short encodings with rarely used things like BCD adjustment instructions, and on 64 bits often requires an extra prefix byte. The RISC-V developers did a size comparison when designing their own compressed ISA, and the variable-length x86-64 used more space than the fixed-length 64-bit ARM; for 32 bits, ARM's variable-length Thumb2 was the winner (see page 14 of https://riscv.org/wp-content/uploads/2015/06/riscv-compresse...).
Yes, with the complexity and transistor budgets, the disadvantages of x86 can be somewhat glossed over, otherwise they would have vanished from the market long ago, but they add a certain overhead which cannot be ignored when looking at low power applications. The efforts the CPU needs to take until it can execute the commands is higher and x86 requires more optimizations done by the CPU than RISC designs. Which today also contain a translation layer, but a way simpler one tha x86, as the assembly instructions match modern CPU structures better.
It is probably no coincidence that Intel, which had to work around the issues of executing CISC code on a modern CPU chose the EPIC design for the Itanium. Which goes beyond RISC in putting compexity towards the code generation vs. on-cpu optimizations. Too bad it didn't work out - it might have, if AMD had not added 64bit extensions to x86. While there were certainly a lot of technical challenges which were never completely solved, the processors seemed to perform quite well when run with well optimized code. Perhaps they were just one or two process generations to early. While considered large for that time, their transistor count was small compared to a modern iPhone processor. I wonder how they would perform if just ported to 7nm (the latest CPUs were 32nm).
If you'd like to see some first-hand observations about modern-ish compilers on Itanic, check out this person on Twitter who does lots of development on Itanic:
Intel is like Mike Brady with his architectural designs that all look suspiciously like his own house.
They refused to compete with themselves and kept x86 as 32 bit so they could promote Itanic, and therefore lost the lead to AMD for years (it wasn't just 64 bit - actively REDUCING instructions per clock with Netburst was... well, legendary - just in a bad way).
It just so happened that the kick in the ass Intel got from AMD came a few years before Apple needed Intel, so Intel had finally started trying enough that they had a product line that would work for Apple.
But really, is Intel suitable for low power? Could anyone seriously imagine an x86-based phone? Their one-hit wonder is only barely keeping up with AMD and ARM when Intel throws hundreds of watts at their chips and turbo-clocks the heck out of them. Even though Ryzen has been showing up Intel for years, they've floundered so long that there was practically zero chance Apple could stay with them long term.
But even in 2005, Intel wasn't necessarily good - they just happened to be the least bad right then.