Colin Cornaby

@colincornaby
889 Followers
381 Following
4.6K Posts

I'm a programmer in Portland, OR doing video processing, graphics and performance on Apple devices. I'm into games, hardware and software.

Currently porting Myst Online to Apple Silicon/Metal as my side project!

GitHubhttps://github.com/colincornaby
Homepagehttps://colincornaby.me

It's clear that AI assisted coding is dividing developers (welcome to the culture wars!). I've seen a few blog posts now that talk about how some people just "love the craft", "delight in making something just right, like knitting", etc, as opposed to people who just "want to make it work". As if that explains the divide.

How about this, some people resent the notion of being a babysitter to a stochastic token machine, hastening their own cognitive decline. Some people resent paying rent to a handful of US companies, all coming directly out of the TESCREAL human extinction cult, to be able to write software. Some people resent the "worse is better" steady decline of software quality over the past two decades, now supercharged. Some people resent that the hegemonic computing ecosystem is entirely shaped by the logic of venture capital. Some people hate that the digital commons is walled off and sold back to us. Oh and I guess some people also don't like the thought of making coding several orders of magnitude more energy intensive during a climate emergency.

But sure, no, it's really because we mourn the loss of our hobby.

Forge federation is something we’re actively pushing for because of this. Full federation support is still a few years ahead of us, probably, but you can already set up your own forge in a way that minimizes inconvenience to users by using Codeberg as a single sign-on provider for a self-hosted forge.

https://git.madhouse-project.org/, which hosts the Iocaine project, is a great example of this. If you set up Codeberg as SSO for your own site, almost all of our content rules are irrelevant to you.

Yes, the Mac Pro is dead

[puffs cigar]

But I believe that the moment when Apple became unserious about professionals was in 2011 when they killed the Xserve

I had a Mac 128K (very) briefly in 1985, and an LC in 1991, but I went to the Mac - for good - in 1999 with the release of the Blue & White PowerMac G3. That was the pro Mac of the time, released soon after the Bondi Blue iMac made its debut. And I went there because Mac OS X was on the way. (I was a long-time NEXTSTEP fan at the time.)

B&W PowerMac G3 400, Quicksilver PowerMac G4 dual 800, PowerMac G5 dual 2.5 liquid cooled, and MacPro1,1 dual Xeon --- it was pro Macs for me over the years until they became aimed at a higher tier of u$er.

I am a Mac Studio user today, but I will always have very fond memories of those lovely and powerful pro Mac towers.

Pour one out for @siracusa tonight.

The 2019 Mac Pro is still a thing of beauty. If it hadn't had it's roadmap disrupted by the ARM transition - or if it got the rumored high end Apple Silicon - it would have been something.

Without GPU or RAM upgradability its days were numbered. MPX was supposed the be the ecosystem of the future but went nowhere.

I wish the Mac Studio was more upgradable. And I'll miss buying Macs that don't seem disposable. I'm already not sure how much RAM I should get in a Mac Studio. It's a balance between being locked in to what you choose, and now treating the machine as something you're not going to keep long term.

https://9to5mac.com/2026/03/26/apple-discontinues-the-mac-pro/

Apple discontinues the Mac Pro with no plans for future hardware - 9to5Mac

It’s the end of an era: Apple has confirmed to 9to5Mac that the Mac Pro is being discontinued. It has...

9to5Mac
Xcode 26.4 is out, and it contains one nice small thing for Clang users: the Apple Clang version numbers finally correspond to the upstream Clang versions. (Apple Clang 21 is based on the Clang 21 release branch.)

One weird thing about the Swift/C++ bridge is that Swift types get bridged into C++ as value types. But they're not value types, they're still reference types. What you're actually getting is a shared_ptr sort of thing that just holds the retain/release references.

But that also can mean they mix poorly into places that expect reference types. I have a template type that templates on references. But I'm having trouble templating on the Swift type because it's a value that acts like a reference.

The weird thing is - at least for the materials - if that was the original intention of the artists they absolutely could have been rendered that way without DLSS5. The non DLSS5 scene is full of metallic textures. This isn’t preserving the intent of the asset artist at all.