Ghostalmedia

Re: on by default

IMHO, the problem isn’t that it’s on by default, it’s the fine tuning of the feature. The velocity and pattern needed to trigger it + the lack of a reasonable max scale.

MacOS has had this on by default for a decade, but it feels more intentional when it appears. Meanwhile, I litterally still see KDE threads from people trying to troubleshoot “bugs” about their cursor size.

The KDE cursor needs about 15 min of a motion designer sitting next to the engineer that coded this.

Been in Mac OS since El Capitan (10.11.0) in 2015

• sent from my fax machine

Got it. Removing RAM modules now.

IMHO, the other part of the problem is that spicy hot-takes quickly get engagement from other users and bubble up to the top. And a lot of those spicy comments are trash, but not in violation of rules, so mods leave them up.

I’ll take my experience out of the picture. If you google Mac and PC enterprise costs, or total cost of ownership, you can find a ton of enterprise studies on this.

Usually the big problem with MacOS is whether it supports the damn software the organization / department needs. And by support, I mean native, not through a janky emulator.

TCO, has been compelling for decades. Folks often report longer lasting workstations, fewer tickets, and less malware. ¯\_(ツ)_/¯

Your wife’s experience sucks, but having done IT for sizable orgs in the past, my experience was that OS X and Apple’s hardware usually needed less coddling than the various Windows machines. Although they did have some lemon OS releases here and there, and those fucking keyboards from several years back were the devil.

Any OS is going to have anecdotal horror stories. If you want to get a real read on reliability you really need more than a sample size of 1. You need scale.

I agree, Apple’s quality has definitely slipped. I’m just saying that most of the code likely OG iTunes. They’ve been pretty public about throwing out old tech stacks and rearchitecting that app to support new hardware architectures, new frameworks, new service architectures, etc.

Weird, I had no idea that features was buried in there. I’m going to use that thing. That’s pretty cool.

I just played around with it and was able to reproduce the bug. If you get to Info via the meatball menu in the now playing panel, track specific audio controls are disabled. But if you get to the info panel via the meatball menus in playlists and album lists, it works fine.

My guess is that this feature probably isn’t getting a lot of regression testing because it’s probably not being hammered on by lots of folks. To reproduce this you need to be a power user going through a specific workflow.

I don’t think there is much of that legacy code floating around. Apple has been pretty public about rewriting that client. 2 years ago they also killed the parts of the app that were basically web content. Browsing the catalog is now a fully native experience.

If you’re having playback issues, you may want to post something to one the Apple communities here. That not normal.

This is a post from the future, after MacOS temporarily jumps to a whopping 2% after it gets its yearly single port of a 5 year AAA old game.

Death is going to have to walk down a reeeeally long Hallway before they get to Windows.

Thank you sir. May I have another?

Thank you sir. May I have another?

What if I don’t want to use whatever I want? What if I want my distro forced upon me?