This test is good and also I'm not sure it's meant to be funny, but it is very funny.

> developers write commit messages

The people who don't write commit messages for us are the non developers.

Writing commit messages shouldn't take any time at all. If it does, then you probably have a range of other professional issues.

Nix does not really work in that even basic things are absurdly complicated and can take days of messing with poor libraries and documentation.

That's not been my experience with jj which after the initial hurdle is a breeze.

Pretty much everybody who does work at the real office where I am has a mechanical keyboard by now.

How do you get good like this?

Just keep doing stuff and gaining experience. Sometimes you'll find that you don't know how to do something, at that point don't just reach for an LLM, do your best to try and understand it, google around, and if all else fails, put it down and maybe come back to it later with fresh eyes

One group of people pretends to have written something and another group of people pretends to have read something. Much productivity is gained.

Zizek had a great point about this.

At least both get paid in not-pretend money.

For the time being. Their manager is under constant pressure to lay them off and replace them with “ai”.

I think that's fair. Funny to have a language that makes it prohibitively difficult to use most of the core computer science constructs (lists, graphs etc.).

No Swift was developed as a strategic moat around Apple's devices. They cannot be dependent on any other party for the main language that runs on their hardware. Controlling your own destiny full stack means having your own language.

Apple already had that "strategic moat" with Objective-C. It was already a language you could effectively only use on Apple platforms (the runtime and the standard library only run on Darwin) and for which Apple controlled the compiler (they have their own fork of Clang).

I suspect that it was developed, in order to make native development more accessible. SwiftUI is also doing that.

They want native, partly as a “moat,” but also as a driver for hardware and services sales. They don’t want folks shrugging and saying “It doesn’t matter what you buy; they’re all the same.”

I hear exactly that, with regard to many hybrid apps.

Swift is Apple's toy language and they cannot and will not allow it to be anything more than that.

Great work on the 20% of making a working chat app. Now somebody has to do the remaining 80% and then the other remaining 80%.

Thanks. It was just a fun exercise and I had fun writing about it.