Why not also remove the password from my wifi while im at it?

I would have preferred to have it solvable through policy or something. A giant business, with high earning employees would of course raise the average rent if not regulated. I find it rather amusing, that it actually happened in the game as well without being explicitly build in.

Guckt euch Herr Schickhose an, dessen Spülmaschine sich beschwert wenn Dinge nicht passen

And I'm sure that fine was as high or higher than the profit they made from the data... what, it wasn't?!

Und wenn du sie drauf hinweist können sie dich leider nicht für die Wohnung berücksichtigen

Isn't that also quite the small form factor? I still had the fridge sized copper monstrosities in mind when thinking of quantum computers

Dann darfst du nicht in den Balrog Streichelzoo

I never understood how transporters are not basically used as quicksave devices. Redshirt died on the planet after beaming down? Just create another copy from the transporter puffer. Tuvix deserves to live. Sure, just recreate tuvok and Neelix from the transporter puffer.

Edit: "Transporter puffer" may come from me watching the German dub

Und ich dachte es geht darum, dass das 'auch' andeutet ihr würde die Lachsfalle trocken laufen

Just for them to be axed again when Cheeto or any other GOP troll comes back into office? They need to be actual law and not something set up by the FCC

That's because the web dev ecosystem at one point decided, that libraries that only offer very minute functionality are acceptable as well as adding 20 of them to your project.

Examples like isEven or left Pad come to mind, which have such high proliferation, that their dev broke half the planets web projects when he broke them intentionally.

For simplicity sake alone I would say No. As long as services don't share infrastructure (eg. a database) you shouldn't mix them so you have an easier time updating your scripts.

Another point is handling stacks. When you create dockers via compose you are not supposed to touch them individually. Collecting them all, or even just in categories, muddies that concept, since you have unrelated services grouped in a single stack and would need to update/up/down/... them all even if you just needed that for a single one.

Lastly networks. Usually you'd add networks to your stacks to isolate their respective Backend into closed networks, with only the exposing container (eg. a web frontend) being in the publicly available network to increase security and avoid side effects.