i want to like fish but i miss my history substitution too much

(╯°□°）╯︵ ┻━┻

there’s a few 3d file browsers. i remember there was one like Doom where you could walk around rooms (dirs) and shoot files to delete them

kwin supports this, gnome from my perspective is more about a cohesive experience you either love or don’t

it’s great if your commits are smaller and more focused. main issue is it can be harder to solve some diff issues as it requires solving merges at each commit being rebased. so if you have a large feature branch that can be challenging when it starts to diverge a lot (ex: bug fixes on main). though the argument then is more for keeping branches smaller and focused which is a better process imo.

just beware it can be confusing for newer git users and when using shared branches can cause no ff commits.

at the end of the day everything’s a []u8 if you want it to be

caches are never really a concern to me they will regen after the fact, from your description i would worry more about db, this is dependent though in what you’re using and what you are storing. if the concern is having the same system intact then my primary concern would be backing up any config file you have. in cases of failure you mainly want to protect against data loss, if it takes time to regenerate cache/db that’s time well spent for simplicity of actively maintaining your system

in Windows you separate each drive by a letter like C:, D:, etc, however on Linux your drives are mounted as part of your folder structure. the top level is called root which would be / you can then mount each disc as a folder under root, so for example /home could be a separate hard drive but it’s still mounted under root, note the starting slash. This means the command deletes any and all files+directories under root, this can include mounted USB, mounted network drives and anything mounted to your root. you’re basically nuking all the files you can access when you’re logged in as admin/root.

i love Linux tips! you can also print animated clams on the CLI with :(){ :|:& };: add to your bashrc to be greeted everytime you open a terminal!

but seriously, don’t run that unless you want to reboot.

make sure to add --no-preserved-root to make sure to update all the English libraries too so you can make sure only freedom fries are respected.

my work we had test, stage and prod. test was very unstable as every merge auto deployed, so stage was semi stable where you would push changes you verified in test. then one day they decided to remove the stage environment. we have no data in test, other teams never passed data there, so we setup a semi production environment that has data and cost 10x as much. now they want to setup a stage environment to save costs but they don’t want to call it stage because that was bad and was too expensive. so they came up with a new name and are making everyone update to push data there. honestly i can’t take watching these people be praised for their innovation and promoted to make more of these shit decisions. the world’s gone mad and the madder you are the more you’re rewarded.

Look at that subtle off-white coloring. The tasteful thickness of it. Oh my God, it even has a watermark!

flatpak distribution is generally done by the developer as a common packaging method. if a distribution wants a native install it’s up to package maintainers of the distribution to support the application. although the package maintainers have to make sure they’re packaging the right versions of dependencies which becomes a problem known as dependency hell.

in your example of handbrake it’s true the main application is pretty small but that’s because it relies on libraries and is a wrapper for ffmpeg. even if you install through a package manager you still need to compare the total size of dependencies.

the disc space usage becomes a problem due to installing libraries both natively and in sandbox. however if you keep a relatively small system install and install applications through flatpak the disc usage will be pretty negligible. if disc space is really a concern then using something like btrfs with compression+dedup would probably solve most problems.

it’s great for applications that are notorious for requiring specific versions of libraries and can cause dependency hell. moves unnecessary system dependencies into a sandbox. for me this means i don’t have to enable multilib to install Steam and pull in 32 bit libraries on my root.

while it does take a lot of disc space it doesn’t duplicate dependencies in most cases. i would say you receive some good benefits at the cost of a bit more disc space, such as increased security, easy installs, explicit app permissions. it’s great for when you have to install a proprietary tool in that you gain control of what it’s allowed to access.

company uses it?