News for hackers. Stuff that matters.
Re:Remembering Unix Desktops – and What We Can Learn from Them by steve1977 on Sunday January 28, 2024 @05:30AM (#39164283)
How is not enough memory or storage a problem of the operating system?
Re:Remembering Unix Desktops – and What We Can Learn from Them by walterbell on Sunday January 28, 2024 @05:48AM (#39164374)
Problem of the macOS licensing model, which mandates excessive margins for bundled memory and storage.
Re:Remembering Unix Desktops – and What We Can Learn from Them by danieldk on Sunday January 28, 2024 @08:10AM (#39165354)
I usually bought a Mac every 1.5 years or so, because I liked being on the cutting edge. However, I am now still rocking a 2021 MacBook Pro 14" because it's still great. In half a year the model is about 3 years old. When I purchased it, it was close to 3000 Euro, and it has 32GB RAM and 1TB SSD.

If I'd sell it, I'd still get between 1000 and 1500 Euro. Let's say for the sake of the argument I get 1200 when it is three years old, then the yearly cost was 600 Euro. Which is... cheap for a tool that I use daily and my income depends on? I mean, if I had to drive by car to work, my yearly cost would be much more than 600 Euro.

I would readily agree that Apple overcharges for memory and SSD, but the amortized cost is not really large.

Re:Remembering Unix Desktops – and What We Can Learn from Them by Thri4895o on Sunday January 28, 2024 @09:15AM (#39165976)
If you depend on this machine for living... You should have a spare machine. Way to recover data very fast if it breaks.... Way to fix it... It gets expensive pretty fast.

Also if you travel with Mac, you need to carry two laptops. There is no easy way to move NVME drive to new machine like with Pc laptops.

Re:Remembering Unix Desktops – and What We Can Learn from Them by danieldk on Monday January 29, 2024 @03:15PM (#39181859)
Ehm, why? What you are saying does not make sense at all. I do hourly incremental backups to fast blob storage. If my Mac breaks, I can pick up another one and be back up and running in no time. The other good thing is that it doesn't matter where I buy it or go for repairs, since Apple has great worldwide service.

Besides that I never had a Mac break down when I travel and I've owned MacBooks since 2007 and travelled a lot with them (including years of daily bike rides, including hilly terrain).

My MacBook is one of the products I literally never worry about.

Re:Remembering Unix Desktops – and What We Can Learn from Them by yencabulator on Monday January 29, 2024 @11:57AM (#39178670)
Meanwhile, my Framework laptop from 2021 has twice the RAM and storage, was significantly cheaper, and runs an even more unix-like graphical environment.
Re:Remembering Unix Desktops – and What We Can Learn from Them by danieldk on Monday January 29, 2024 @03:10PM (#39181801)
But it doesn't have macOS. And that's where we started at: macOS is popular, because it's a great graphical UNIX.
Re:Remembering Unix Desktops – and What We Can Learn from Them by Thri4895o on Sunday January 28, 2024 @05:51AM (#39164395)
Because the operating system only supports devices with limited memory and storage.

I would love to run macos on my beefy workstation. But MacOS support for AMD Ryzen sucks.

Re:Remembering Unix Desktops – and What We Can Learn from Them by Aaron2222 on Sunday January 28, 2024 @06:20AM (#39164574)
It's not that Mac hardware is only available with limited memory and storage (you can get a MacBook Pro with 128 GB of RAM and 8 TB of storage, or you can get a Mac Pro and throw in a bunch of M.2 drives on PCIe cards), it's just that the pricing on them is ridiculous.
Re:Remembering Unix Desktops – and What We Can Learn from Them by steve1977 on Sunday January 28, 2024 @07:39AM (#39165113)
But that’s not a problem of macOS.
Re:Remembering Unix Desktops – and What We Can Learn from Them by pdpi on Sunday January 28, 2024 @08:14AM (#39165395)
It's not a problem of macOS in the strictest sense but we're talking about highly vertically integrated platforms. You don't get macOS without a mac, so it _is_ a macOS problem in that sense.