On Windows, I hate them. They always push me towards using a PIN instead of my Yubikey or password.

But, something to keep in mind: AI caught a lot of us by surprise. I used to pass through circles of AI developers, and I never thought I'd have an AI coding agent 15 years later.

1: The quality of code varies widely from model to model. In Visual Studio Copilot, I get so-so code from GPT, great code from Claude 4.x, lousy results from Claude 5.x

2: "Novel work" is harder to get from an LLM than when it's following an example. For example, I can get great Blazor / HTML / css from an LLM (and then spend time iterating making small adjustments,) but if I'm writing a complicated DB query or implementing a novel algorithm, it's best to do by hand.

3: But, in the case of a novel algorithm or query, I get great results saying "please write unit tests for XXX". That alone makes me develop code twice as fast!

The first part of "Wealth of Nations" by Adam Smith gives many historical examples.

And in Ray Dalio's book, he explains how the US government did it in the past, and will need to do it again in the future.

His theory is that governments have a debt cycle, and printing money is just one point in that cycle.

The article makes a lot more sense if you've practiced Zen.

Think of it as someone's way of making sense of Zen teachings by related them to something they already understand.

"Zen Mind, Beginner's Mind" makes more sense in a group setting. I read extracts of it with a Zen priest in a meditation group.

It's also a hassle to have it "read" messages, it requires far too much interaction with the screen (and then the phone for permissions) for driving.

In contrast, with my Pixel watch, while driving, I can see enough of the message to get an idea if it's important or not.

The thing is, I really like seeing text messages on my watch out of the corner of my eye. I don't read them, but I know that so-and-so texted me, and if it's important I figure out how to read the text safely.

Otherwise, I turn off almost all watch notifications very aggressively.

---

I also really enjoy using my watch as an alarm clock and to track sleep, but I could just wear it at night if I wanted to wear a mechanical watch.

> But I guess, if there were a distribution which sets things up so that 4 or more people can use the same PC, it'd get wider adoption...

That makes no sense, for a few reasons:

The shared computer model is generally replaced by RDP (or similar) to a VM running in the cloud.

Vast majority of people use laptops or other portable computers; using networked applications where resource sharing happens "in the cloud": IE, web applications. The portability of laptops trumps stationary computers.

Furthermore, with modern economics, the computing power to do basic computing is so cheap that "dumb terminals" don't make sense anymore: A computer powerful enough to run a web browser costs about the same as what it would take to make a "dumb terminal".

Remember, a typical smart TV is a computer powerful enough to run a web browser or a general office suite.

C is great when you need to do manual memory management. Most software written today doesn't need to do manual memory management. (And frankly, for the typical software project, manual memory management is a liability.)

I always end up picking a lot of dust out of my usb-c ports on my phones; or otherwise the port wears out and disconnects before charging completes. (Right after my wife entered the hospital in labor, I needed to scrounge around for something to clean out my phone's port because the "go" bag only had a wired charger and my phone wouldn't charge on it.)

It's why I went to a wireless charger for daily use.

---

I'm real curious why lightning never became the standard. Was Apple trying to keep it proprietary? Was there a half-hearted attempt to open it up or otherwise convince the Android ecosystem to use it?

We can have timezones where noon is close to true noon. Where I live, the sun is highest either at 11:30 (Standard) or 12:30 (DST.) Most major cities are southwest, so if we stay on permanent standard, everyone's true noon is going to be within 30 minutes of noon on the clock.

Permanent DST screws things up for the cities that are southwest of me, because then their sun is highest in the sky after 1:00 PM. These cities are very far, either requiring a plane ride or a day-long drive, so it's not a big deal for them to switch to a different timezone.

Make sense? You're going off on strawman rants without understanding what I'm advocating for.

20 years ago there was some momentum behind Visual Basic .Net; but the language was so similar to C# that it just wasn't worth using. There was a joke that .Net was a "skinnable language."

BTW, there's a whole nitpicky/semantic argument that C# isn't null safe because of the null forgiving operator. That will probably come into play with G# if the null forgiving operator can be used from C# to pass null into G# code that doesn't expect it.