Lettuce eat lettuce

Always eat your greens!

  • 3 Posts
  • 255 Comments
Joined 1 year ago
cake
Cake day: July 12th, 2023

help-circle
  • Performance and how configurable things are, plus ease of use.

    For instance, my default router/modem device from my ISP was super clunky and confusing. I needed to set up some custom port forwarding and firewall rules. The aftermarket router I bought was faster, had way better wireless coverage, and the UI was so much easier to set up the configs I needed.

    So it’s up to you, from what you said, seems like you probably would be good with the default from your ISP.







  • In the last year I have switched to all cast iron, carbon steel, and stainless steel for all my pots and pans.

    No Teflon or “non-stick” coated garbage for me. Properly seasoned and cared for cast iron, carbon, or stainless steel will all be nearly as good as a “non-stick” pan and doesn’t have the risk factor.

    Recently, non-stick pans have been released that supposedly are safer, but I don’t really feel like trusting billion dollar corpos to not lie for the 20th time about that, not when there are fantastic alternatives.






  • I’ve heard that the DoD uses RHEL pretty extensively. RHEL in the US Military

    That article says that the US military has the largest single install base for RHEL in the world, but that was about 15 years ago, I don’t know if that’s still true.

    Apparently back then the US nuclear sub fleet and its sonar systems also ran on RHEL.

    I suspect lots of military hardware runs some form of *Nix or BSD type system. Many embedded systems run some *Nix type OS, and a huge portion of the developed world’s weaponry is smart, so it it full of low power embedded systems and custom SoCs.







  • Appimage is probably the most similar to a naked .exe in Windows. They are useful for small apps or simple indie games, but I prefer Flatpaks for my everyday big applications.

    Agreed, Snaps are like Flatpaks but worse because locked down back end and Canonical’s sketchy nature. Imagine a really delicious pastry that anybody can make and sell, then imagine the same pastry but only one bakery in the world can make and sell it. Which would you prefer? Lol


  • Essentially yes, if you start using lots if older applications or mixing applications that use many different dependency versions, you will start to use lots of extra disk space because the different apps have to use their own separate dependency trees and so forth.

    This doesn’t mean it will be like 2x-3x the size as traditional packages, but from what I’ve seen, it could definitely be 10-20% larger on disk. Not a huge deal for most people, but if you have limited disk space for one reason or another, it could be a problem.



  • Flatpak is a universal application packaging standard for Linux. It allows devs to create a single application that gets bundled with all necessary dependencies including versioning.

    These apps run in their own semi-isolated “container” which makes immutable distros possible. (Distros like Fedora Silverblue that are effectively impossible to break by installing or removing critical system files.)

    This means that a Linux app doesn’t have to have a .deb version, an .rpm version, or be pre-compiled for any other distros. A user can simply go to Flathub, (the main repository for Flatpak apps), download the flatpak, and install it on their distro of choice.

    It’s quickly becoming the most popular way for users to install apps on Linux because it’s so easy and quick. But there are a few downsides like size on disk, first party verification, per-distro optimizations, and the centralization of application sources. That’s why some users aren’t fully endorsing or embracing how popular they are becoming.