Yes, M1 is a exciting step forward for personal computers. But again, it doesn't make what we have today and still have to use less beneficial.
Well strictly speaking, it does make today's Intel Macs slightly worse. Normally Apple supports (with new OS upgrades and such) old Macs for around a decade. They don't promise any specific span of years though. Across CPU transitions this number drops a lot. So a new Mac Book Pro 16" purchased in 2019 you could expect to still be running the current OS in 2037 to maybe 2039. I expect it will actually not run a new macOS in 2035 now.
That may or may not be a big deal. Any given customer may only keep those Macs for a much shorter time period and replace them as newer better ones become available anyway. Or be on a "new every two" plan or something. Or the particular workload might be fine running on older versions of macOS for a few years anyway (lack of security fixes might be an issue though).
Over all though, yeah, the Intel computers purchased last year run exactly as fast this week as they did two weeks ago (except a statistically small percentage that broke in that time). They still do the same jobs they did before at the same speed.
It'll be interesting to see how passive cooling stacks up with continuous heavy load (e.g. iMovie export).
Apparently it takes a bit over ten minutes on....mmmm....it was a video export (I didn't do this test, I saw it on one of Rene Richie's YouTube videos), but not iMovie for the M1 MacBook Pro to spin up fans (and at that point they were apparently still very quiet, easiest to tell by putting a mic near the exhaust as opposed to listening with human ears). At that point it started having about a 15% performance advantage over the M1 MacBook Air. The Mac mini was still passively cooling and holding the same speed.
So I think we need a load heavier then video encode exporting to see a big difference! Maybe my next personal laptop purchase will not end up being a Pro, I might be happy with a 15"+ Air (if they make them, and if the M1 16" Pro doesn't have some other compelling things going on)
I mean, just think about Apple TV with an m1-style chip in it - will Apple finally try (post-Pippin) to compete with consoles for real?
Yeah, that would be cool...but Apple's real problem with video games isn't technical. Or maybe "isn't just technical". They don't put in the work to build the kind of relationship with the big video game makers. They don't push for big AAA exclusive windows/DLC. They focus on the "casual" market. Which might actually be a good strategy, but it isn't what you need if you want to be the next Xbox of PS(some-number). It also won't get you to be the next Nintendo Switch either (that needs a lot of focus on in-house game talent, and probably a decade or two to generate valuable in-house entertainment IP). Apple has the
money to do that kind of thing, but I don't know that it has the interest in doing that kind of work. If you see a new SVP of gaming (or any euphemism for that), then maybe. Especially if they hire someone with that kind of role away from MS or Nintendo.
At the technical level I have no doubt Apple could make something that does a great job, and even has the same sort of price point as the XBoc Series X or PS5. Although if they haven't been working on it since 2017 they won't be launching something like that in 2021.
I hope the CEO of Intel threw up when they read this. Hopefully this is enough to get Intel from continually sandbagging. Very exciting time in processors, this is going to push things ahead by leaps and bounds.
I doubt the M1 is making Intel's CEO happy, but the vomiting is coming from looking at AMD's performance numbers. There are a lot of moats between Apple making significant dents in Intel's business (past the non-trivial, but surely not more then 7% of CPUs that Apple has been buying from Intel to put in Macs). AMD on the other hand is a direct competitor to basically all of Intel's CPU business. They aren't socket compatible, but from the software layer they are a direct replacement, and even at the hardware level they are close enough for many many many of Intel's customers (basically any that actually design their own motherboards, as opposed to ones that just use Intel's reference designs, and even there AMD provides reference designs).
In other words the Apple M1 is like Intel's CEO accidentally hammering his thumb and not the nail. It is more then noticeable. It hurts. AMD is like a bandsaw accident. Probably not fatal, but it could be. It'll also be life altering.
Steve jobs never wanted macs to be user-upgradeable or serviceable.
Yeah, on the other hand Steve Jobs changes his mind (well changed). He was just as against having 3rd party Apps on the iPhone. That wasn't a front, it was real. Likewise he changed his mind about how upgradable Macs should/could be. Although a large part of that was thinking that it could be done at Apple Stores for people that wouldn't otherwise get any benefit from having a Mac with expandable memory because it is too hard for most people to do. Of corse the expandable memory one went away because it was an apple care call driver/major source of service repair (not just the result of doing a bad upgrade, but also just RAM working loose from sockets in portable devices, which is why the desktops kept it long after the laptops got rid of it).
Now, I understand that some folks want to know what the behavior of the systems will be when pushed to the edge, but “pushed to the edge” should in no way be confused with “day to day usage”!
Well some people have day to day usage that pushes machines to the edge. My common work load on the MacBook Pro hurts it for about an hour. If I had a newer MBP with 32G of RAM it is actually more like 15 minutes (I have coworkers with the newer model). Don't feel bad for me, I also have an iMac Pro, and normally arrange to do that sort of work there. I absolutely won't be attempting to get a new work laptop until an ARM system with 32+G is available.
I also have very little doubt that one is coming (not no doubt mind you, just very little doubt).
I can also afford to wait on that because I'm WFH for at least six more months, so I really don't do much of anything on that MBP.
iPad office is nothing but a gimped pointless version with 90% of its features missing. If you really believe what you have written here than you have no idea how to use a spreadsheet or word processor
I think a vast majority of people really do know how to use word processors and spreadsheets and really have no need for the vast majority of the features.
I write a lot of design docs in a word processor. I really don't need to do much more then import a template, brain dump. Copy and paste my word soup into more reorganized clumps. Rewrite to group related thoughts. Remove any "supporting facts" that actually lead nowhere. Maybe make some process graphs or some UML-ish diagrams and slap them in (we have some great tools to do that, so even if the word processor can make UML diagrams I would rather generate them from my actual data definitions). Occasionally I make some directed acyclic graphs and shove them in, and again I have nice tools to do that..although here I sometimes don't drive them from live data, so if a word processor really could do that directly I would have a modest benefit.
Oh, and spell check. Spell check is great for me.
That is a pretty small percentage of what modern word processors do.
Likewise my use of spreadsheets is simple. Mostly because the data I feed into them is simple, and my desires for them are simple. If they had much more advanced graphing I might sometimes get some use out of that. If they could handle vast data sets (like a half billion entries) I might get some value out of that, but that is debatable because I have other tools that are built into the companies data flow. So if I want the weighted moving average of some field and the spreadsheet didn't die when I dump that much data into it I would need to wait for the WMA while the tools we have compute things like that as they extract "in case" they are needed (they also live update some of those as data comes in because they drive alarms and other live production things).
I do know how to use a spreadsheet, I just really don't need much from them. Likewise most people who use spreadsheets don't need very many of the vast quantity of features they have.
Lots of people may need
different subsets of the word processor and spreadsheet features, but only a tiny minority of people need very many actual features from them.
[sorry double quoted this]
Linux has ARM support and the M1 can easily be supported. Microsoft could choose to support Windows on it. The T2 allows disabling its boot volume signature checks.
The M1 doesn't support disabling boot signature checks. However you can
sign your own boot images (self signed cert). I'm not sure that would work well for MS, not for someone wanting to make a M1 Linux distro. However Apple did show off a fully supported by Apple hypervisor with some M1 distros & also with Docker.
I think that would work well for a whole lot of Linux use. I'm not sure it is as valuable for Windows (i.e. it is more of a Parallels/VMWare solution for a hypothetical ARM M1 Windows image then it is a Boot Camp for M1 ARM Windows).
I hope something like virtualPC comes along and let’s me keep running my windows XP code.
Hmm, I think you might want to look at Bochs. It should have no problem doing what you want, although it probably won't make for a fast virtual XP machine.
A LOT of companies use Macs for development and a lot of them are dependant on VMs and virtualization like Docker
Apple did show off their own virtualization system including running ARM Docker containers (or are they called instances? I'm not a Docker user, sorry). The downside here being if you really wanted x86 Docker instances this isn't going to help (but isn't Docker a Big Deal because it is easy to run instances on various cloud services and in-house clouds? I'm not sure how important this is...then again almost all my Linux experience has been treating it as a generic Unix-ish system & I probably use it on the RPi more then on x86 as it is!).