Bash with fish and GCC with Clang.

The European retards say things like this as though they themselves haven’t swung far right lately. Pot meet kettle.

This is just typical America bad copium by the Europoors and internalized hate by American Euroboos.

A World War is a war between two or more world powers.

That one dildo vape.

GTX 1060 in a laptop. I still have it.

What will you replace prisons with?

Work and reeducation camps.

Waste time configuring things and troubleshooting things when your ultra custom system breaks.

So then tax all capital gains as income. I don’t get why capital gains get taxed less than income. If anything they should be taxed more.

I use normal KDE because I don’t know how much of a hassle it would be to put everything in containers and use flatpaks for everything.

The distro is designed to be a bulletproof, highly user-friendly operating system that showcases the best of KDE technology—a system that KDE can confidently recommend to casual users and hardware manufacturers.

So it looks like there will finally be a distribution that Windows, Mac, and ChromeOS users can jump to and just start using without having to learn much and with a much better and more familiar GUI than GNOME.

Why? What’s the issue with Snap? Is Flatpak any better?

I use Fedora KDE but this one sounds like exactly what I need. I primarily use Linux for software dev and web browsing and Windows for gaming and Office.

By dying

Survival

The Lunar Gateway will be complete in your lifetime and and the Artemis program is underway. Who knows what will happen after that.

Both.

'None of your business, motherfucker."

Discord. I have a channel in one of my servers that’s just me.

Secureboot and DMA are two different and AFAIK unrelated things. Secureboot primarily exists to ensure that only trusted OS kernels are run on a particular device. Otherwise someone could just boot their own OS installation from wherever and then have it access your storage and other devices and thus compromise your machine. I am not entirely sure how it works but I think it uses cryptographic signatures for kernels and drivers that aren’t built into a kernel. I know that on Linux with Secureboot on if you want to use certain dynamically loaded drivers then they have to be signed. I prefer not to deal with all that so I just disable it in the firmware because no cyber criminal has physical access to my PC anyway.

DMA is just a way to get data from peripherals without CPU intervention. Without DMA every time a peripheral wanted to send your machine data it would have to trigger an interrupt (or be polled continuously) which the OS would catch and then read the data from the device. This isn’t really super practical with modern hardware hence DMA allows peripheral devices to write directly to the system’s main memory without the CPU (or the OS that runs on it) being involved at all. Then the kernel can read that data from memory whenever it sees fit to do so.

By contrast, Windows is a microkernel. It only creates an API layer for the hardware vendor to write a driver that interfaces with Windows.

NT is a hybrid kernel that is nearly monolithic.

Also you don’t seem to understand what the difference between a microkernel and a monolithic kernel is. The defining difference is what mode and address space drivers and non-core kernel subsystems run in. If they run in the higher half in a privileged CPU mode like the base kernel then you have a monolithic kernel. If they run in userspace as one or more programs then you have a microkernel. If some run in kernel space and others run in userspace you have a hybrid kernel. And if your kernel exposes hardware interfaces directly to application programs providing only protection and multiplexing of them between programs and shared libraries are used to interact with those interfaces then you have an exokernel. If the kernel mimics the underlying hardware to each program running on top of it and let’s them think they’re running on the hardware directly then you don’t have a kernel at all you have a type II hypervisor.