• 0 Posts
  • 27 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle


  • If you’re upset about that, you know nothing about IP law.

    If you do not grant Firefox a license to use your information, the only thing they can legally do is destroy it. So no storing of bookmarks, usernames/passwords, search history, browsing history, no saving your open tabs so your next session picks up where the last ended, none of the things that we all expect of a modern browser. Without that, you’re basically left with just a URL bar with no search ability.

    They’d gotten by without that clause for a while despite being technically illegal in the EU and California. And again: what’s the alternative? Chromium has the same thing, and no Firefox fork can exist without mainline Firefox.







  • The thing with Debian is that yes, it’s the most stable distro family, but stable != “just works”, especially when talking about a PC and not a server (as a PC is more likely to need additional hardware drivers). Furthermore, when the time comes that you DO want to upgrade Debian to a newer version, it’s one of the more painful distros to do so.

    I think fedora is a good compromise there. It’s unstable compared to RHEL, but it’s generally well-vetted and won’t cause a serious headache once every few years like Debian.





  • The thing with Debian distros (like Ubuntu, Mint, PopOS) is that they’re extremely stable releases. This does not necessarily mean everything “just works”, but rather that they will not experience major code changes that could disrupt a working system. This means that if some apps don’t work out of the box, that state is going to be pretty much the same in any distro based on the same Debian version.

    A more “agile” distro might be less stable, but as a result could see some updates to apps that Debian is still lagging behind on. Fedora is probably the “next step” in this direction: it’s still reliable but gets updates more frequently than Debian (it’s sort of a “proving ground” for code before it gets pulled into Red Hat, which is a distro focused on long-term stability).

    As for desktop environments: I’ve always thought GNOME was the most Mac-like DE, but KDE has enough configuration options that you can kind of turn it into anything you want. Since this is on a very old laptop, you might consider LXDE, which isn’t the prettiest DE, but it’s super lightweight and might let you squeeze out a bit more performance if you’re wasting a lot of compute power just rendering the desktop.





    1. Yes, portainer will see every container you make, regardless of how it was created.

    2. No, creating a docker container doesn’t make a compose file. It’s like cooking a meal doesn’t output a recipe.

    3. You can save the compose file(s) wherever you want, you just need to run “docker compose up” from that directory. If you make the container within portainer, I believe it stores the compose files in its own volume. Not sure about that, I keep my compose file separate from portainer for most services.




  • For a similar reason that most coaches don’t actually participate with the athletes they’re training: their job is to watch the athletes, look for gaps in their technique, and help them to address those. You can’t look for that as effectively if you’re swimming alongside them compared to standing on the side of the pool.

    But yeah, all “learn HOW to swim” lessons I’ve ever seen have the instructor in the water with the student, because they have to be like 25% teacher 75% lifeguard.