Linux has become too bloated and mainstream. It is time for programmers to write their own compilers and operating systems once more.
>>109101108Just install gentoo
>>109101149Alpine and Gentoo don't fix the 50 million lines of kernel bloat
>>109101175Let me guess, drivers = bloat?
>>109101182I mean, if you are conditionally compiling for your exact hardware configuration, then you've solved the driver bloat problem. If you aren't doing that, then yes the compiled code literally is a waste of memory.But beyond that, virtual memory, scheduling, power management, SE Linux etc are all bloat. The N64 had basically none of that.
>>109101108If you weren't the absolute retard you are, you'd realize that when you prepare your own kernel for compilation, you can choose what features you want and that you can make the kernel as lean as you want. Your shitty "I wasted 2 years of my life on this" "small kernel" won't be able to compete with Linux in any metric.
>>109101245I addressed that above, but furthermore there are just approaches in the kernel that are too general for maximum performance. You don't need a scheduler, virtual memory, or power management at all, for example.Why be allergic to understanding how your hardware was intended to be programmed?
>>109101207>>109101260That would be since the N64 only ever ran one program at a time and that program could enjoy full access to your system because, what would it do, erase the save files on its own cartridge?If you want to run something like this today, you can. Unikernels are everywhere. There are even patches that compile Linux + an application as a unikernel.Meanwhile, on every normal system configuration, I'm happy that I can run multiple programs, that they can't interfere with each other, access my hardware or without going through the kernel which does access checks.My hardware was intended to run multiple programs. That would be why it has things like multiple cores, a programmable timer or an MMU and it was intended to have power management, which is why it has things such as ACPI and P-states and C-states.
>>109101271Name a moment where you truly wanted to run multiple programs at once on your computer. They are vastly outweighed by the moments where you only wanted one program. Before "streaming" and "screen recordings" existed, we had analog recording solutions. Each layer of assumption required for multiprocessing adds needless complexity that makes hardware and software so difficult to produce that you end up in 2026 with 150 million lines of bloat and a maximum of five companies on earth who manufacture devices for 8 billion people, all to achieve functionality not meaningfully more than a PS2, nokia, and a handycam could have done 26 years ago. And don't get me started on web browsers.
>>109101314Oh, okay. You're not just retarded, but also schizo. I'm sorry I wasted my time in your thread.
>>109101321i'm sorry i couldn't convert you to my church, king
>>109101108I used to work with a guy who was one of the many volunteer gcc port maintainers. he was one in a million. anyways he moved to another country to work for goldman sachs.
>>109101314>>109101271For most programs I think multiprocess OS makes sense.But for anything that expects real-time interaction I'd prefer it came on a read-only usb stick with a minimal OS, expecting some "standard" hardware api, and run baremetal.
>>109101207unloaded modules aren’t in memory though
We need a modern command line OS
>>109102065I'll make the logo!
>>1091011826 different MAC layers and various frameworks only used by one oriental telecom company each is pretty ridiculous. Not to mention parallel implementations of so many features.
>>109101108What's it like to be beautiful and have sex?
>>109101149based as fuck, Gentoo+Mate=love
>>109102246boring, women are pure evil, cold, conniving. learn to be happy on your own. chase wealth and vision. Become someone of value and women chase you. Women can't fathom a happy man.
>>109102282>chase wealthwhy do they always want so much money
