This is a good approach. I’ve always found it beneficial to learn “the standard things” than relying on a customized setup.

I’ve seen some people absolutely lost when they login to a system without 500 custom aliases on it…

The android nextcloud client works great if you’re willing to setup/maintain a nextcloud server.

BeOS or haiku?

I have a dual 603 BeBox I haven’t fired up in a while…

RedHat.

Not Fedora. Not RHEL. Back when it was just RedHat Linux.

Works fine, though it’s not an “iso” file. But it doesn’t matter what extension you use.

I used to do this to switch an old laptop between Windows and Linux. I’d backup one, overwrite with the other. Swap as necessary.

Things installed by apt almost always work as expected and are easily run from the cli.

Flatpaks are sometimes more up to date.

BitTorrent would likely increase latency, not lower it. The bit torrent protocol is very inefficient for small files and large numbers of files (https://wiki.debian.org/DebTorrent - see “Problems”).

But I think your question is more “why not use p2p to download files” for which I think the answer is likely “because they don’t need to.” It would add complication and overhead to maintain. An FTP/HTTP server is pretty simple to setup / maintain and the tools already exist to maintain them. You can use round-robin DNS to gain some redundancy and a bit of load spread without much effort either.

“AllowedHosts” is the one thing that pisses me off the most. It’s a terrible name and caused me tons of confusion when first setting up wg.

“I’m switching from Windows and want a good distro I can watch Mr. Beast videos on.”

Okay this “which distro should I use” shit is just getting out of control.

Which one is best for Android development? Are you kidding me? Just pick any one you like.

You sound like you have no disabilities that make it hard for you to use the Internet. Good for you.

If AI can add usability features that help people use the Internet easier then that’s a good thing. You don’t need to use it. Why complain about software being capable of helping others?

Windows is historically a “single user OS” whereas Linux is historically a multi-user OS. They’re both multi-user now but the philosophy of these backgrounds results in what you see today.

So under Windows you login “as an admin” and don’t need passwords for many things - similar to (but very much not the same as) running Linux as root.

Under Linux you login “as a user” and need to elevate permissions for things which can affect other users on the same system. Typically with sudo these days.

These lines are very much blurring so you can do many things under Linux without a password and some things on Windows require “running powershell as an admin”.

Using containers for build environments is probably my favorite use of containers.

I have an application I build for Linux, Mac and Windows and frankly building two or three Linux builds in containers is easier than the Windows and Mac builds alone. A github action automates it easily.

I guess i am still skipping on how real time kernel address the pause? it just never pauses or it no longer needs to be paused?

When hardware has data ready for a program it generates an interrupt that lets the OS know that there is data ready for an application. My understanding is that real-time OSs give high priority to interrupts so that they’re processed quickly - usually within a fixed period of time (e.g. they may have a max time between interrupt and processing).

as a side note, is this similar technology they use in high precision manufacturing?

In those cases it may be more likely they use a micro-controller that doesn’t run any OS at all - at least not a multi-tasking one. If you’re just running a single program you don’t need to worry about latency due to other applications running.

So, contrary to what it seems a single CPU core can only execute a single “thing” at a time. Modern operating systems do something called “preemptive multitasking” to give the illusion that more than one things are running at a time. The OS will start your task, then after a while save its state and start another task running, then switch back. It does this fast enough that each job seems to be running concurrently.

Now if you’re running on a RaspberryPI your program might be waiting for input from a GPIO pin. And when you get that input you want to turn on some switch. Maybe an important switch. BUT It could be that your application is in the “paused” state when that pin gets input which will cause a delay between when the pin is trying to send you input and when you actually process it.

A real-time OS minimizes such delays (latency) so that you can respond quickly.

Which distro?

Feature creep is a hallmark of “software bloat”. Using a web browser to do something completely unrelated to it’s core functionality is pretty much the definition of “bloat”.

Obs is purpose-built to do the thing you want to do. That it also has features you don’t want does not make it “bloated”.

I’ve always liked “nomachine” for remote desktop access. It seems to support Wayland.

What should I do?

Let them do what they want.

I guess the word “bloat” has no meaning anymore.