No, thank you, I'll keep a flawed x86 architecture. We could also stop writing shit software.
No, thank you, I'll keep a flawed x86 architecture. We could also stop writing shit software.
I used to think like that - until I analyzed all my PC builds over the last 12 years and realized with Intel changing sockets every generation the whole incremental upgrade thing was fond memories from the 80's, 90's and early 2000's. Once I realized incremental upgrades wasn't a hill worth dying on my choices increased and I've never been happier with the size/weight/speed/battery life that previous dogma prevented me from even evaluating.
>We could also stop writing shit software.
We could but people don't. Sentiments often don't survive contact with reality :p
To this day there still exists a cadre who think Apple users are idiots for spending so much money on a computer. Many of them have not seriously taken a look at what the platform offers and they do not fully comprehend why people choose this platform over others.
Regarding the "We could also stop writing shit software." quote, it seems as if there has been a wave of optimization over the last decade just out of necessity. (electron notwithstanding)
It is not enough, components that are written in fast languages such as the OS have generally gotten slower. We are forced to upgrade due to security and I don't see any incentive for companies to improve this part of the software stack. You can use other desktop apps that are faster but you only really have 2-3 choices in OS and that dictates everything else you can do with your computer.
Was running Windows 11 on the Parallels Desktop on M1 and it seems snappy but not as snappy as MacOS. I noticed this same behavior on Windows 10 running on a core i7. It seems as if the design of the OS has some bloat that I cannot explain clearly but can definitely feel. We should consider that maybe Apple has been also optimizing software to be more performant.
Alder Lake 2022.
They absolutely do. You can see it in all their bundled programs, too (except Xcode... sigh). Safari, Pages/Numbers/Keynote, Preview, Maps. All snappy and light on resources. None of them prone to slowing down unrelated things on your system. You can leave them open in the background for weeks and forget they're there.
There's also iOS and Android. Android's gotten better, but it's always needed more energy and faster hardware to approach iOS performance and UI responsiveness. The software's simply better, by that metric, anyway.
Another instance of this was visible in BeOS vs. Windows/Linux, back in the day. The difference was not subtle and was present even when running cross-platform programs, so it must have been BeOS itself (and its libraries, SDK, et c.) responsible for everything feeling way faster and more responsive.
A significant portion of this is just requiring more efficient developer tools.
- Generational GC vs ARC memory management accounts for a large (50-100%) increase in memory usage
- JIT vs compiled code performance impacts
- Swift value types vs Java (and Objc) class types removes further memory management pressure as well as allowing for significant memory savings.
- The underlying OS model Apple has restricts the need to run code from multiple applications at one time to a small set of extension points. Android does allow for background processing (although you can't guarantee consistent/persistent processes).
Of course you give all this up when you are just wrapping your javascript + web content up in an electron or similar framework. In that case, you are running at a fraction of the efficiency of either platform.
Hardwired storage is horrible from a data recovery standpoint also, you should be able to take our your storage chip and try to recover data from it in a standalone fashion as long as you know the encryption key, even if your main board or CPU has been damaged.
Their storage and RAM prices being double the market price is also irritating.
Yep. I still have desktop machines and build another every 4 years or so. I used to upgrade machines, but it's just not realistic anymore. If I'm very lucky I'll manage to reuse the case and power supply, but even that's iffy. Stuff's changing too fast, including, as you mentioned, processor sockets. Memory, too. Man, I had some memory in the 2000s that lived through like 3 different machines. Not these days. If I upgraded video cards more often I guess I might manage to do that once per machine, but that'd be it.
Buying entire new computers is the most wasteful thing you could do, both money wise and environmentally wise.
There is definitely value in SOC for CPU/MoBo (maybe memory), but the other components work better upgrading at different rates.
They've been on the same couple sockets for a long time now.
Processors/Motherboards not as much, maybe once every 5 years or so.
Apple really seems all about throw away culture.
Then go for it - you have choices, and no one is forcing you to buy a Mac.
I personally got shit to do and have no interest in replacing all of that at that type of frequency.
Just because Apple computers before last a long time doesn't mean it will be the same with their current computers.
Although my personal bet is that the 2016-2019 MBP will degrade faster than the 2020 M1 Macs.
I have tried giving older Macs to other family members, that didn't work out so well. So there are limits.
In general, used Macs have crazy high resale value, and if they work out ok, no problem with that. Both ends of the transaction receive value from the exchange.
I am in the process of clearing out quite a bit of e-waste, but we are talking fried PowerPC Macs and some iPhone 4 devices that I cant get working again. I have noticed that the Macs tend to be physically smaller than thier counterparts from the same era in my collection; that might suggest less e-waste overall, but of course the variation is all over the place.
The oldest operational x86 machines in my setup are two tower Mac Pros, a 2007 one and anither from 2009. These are somewhat upgradeable: you can use SSDs instead of rotating rust (duh), max out the RAM (easy), put in newer GPUs (drivers and BIOS permitting), or max out the CPUs (you need a moderately weird tool to get at the heat sink screws).
The fate of our electronics is indeed worthy of concern, but I don't see that Apple approach leading necessarily to more trash.
(oh yes: I am typing this on an ipad 4. I'd love to keep using it for another 14 months, it will then be ten years old. but it's getting a bit unreasonable. Works for hacker news though)
My assumption your approach is far more wasteful at a cost of getting top notch performance. Nothing about the bleeding edge is ecological.
Just to clarify though I don't replace all those components every year, it usually ends up being one or maybe two things a year. But if I do one component a year my system can end up lasting indefinitely.
If you can get by on a decade old machine all the more power to you. Professionally I cannot.
It still received the most recent OS updates.
Battery life is not as good at 8yrs - but still has a few hours of juice in it.
Overlooking the butterfly keyboard fiasco, Apple makes robust long lived hardware, and software to support it.
It’s market does not include the 3% “piecemeal” upgraders. But I suspect in “amount of time component is use” metrics it handily beats the wintel world (and the Android world)
The main difference that I see is that the M1 chip is much faster and more power efficient than the systems it replaced (as well as much more expensive systems, for that matter; see M1 Air vs. Macbook Pro). I suspect that means that people who buy the M1 systems that Apple is selling won't replace their laptops as soon as people who bought x86 versions.
Your point is taken, but this is a trend that Apple has been moving towards regardless; it's not something that's new to the M1 Macs. You haven't ever been able to swap out your motherboard or processor in a Macintosh with very few exceptions (including the Xeon Mac Pros), and we've yet to see what an M1 (or M2 or whatever) Mac Pro would look like, expandability-wise, anyway.