News for hackers. Stuff that matters.

A comment on Leaving htop running freezes macOS High Sierra. Parent comment

Re:Leaving htop running freezes macOS High Sierra by znpy on Friday January 05, 2018 @10:45PM (#16083726)
> For a ~$6k setup, it’s awful. It’d be awful for $1k. About 10 years ago, I had a Dell D830 running Fedora and later, early versions of Gnome shell. The dock powered the laptop and a mouse, keyboard, external drive, and two monitors. It was a single (albeit proprietary) connector, and the dock was fairly expensive (~$200 IIRC). It worked damn great, nearly every time, even with sleep States in Linux on a laptop 10 years ago.

And what did we learn here?

[ Parent | on HN ]
Re:Leaving htop running freezes macOS High Sierra by ethbro on Saturday January 06, 2018 @12:01AM (#16083938)
> And what did we learn here?

That I should pay Apple $10k for my next MBP so these features can work?

[ Parent | on HN ]
Re:Leaving htop running freezes macOS High Sierra by WWLink on Saturday January 06, 2018 @12:40AM (#16084031)
I dunno what you're whining about, I've had multi monitor setups on several mac laptops and they've always worked fine. Same on my desktop. Same on my work desktop. It's almost always more reliable than doing it on Windows.
[ Parent | on HN ]
Re:Leaving htop running freezes macOS High Sierra by codezero on Saturday January 06, 2018 @01:55AM (#16084205)
Ditto as I commented above, but I’ve heard these reports from lots of technical and smart people leading me to believe there’s a real reason. As others above have mentioned it sounds like laziness on the part of peripheral vendors, but it’s a bit surprising Apple doesn’t have a workaround that makes this not crop up.
[ Parent | on HN ]
Re:Leaving htop running freezes macOS High Sierra by wolrah on Saturday January 06, 2018 @12:37PM (#16086382)
> it’s a bit surprising Apple doesn’t have a workaround that makes this not crop up.

If the problem is in fact lazy device manufacturers botching the identification data then I'm not sure how a third party could effectively work around the issue.

If I make two devices that report identical ID information there's no practical way for the OS to tell them apart.

[ Parent | on HN ]