Multiple Displays on a Mac Sucks
So many people I’ve worked with have used multiple displays – typically a matched pair side-by-side – and sworn by them. It’s always mystified me, to be honest.
macOS 15 Sequoia had a hard time with CoreStorage – and thus encrypted HFS+ volumes – since it deprecated both technologies and callously crippled some important tools for working with them, but nonetheless it mostly still worked. While I’d often – but not always – have to manually unlock one of my HFS+ volumes –……
Visit wadetregaskis.com → RSS feedOn Hacker News Apr 2024 – Nov 2026
Systems & Performance 3Software Engineering 3Web & Frontend 1Tools & Productivity 1Life, Learning & Writing 1Hardware & Electronics 1
So many people I’ve worked with have used multiple displays – typically a matched pair side-by-side – and sworn by them. It’s always mystified me, to be honest.
A few weeks ago, Axel Roest published a simple web server comparison , that turned out to not be doing what it was thought to be doing. Figuring that out was a very interesting discussion that warrants a retrospective, to look at which parts were particularly helpful and which not so much.
macOS 15 Sequoia had a hard time with CoreStorage – and thus encrypted HFS+ volumes – since it deprecated both technologies and callously crippled some important tools for working with them, but nonetheless it mostly still worked. While I’d often – but not always – have to manually unlock one of my HFS+ volumes – but…
In absolute terms they don’t have much overhead – think sub-microsecond for most uses. Which makes them perfectly acceptable when they’re used sporadically (e.g. only a few times per second).
NSCopyObject is a very old Foundation function – pre-dating Mac OS X entirely; from the NeXT era – that was originally basically just memcpy , but now it’s complicated. A lot more complicated.