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.

They also received far more abuse than usb cables. We don’t generally anchor one end of a usb cable and then walk around erratically for hours everyday within the range of the cable (and now and then pushing it) with the device on the other end of the cable.

Those cables _were_engineered for more abuse.

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.

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.