Even if it were Opus, comparing to a version number makes for an interesting snapshot of time comparison: if you knew how a model performed at whatever time in was in vogue, you can say "well, it looks like Model X is about 6 months/1 year/etc. behind the frontier SOTA" - which is exactly the discussion that happens in the open-weight/local LLM space. (interesting, MAI-Code-1-Flash does not appear to be such an open-weight model, following the western trend of locking models up)

(Not that I know all that well how good Linux machines are at clocking down anyway - my XPS and desktop both have VRR panels, but for all I know Niri runs them at full bore at all times - haven’t tried to measure, wouldn’t even know where to start)

Even knowledge of how to drop to C is fairly rare in much of development, and you know what? That’s okay. We all specialize in our own areas of this beast of a field.

(Seattle is my home airport, so maybe this has something to do with it - but come on, SEA is no ORD or ATL...)

Holier than thou “yeah well I work on stuff that doesn’t use databases, checkmate!” doesn’t really land - data still gets moved around somehow, and often over a network!

Looking even at normal arterial streets, many streets in Seattle are marked 25, but you'd be hard-pressed to find even a cop going under 30 most of the time.

I truly don't understand US road design. The construction of the road and the posted speed limit almost never are even gently correlated other than on a few select residential side streets in a few select cities who have rebuilt streets based on safety studies.

Now, yes, almost everything about Apple’s hardware UX is a light year ahead of most competitors. That’s been true for ages.

Patch files are excellent for small diffs at a glance. Sure, I can also `git remote add coworker ssh://fork.url` and `git diff origin/main..coworker/branch`, and that would even let me use Difftastic (!), but the patch is entirely reasonable for quick glances of small branch diffs.

Obviously enterprises aren’t commonly BYOD shops, but SMBs and startups certainly can be.

… whether the people who would do such BYOD things are at all likely to be Windows users who care about this Bitlocker issue, is a different debate entirely.

They are tools, they are sometimes useful tools in particular domains and on particular teams, but your comment reads like one that assumes they are universally agreed upon already, and thus that the health industry has a trustee example they could follow by watching our industry. I firmly disagree with that basis.

Now, unified memory shared freely between CPU and GPU would be cool, like Apple and AMD SH have, if that’s what you meant.