R*dd*t refugee

Fuck /u/Spez

  • 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle
  • I settled on two.

    1. Arch for my desktop, because there I like having an always up-to-date system with the latest drivers and libraries so that I can always try the latest versions of whatever it is I want to play with next. Pacman is also a pretty good package manager, and almost any piece of software that is not in the default repos can be found in the AUR. For the rest, I also like that Arch just gets out of your way and lets you configure your system how you want.

    2. Debian for anything that runs unattended, like all my homelab services. It’s well tested, offers feature stability, has long-enough support, and doesn’t do weird things every other release like forcing snaps or netplan or cloud-init on you. Those “boring” qualities make it the perfect base to run something for a long time that doesn’t scream for attention all the time.



  • ssh tunneling can be very useful for testing or one-shot things where you quickly need access to a service that’s not directly reachable, but I wouldn’t use it as a permanent solution for anything. You quickly run into problems like:

    • TLS certificates don’t work, so you get into the habit of clicking through security warnings or turning of TLS validation altogether.
    • Virtual hosts don’t work
    • Port conflicts when you want to access the same type of service on different remote machines, so you have to remap them and remember things like: localhost:8080 is foo:80 and localhost:8081 is bar:80
    • If it’s not your infrastructure (i.e. you are an employee in a larger company), you are probably bypassing all kinds of security rules by exposing a service and your security guys will not be too happy about it if they find out.


  • I general why does there have to be static sidebars that are rarely used. It causes the content body to be squeezed into tiny space.

    I think the rationale is that most people use widescreen monitors nowadays, so if you allow the content part to run across the entire width of the screen, it becomes ugly and hard to read. Therefore the middle section gets a limited or fixed width, which in turn then creates two empty columns to the sides that designers are then tempted to fill up with “useful” stuff.

    You can try this yourself: paste a long line of text into a notepad window and maximize the window. It is much harder on your eyes to read and focus on the text than if you resized the window to a more reasonable width where the text gets broken up into several lines.

    I’m not against this design paradigm per se, but the content width reduction is often overdone, leading to a squeezed feeling like you say. It can also create problems if you have a habit of not using maximized browser windows, but for example a window tiled to one half of the screen. Some of the better sites work around this by having a reactive design that reduces, collapses or removes the sidebars when the window is narrower than a certain width, but many sites don’t.