1. I want it to be easy for developers to publish their own packages. 2. I want it to be easy for users to install these developer-published packages.

> Are you saying they're not "professional"?

I regret using the word professional, I was replying to the claim GP made:

> Packaging it for a distro is someone else's job

Well I (as a developer) want to publish my own software without waiting and hoping someone else will do it for me.

> Somebody has to do the work.

Yes, I (the developer) want to do the work. The whole point of the article is that its painful to do today. I'm interested in how we make the packaging work easier so the developers can do it.

> [...] So third parties

the whole 3rd/1st party question is whether a developer can publish their own package. In most cases they technically can (taps, PRs, flathub, Debian registries, so on) but run into lots of issues along the way.

The idea that your OS distro needs to explicitly support and package every software you could ever want to use seems crazy to me.

Both users and authors want the same thing: low-effort, high-quality distribution of software.

Personally I put my support behind flatpak for GUI, mise for CLI/TUI, but it's not a perfect solution and I occasionally bail out to homebrew/linuxbrew.

Most people would have seen those websites on shitty low contrast CRT monitors, so seeing them again today with a modern OLED is a very different experience.

I don't agree with "Domain control as a fallback", as the author said "a domain is not owned, it is rented" and I want to normalise the idea that if you lose your private key, you need to start again. I hate that we keep giving so much authority to domains, it's such a big weakness. The author even left the key rotation chain out of the initial implementation.

I still think root/signer keys or sigchains are decent options.

Someone's optimistic

- USB4 is built on Thunderbolt 3's protocol, implementing a subset of its mandatory features

- Thunderbolt 4 is a strict profile of USB4 (all optional features made mandatory)

- USB4 v2 introduced 80 Gbps signaling

- Thunderbolt 5 is a strict profile of USB4 v2 (again, optional features made mandatory)

I'm curious which dev tools you're using aren't installable with standard mise backends. 99% of dev tools I use don't require a plugin.

> (more painful than, say, an asdf plugin)

You can still use asdf plugins, I could use mise to install an asdf plugin right now with one line `mise use asdf:raimon49/asdf-hurl`. The mise registry is just a convenient list of aliases, even if it doesn't accept new asdf plugins, you don't need it to.

As Larry Wall said "make easy things easy and hard things possible"

Pixi is very python focused, it's both a tool manager and a library dependency manager (see uv/pip). Mise considered library dependency an anti-goal for a long time, while I don't see that on the website anymore I haven't seen any movement to go into that space.