The difference would be that RMS is extremely well-versed in computer technology. He understands the problems with non-free software.

Someone with his knowledge could choose to disregard those issues for convenience, but Stallman is willing to make great sacrifices.

But now it’s too long for a power user.

Short and Long options are a thing.

Ex: GNU rm can use

--recursive

-r

or

--force

-f

To be fair, that is an issue with the implementation of the given commands, rather than the concept of the command line.

You could create a program that operates like so:

remove-file --dont-ask-for-confirmation house.png

Linux is software.

It doesn’t contain this intrinsic meaning you refer to.

It’s self-explanatory to you because you’re already familiar with the logic, language, conventions. I’m guessing, you grew up with all that from childhood…

This argument can be used as a reason to implement GUIs.

If we wish to market to an audience that has had some basic experience with using Windows and Mac, we can skip some of the reteaching by implementing familiar GUIs

Security is much more effective and adopted when it is simple. My understanding is that SELinux is not.

This means not only will fewer people use it and more people turn it off if something doesn’t work, it means more people are at risk of misconfiguring their system to allow something they didn’t intend to.

This is somewhat mitigated from the fact that, from my experience, Linux Security Modules cant ever make you less secure than without it. But it still can provide a false sense of security if you misconfigure it.

Here is a good article showing what I am referring to, and providing a solid security tool: BSD pledge/unveil on Linux.

Depends on the environment surrounding the door, as well as the environment surrounding the computer.

Some people simply care less about their computer security. The debate stops there. Security operates on a foundation of what you want to secure.

By comparing two environments of someone’s life you know little about, you are commenting from ignorance.

True.

Though, you are probably going to have a much easier time implementing a change to your code that is present in a company’s published code, than you would trying to reverse-engineer a binary.

Sharing of the code I would consider “giving back” in it of itself.

It can be done if you mess with the initramfs.

The kernel starts everything else by unpacking an archive containing a minimal environment to set stuff up for later. Such as loading needed kernel modules, decrypting your drive, etc. It then launches, by default, the /init program (mines a shell script).

That program is PID 1. If it dies, your kernel will panic.

After it finishes setup, it execs your actual /sbin/init. These means it dies, and that program (systemd, openrc, dinit, runit, etc) becomes PID 1. If an issue happens, both could fail to execute and the kernel will loop forever.

Very simple actually: don’t use 100% transparency.

Just use something like 80-90% opaque (10-20% transparent) and use the background color as black so it just dims whatever us behind it.

You can have both function and form.

Its possible: Link

I’ll take a program that isn’t getting updates anymore or simply wasnt working in my modified environment using slightly more ram and storage over it not working at all.

I have firsthand experience with videogames made for one flavor of Linux not working on my machine due to dependency hell.

This is a good reason for static linking. All the dependencies are built into the binary, meaning it is more portable and future proof.

We don’t need flatpak for this!

They have also had this issue open for 20 years.

And this amounts to just allowing the user to specify a different directory for Firefox on Linux (~/.mozilla is terrible).

Frankly unacceptable.

We can use dinit, s6, runit, and openrc.

There are more, but these are all top contenders.

I switched to dinit recently, it uses declarative service management (like systemd unit files). Very clean, fast, lightweight, and portable.

Linus already has a backup. Its Greg Kroah-Hartman.

Yes. ~/.mozilla. Its annoying.

You can fix it with a hack by putting a shell script in your path (before the original firefox) that consist of:

#!/bin/sh

HOME='/home/engywuck/.local/share/firefox' /usr/bin/firefox

Call that instead of the original firefox from now on. it will create the “librewolf” folder in ~/.local/share and chuck its junk in there.

Edit: This bug has been open for TWENTY YEARS.

Honestly ridiculous.