Hacker News new | ask | show | jobs
by jonhohle 1006 days ago
Crippled in what way?

Others point out Homebrew, but I still prefer MacPorts for command line tools. It feels more “BSD” to me, while Homebrew reminds me of some tools a Node developer would write (cheeky terminology, overuse of emoji, cleverness over correctness, etc.).

At home I just use macOS and FreeBSD and many of my personal projects typically build on both. The base userland tools are mostly the same, but the non-POSIX stuff diverges heavily (file system control, process isolation, configuration, etc.)

1 comments

When I need to install some random program, I can't just create a container and build it. Instead, I need to install a pile of random dependencies, and then homebrew, macports and xcode all fight with each other.

Also, the MacOS window manager is objectively terrible. "Move window to right of screen" involves a keypress, trackpad hover, and menu selection. "Maximize window" doesn't exist. "Minimize window" makes the window inaccessible with command-tab and option-tab. Neither of those keyboard shortcuts function properly if there is more than one monitor plugged in.

Fractional scaling breakages still exist.

The font renderer is de-featured (vs the open source ones) because it is working around some expired patents involving true type hints.

It can no longer open postscript files.

I could go on for a long time.

MacOS makes a passible dumb terminal for accessing remote development environments though. It also integrates in well with iOS, etc.