Is this written by an LLM? It reads like it.

He isn't, but nearly everything he puts out there is AI produced. His video thumbnails look awful, and that task manager he built for macOS is fully AI coded. Not saying it's a bad thing, but I dunno it's kinda all ugly looking to me.

Every pixel is where I put it, so that's all that matters to me. If it's ugly, it's intentionally so. AI had no input into designing the visuals or UX.

Only sane response in this thread about this topic. Thank you.

It's both. Fuck DHH.

Holy shit, that blog post was insane. He's clearly a racist twat.

Has anyone been able to make this actually work as a macOS screensaver? I'm using Tahoe and when I go to System Settings -> Wallpapers -> Screensavers, I don't see any option to select like Afterglow or any of the wallpapers I installed.

Go to the settings in Afterglow first and enable it. Then in Settings Wallpaper tap the 'Screen saver..' button. Select 'Custom' and then scroll and it is the last item to the right in the 'Other' section.

Yes it works, but you need to enable it in the Afterglow settings first.

Not the point of the article but it did show a Bluesky post... I didn't know you could make the Apple Watch interface look different with a third-party app. I gotta try this out.

You are 100% spot on with this, not sure why anyone would disagree. The website is clearly AI generated.

I'm not trying to say it's not generated, I'm just saying that it doesn't stand out as offensive to me.

How so?

The parent didn't go into any detail. I can. Homebrew has a history of ripping out your foundation underneath you. One day you are on Python 3.8, then next day you are on Python 3.10 and all your packages are broken. MacPorts doesn't do that.

Now, whether you should you be using the Homebrew Python is a completely different question. YMMV for other platforms managed via Homebrew.

I've traditionally used MacPorts for dev tooling and Homebrew for everything else, but with more aggressive adoption of tooling like uv an nvm I'm not sure the different really matters for me anymore.

Exactly. Same with PHP, MySQL etc… Also they just block old versions and dont let you install them, you have to jump through a lot of hoops to use an old PHP version for example, so in no way developer friendly.

In the end I realized that Brew is a package manager for consumers, and as a professional i should’nt keep fighting it.

A lot of that is simply formula authors / application devs who don't know what they're doing (python@3.10 and other versions are a thing, and have been for quite a while now, but they're not always used and devs don't always keep track of the version they need) and people not updating their software for years (pythons are on a 5 year cycle everywhere, homebrew included: https://devguide.python.org/versions/ and https://formulae.brew.sh/formula/python@3.10 ).

Python in particular is well known to not be a stable target. For anyone. By design. If you expect long term use of a specific version of code, use a different language. It is not at all homebrew's fault that they're how many people discover that.

I use mise for dev tooling, that way I can have the exact correct version for every project.

Python through brew is the one I expect to be the latest one I use for one-off scripts.

I switched to mise too for all my dev tooling. It just works so nicely for all kinds of ecosystems. I can use the same tool for Python, Node, Java, whatever and it just works.

pyenv has been standard tooling for far longer than uv. depending on package manager supplied Python packages only makes sense if you’re running rhel or Debian or something and your application is packaged/deployed/the maintenance path uses dnf/apt. Otherwise you should always use a venv and use an out of package manager update mechanism. Like, in a broader sense, vendoring dependencies only makes sense if you’re shipping an application, not on a dev box.

This is not about python packages, this is about python itself.

That's what the GP means as well, you can use pyenv and uv to install multiple versions of Python and create envs with whichever version you want to use.

Would love to see Tandy DeskMate on here!

DeskMate in 1988 came with my family's first computer, a Tandy 2000 TX. One of the first mainstream consumer PCs with a 3.5" disk drive. (We had to later buy a 5.25" drive in order to share software--er, I mean data--with our neighbors.) DeskMate was marketed as, "Finally! No need to use complicated MS-DOS!" Of course, you couldn't _really_ use it for much, as MS-DOS programs of the time were much more powerful and interesting, but it was a nice tech demo I guess.