barsoap

barsoap, 8 months ago

Also, imo, having windows in windows is useful when you want to use your favourite terminal in your favourite IDE.

The wayland way to do that is to have the application be a compositor, they made sure that nesting introduces only minimal overhead. And that ties in with the base protocol being so simple: If you only need to deal with talking to the compositor you’re running on, and to the client that you want to embed, a wayland compositor is indeed very small and lean. Much of the codebase in the big compositors deals with kms, multiple monitor support, complex windowing logic that you don’t need, etc.

Oh and just for the record that doesn’t mean that you can’t undock the terminal: Just ask the compositor you’re running on for a second window and compose it there. You can in principle even reparent (client disconnecting from one compositor and connecting to the other) but I think that’s only standardised for the crash case there’s no standard protocol to ask a client to connect to another compositor. Just need to standardise the negotiation protocol, not the mechanism.

barsoap, 8 months ago (edited 6 months ago)

TETP is just a nefarious scheme to dictate glorious typography to member states. Seriously that thing is good: Ridiculously legible and specifically so in “big font at long distances” situations, meanwhile both friendly and authoritative – exactly the kind of thing you want when asking for the way. No “yeah let me think where was that intersection” or “can’t you find your own way” but “Of course! Go straight ahead, first to the left, then the second right”.

Now if the EU would get around to telling member states that they should learn from each other in overall traffic and urban design, and follow the best practices that they can find anywhere. Which is diplomatic language for “Do as the Dutch do”.