On: Hackintosh is almost dead

[viraptor]

> Why build a Linux box and be locked out of tools like Photoshop

That's what VMs are for. You're never really locked out. It may not make sense to go that way if Photoshop is THE thing you work with of course.

> when I could have UNIX workstation that ran commercial software

Because for lots of software MacOS is a second class system. Partially because there's just no way to test things on it without investing lots of money in hardware, so many people don't.

If you're doing lots of sysadmin / software maintenance style work, MacOS just provides unnecessary pain.

[macintux → viraptor]

> That's what VMs are for.

For me, the psychic angst of using Windows is much, much worse than any Mac-related inconvenience.

[sbuk → viraptor]

> If you're doing lots of sysadmin / software maintenance style work, MacOS just provides unnecessary pain.

Amazingly a significant amount of the software that you use on a daily basis, perhaps unwittingly, is developed and maintained with macOS and Windows!

[viraptor → sbuk]

I'm working on packaging things for Darwin platform. And helping people deal with homebrew/compilation issues. I'm painfully aware how much is developed by people with no access to or interest in MacOS. And unless something targets windows explicitly (not wsl), you can basically expect issues going in. In a twisted way, I'm one of the enablers of the current situation where things are usable on a mac.

Sometimes you can tell by the simple fact that the git repo contains files in one directory that conflict in naming. Linux has no issues with "Foo" and "foo" coexisting.

[pjmlp → viraptor]

Nothing to do with Linux, and everything to do with case sensite filesystems common on UNIX.

macOS uses case insensitive filesystem by default for backwards compatibility with HFS+.

You can turn case sensitive on HFS+ and APFS if so desired for the "Linux" experience, via Disk Utility or the equivalent CLI tool.

And if looking to have some fun on an ecosystem that doesn't expect it, you can equally turn it on on NTFS, via fsutil.

[cesarb → pjmlp]

> > I'm painfully aware how much is developed by people with no access to or interest in MacOS. [...] Sometimes you can tell by the simple fact that the git repo contains files in one directory that conflict in naming. Linux has no issues with "Foo" and "foo" coexisting.

> Nothing to do with Linux, and everything to do with case sensite filesystems common on UNIX.

Of the three major desktop operating systems (Microsoft Windows, Apple macOS, and the Linux family), only Linux has case sensitive filesystems by default. Therefore, it's likely that someone who didn't care about filename case conflicts was running Linux.

[pjmlp → viraptor]

Indeed, why get a lesser experience with Linux laptops, when I can use Apple and Microsoft platforms, and use Linux in a VM when I really need to.

The Year of Linux Desktop is delivered on a desktop VM.

[viraptor → pjmlp]

If that works for you, great. My default works better with Linux with only occasional other system. Makes me least angry. (Also because Linux is the only system that handles sleep/hibernation for me without issues, ironically...)