Partly, sure. Don’t think that’s the whole story. I don’t work at Apple or anything so I don’t know what actually goes on in board meetings but I think any tech person would see there are pros and cons to web apps versus native apps.

There’s a funny history where the original iPhone apps could only be web apps as there was no SDK! See history section at https://en.wikipedia.org/wiki/IOS_SDK

You can watch Steve jobs rave about the future of PWAs here! https://youtu.be/QvQ9JNm_qWc

In my org the ones who used to do nothing but sit at a desk and press buttons now do nothing but sit at a desk and copy and paste LLM output.

The useless layers of labour hasn’t changed with AI because it was and continues to be a failure of management that they exist in the first place.

I welcome the idea of working smarter, not harder, but I don’t think it can be applied to every company.

There are implementations of cp out in the wild that do not recognise the --recursive flag. OpenBSD was mentioned in the article and there’s also busybox cp https://busybox.net/downloads/BusyBox.html

Mistral now serves GLM-5.2: https://mistral.ai/news/regional-inference-open-models-new-c...

Not sure about use in the Go community at large but Go introduced os.UserConfigDir[1] which is portable across Windows, macOS, Plan 9 and Linux/BSD as per XDG back in 2019. Also CacheDir.

[1]: https://pkg.go.dev/os#UserConfigDir

> On Darwin, it returns $HOME/Library/Application Support

Which is not the behaviour most people would think is sensible, especially for CLI programs.

Ghostty has chosen to use that as the default and I feel like it's going to be the tipping point where people will assume $HOME/Library/Application Support is normal for CLI programs.

Mac users are used to checking ~/Library/Application Support/App, ~/.app, and ~/.local/config/app

fwiw, it absolutely drives me nuts that cli programs are putting configs in that hard to reach folder (long path name and _spaces_ in the folder name ugh)