4 ms·

> The fact we're still discussing the trackpad, suspend/wake, fonts, networking, and UI - in 2017 - means the problem still isn't solved on Linux. One reason i

> The fact we're still discussing the trackpad, suspend/wake, fonts, networking, and UI - in 2017 - means the problem still isn't solved on Linux. One reason is, it's not Linux's problem to solve. It's the hardware vendor's. Those morons still don't ship with proper drivers, firmware, or even specs —possibly because spending a single cent on Linux isn't economically viable or something. Last time I checked, suspend and power management does work flawlessly on Linux… when the hardware is a couple year's old. But it will never work properly on new hardware unless the vendors make it so themselves. On the other hand, Wifi hardware vendors now often ship with proprietary drivers. Proprietary sucks, but it at least works. > I'll pay the $1000 premium and if I value my time at $25/hour, I'll recover that additional cost within 2 months compared to Linux maintenance. I wish it weren't so, but the maths don't lie. Let's be generous and assume MacOS requires zero maintenance. 1000/25 means 40 hours (a full work-week), of Linux maintenance. A full work-week in only 2 months, aren't you being a tiny bit hyperbolic? I spend a few minutes per month in maintenance.

idm 10y ago
Think of it like this: 8 weeks, 5 days per week, 1 hour per day. That's 40 hours. I spend more than a few minutes a month administering my MBP, so I have no idea how you get along doing so little for a Linux machine. In fact, I spend more than a few minutes a month administering my Linux servers... I honestly think my 1-hour-per-day estimate is in the ballpark and your experience sounds unlike mine.
- loup-vaillant 10y ago
  Maybe I'm just negligent, but I do have a remote server I spent a full week configuring (web, and mail, just for me, from ssh). I'm no sysadmin, I expect a good one would have needed no more than a couple hours. But I haven't touched it in months. It just works. (Or not. Lack of updates may have lead to vulnerabilities.) At this point I doubt we mean the same thing by "administration". To me, it means updating the system, fixing what doesn't work, and installing new programs. Spending en entire hour per day just for this sounds insane. Perhaps you had other tasks in mind? Also bear in mind that I'm currently using a "long term support" release of Ubuntu, on hardware I knew would be well supported (I've read a couple reviews). It's not Arch on a random laptop.

idm 10y ago

Think of it like this: 8 weeks, 5 days per week, 1 hour per day. That's 40 hours. I spend more than a few minutes a month administering my MBP, so I have no idea how you get along doing so little for a Linux machine. In fact, I spend more than a few minutes a month administering my Linux servers... I honestly think my 1-hour-per-day estimate is in the ballpark and your experience sounds unlike mine.

loup-vaillant 10y ago
Maybe I'm just negligent, but I do have a remote server I spent a full week configuring (web, and mail, just for me, from ssh). I'm no sysadmin, I expect a good one would have needed no more than a couple hours. But I haven't touched it in months. It just works. (Or not. Lack of updates may have lead to vulnerabilities.) At this point I doubt we mean the same thing by "administration". To me, it means updating the system, fixing what doesn't work, and installing new programs. Spending en entire hour per day just for this sounds insane. Perhaps you had other tasks in mind? Also bear in mind that I'm currently using a "long term support" release of Ubuntu, on hardware I knew would be well supported (I've read a couple reviews). It's not Arch on a random laptop.