Writing down what you learn cements knowledge, and sharing what you write might help someone else.

You can still have a central team of operators. When they're expected to deploy and support applications from development or procurement teams, I'd argue that's something else than devops for better or worse.

Someone else considered it worthy of sharing here and enough people here found it interesting enough to get it to the front page. I don’t quite understand why, but it seems like it’s striking some sort of chord.

I may be way off, but to me it seems like the AI bubble is largely a way to siphon money from institutional investors to the tech industry (and try to get away with it by proxying the investments) based on a volatile and unpredictable promise?

Now I’m suddenly a third-class user, as I’m neither an enterprise customer nor paying for their AI features. I can only cross my fingers and hope the product doesn’t follow its new incentives. That doesn’t feel like a great position to be as a hobbyist who appreciated and paid for everything they released previously.

In that sense it could be reconstructed as ”soft power mode” and ”hard power mode” where the former inspires confidence and encourages creativity and the latter emphasizes compliance and alignment. Any person in a position of power will utilize strategies that could be seen as signs of either mode depending on the situation.

> If it exists, what are the barriers to adoption? Why don't we all use it?

My theory is that people in general don’t care that much, or (particularly in the case of corporations) consider permissive licenses to be ”freer” than copyleft.

the very first paragraphs on specifications.freedesktop.org says this:

> Freedesktop.org is a project to work on interoperability and shared base technology for free-software desktop environments for the X Window System (X11) and Wayland on Linux and other Unix-like operating systems. > We are not a formal standards body. The standards published on these pages are active or tentative (if marked as such) specifications which desktop environments may implement to improve mutual compatibility, share code and pool resources.

Deferring to XDG_CONFIG_HOME on MacOS if it exists makes a lot of sense as it conveys a clear intent from the user and the convention has grown popular. I’m not sure that the default ~/.config from the XDG specification is automatically better than ~/Library/Application Support by appeal to freedesktop.org’s authority.

And please don’t move configuration files around between releases without really being intentional about it.

Daniel Stenberg (from the curl project) has blogged a bunch about AI slop seeping into vulnerability reports[1], and if the same happens to code contributions, documentation and so forth that can help turning a fun hobby project into something you dread maintaing.

[1] https://daniel.haxx.se/blog/2025/07/14/death-by-a-thousand-s...

I’m not at a computer where I could try that hypothesis right now, but back then my conclusion after testing various executables was that any unsigned Go binary would be flagged as a malware.

For smaller businesses and hobbyists it feels like expecting support for all major browsers would be discouraging in a negative way. I appreciate digital art even if it doesn’t work in my favorite browser and a shitty online menu for a food truck is better than none.

To address your example: Why were the arrow keys on those particular keys? Who put them there? hjkl are on the home row, and touch typists end up having the movement keys under their right hand’s resting fingers. That’s suddenly quite convenient.

I get it from GitHub’s perspective, it’s a nudge to get people to accept the core premise of ”social coding” and encouraging user pressure for mirrored projects to accept GitHub as a contribution entrypoint. I’m impressed by their successes and would attribute some of that to forced socialization practices such as not allowing PRs to be disabled. I’ve grown to dislike it and become disillusioned by GitHub over the course of a long time, but I’m in awe of how well it has worked for them.

https://portal.ct.gov/ag/sections/privacy/reporting-a-data-b...

I doubt this is an engineering team’s naivete meeting a rational legal team’s response. I’d guess it’s rather facing marketing or management naivete that sticking your head in the sand is the correct way to deal with a potential data leak story.