We also got stuck with XML-based project files somehow, despite .NET Core/.NET 5+ being a complete rewrite.

Claude is a buggy mess because it's slop, not because it's electron. Heck, it runs a full Linux VM under the covers without asking.. it's insane.

We're lucky to have a handful of big Doug Firs, Sitka Spruce, and Western Red Cedars left on Vancouver Island.

[1]: https://en.wikipedia.org/wiki/Big_Lonely_Doug

Where I work, a senior would be reprimanded for such behavior. A key metric to their success is how well they can transfer knowledge and teach others, and their peers' feedback is used to determine this.

The senior that "punches down" does not go far in this case.

While they don't _prevent_ Asahi from doing what they're doing, they certainly don't go out of their way to make it easy for them.

Apple has pretty good competition in every segment with the exception of maybe the iPad, but I'm not a tablet user.

If you are comfortable building a custom PC and fixated on the spec sheet sure, it's not that exciting. But there are some rough edges with PC couch gaming that are sanded off with this machine.

The G5 was actually the last Mac I owned until buying a Neo just for giggles.

As other commenters have pointed out, cooperative multitasking is actually a great fit for I/O bound code.

I did consider experimenting with the Routines feature on the desktop app, but I'm leaning towards whipping together something with cron. I saw another poster here who has a daily PR summary routine that I think would be handy, as I have quite a few repos where I'm a sporadic contributor but would like to keep tabs.

The issue is folks expect this to be at a higher level, so when libc or GTK or Qt etc. have breaking changes, all your apps using the old versions fail. This is a legitimate pain point with traditional distros.. I don't want to sound like I'm downplaying it.

However, this is basically solved by flatpak (and others like it, eg snap) which contain _all_ these dependencies in the package. Layering (ala containers) is used for deduplication so you don't have 20 copies of a given GTK version.

While MacOS provides the windowing toolkit etc. at the OS level, it's otherwise similar to how a .app file works. Installers aren't dropping dynamic libraries and resource files all over your disk, the app is "self-contained."

Assuming all that stuff is upstreamed (and they aren't using oddball webcam/input devices etc) it should have much better support than Qualcomm.

Fingers crossed!

I'm curious to see if this weird stack gets ported to the Googlebooks or if they just make a mouse-friendly Android app instead.