IT workers desperately need to unionize. There is so much bullshit that happens, folks are expected to do three different roles at once, have multiple technical stacks they are experts in, and work extra hours + be on call after hours or on weekends.
Thanks, and right back at you.
Most every day this week, I'm scared that I'm not going to be able to accomplish all that I want and should.
I'm scared of letting down the people I care about most.
I'm scared that I'm not going to be strong enough when life throws really brutal curve balls at me.
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.
I have a monthly budget that I pay recurring charges out of, a couple hundred USD a year give or take.
I also do a lot of one-off donations to various projects and creators.
I also have some FOSS software/services that I pay monthly for premium features on, like Bitwarden, Proton, and Podverse.
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.
I'm not an expert, but from my understanding, more like android apps.
They aren't totally isolated like a docker or LXC container would be, but they are generally self-contained.
The Linux Experiment has a really great vid that goes into detail on all common packaging formats in Linux including Flatpaks:
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.
I have been enjoying fish a lot over the last few months, but I generally try to use Bash, it makes cross-*NIX administration that much easier.
Sure thing...now GPL/Creative Commons all your code involved in any way for your models, documentation, parameters, data sets, and allow full unlimited integration and modification by any parties to any portion of it.