Hierarchical taxonomies always run into problems because there are multiple equally valid ways to organize things. Hierarchies are inherently a wrong-headed approach. Subjects are inherently multidimensional. Hierarchies wind up forcing you to stack categorization on different properties on different levels of the hierarchy and it winds up arbitrary which ones you preference over others.

The tendency to reach for hierarchies is a bias we inherit from life in the physical world. A physical object can only be in one place at a time, so we organise physical objects in hierarchies by necessity. Rooms, cabinets, drawers, files. This is not a necessary limitation on computer system but people keep insisting of using them anyway.

I’d forgotten about Myrlyn. I guess I never switched over to it from the older YaST software updater, which does not have the equivalent of ‘zypper dup’. But from what I read now, Myrlyn does, so that is good.

Discover does not, however. Not only does it not do the equivalent of ‘zypper dup’ it does not resolve package conflicts that can arise with external repos.

For anyone reading whose not familiar, on Tumbleweed, ‘zypper dup’ (or the Myrlyn equivalent) is what you need to run periodically to update to the latest snapshot (and being a rolling distro, new snapshots come out anywhere from every day to every few days, depending how the automated testing goes).

openSUSE Tumbleweed has a graphical installer you can use to install, remove, update applications, browse, search, etc. But you still need to run a command line ‘zypper dup’ to fully update the system.

Wow, both links gave me the same number! What are the chances!

It’s a very basic principle, that you don’t create powers that could be abused. That they haven’t been abused yet does not make doing so ok. It like saying it’s ok that my government was given the power to lock people up with no reason or due process because they haven’t used it yet.

And also until the committee designing it has it members on it representing the interests of users. The point that this was lacking in the original is-a-trap article is an important one and is also being missed.

Have you ever used bank software, or some government services site? It is often really hard to not get the idea that it was designed and run by idiots. As someone who’s worked as a software developer most of my life, it is not difficult for me to believe it, either.

Right, a stack that was itself read-only would be hard to use! :^D C definitely lets you modify the things in the stack. (Ah the fun of bugs where you accidentally overwrite other shit on the stack!) I don’t know Rust, but it would not surprise me if Rust only had immutable things on the stack.

I’m drawing on some old memories here, so I could be mistaken, but I don’t think the stack is read only, not in C anyway or in the underlying machine code. If it is faster it has to do with greater overhead needed managing the larger heap and perhaps being more efficient to push and pop with small offsets to a local stack frame vs large absolute addresses.

There seems to be a certain entitled smugness that always shows…

I don’t think they are the same category of thing. Ocean is a design system. Breeze is a theme.

Edit: now I’m less sure. This seemed to say it is both a style and a “design system” which I took to mean a technical mechanism for styles, but now i’m less clear what they mean.