Linux

>linux
>well organized

Who are you quoting?

Still better than System32.

yes, that looks very organized

>linux
>well organized

>2008
Looks really clear and minimal OP.

That's actually pretty well organized when compared to uhhh windows

It's even more of a clusterfuck now that the Poettering nigger has invented Pulseaudio

Install sta.li
Install OSS
(install plan9)

PulseAudio wasn't even an issue until it became a requirement for BlueZ. I'm dreading the day that some basic component switches to exclusively support systemd.

Pulse is already on the you numbskull

It's not as bad as it seems since the graphic literally shows all possibilities. For the average Ubuntu install it just goes (gstreamer ->) pulse -> alsa -> output. Still silly but not as bad as you may think.

>install OSS
or try sndio from OpenBSD

>implying anyone still uses OSS
>implying anyone still uses ESD
>implying anyone still uses aRts
>implying anyone still uses Phonon
>implying anyone uses ClanLib
>implying anyone uses Allegro
>implying anyone uses NAS
>implying people without bluetooth use BlueZ
>implying people without firewire use FFADO
>implying JACK is used outside of music recording/production/performance
>implying PortAudio is not a niche
>implying NAS is not a niche
>implying that you can't rearrange everything into a simple, well organized stack of APIs, servers, drivers

It has its faults, but it's better than "dump everything in C:\Windows"

...

I'd just like to interject for a moment. What you're referring to as Linux, is in fact, GNU/Linux, or as I've recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.

Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called "Linux", and many of its users are not aware that it is basically the GNU system, developed by the GNU Project.

There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine's resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called "Linux" distributions are really distributions of GNU/Linux.

Did you just read whatever he wrote?

Linux has a good system structure. BSD however does it better. But the best has to be NixOS, package collision on it is literally impossible.

Better than c:\Windows\everythinghere

How does NixOS deal with PATH? Having 200 paths, each one for at most a few binaries, seems pretty impractical.

>10x stuff
>everything connected to systemd
Modern Linux.

/usr/bin is still populated, but with symlinks to the current versions of software in the /nix/store.

C:\Program Files\YourProgram\everythinghere

vs

/bin/somestuffhere
/usr/bin/somestuffhere
/usr/share/somestuffhere
/lib/somestuffhere
/etc/somestuffhere
/sbin/somestufhere
/usr/sbin/somestuffhere
/usr/locale/bin/somestuffhere
/opt/bin/somestuffhere

You forgot some stuff in the registry, appdata and my documents

Linux is a kernel.

~/somestuffhere
~/.cache/somestuffhere
~/.config/somestuffhere
~/.local/share/somestuffhere
/tmp/somestuffhere
/var/somestuffhere

I don't have anything to say about how Windows 10 handles sound.

>C:\Program Files\$program\everythinghere
because why bother making any distinctions the purpose of a program/software package
>C:\Program Files\$company\$program\everythinghere
because you should remember which company you paid money to so that you could sign an EULA and install their proprietary program

vs

>/bin/$program
because all system-required executables belong in a single place
>/usr/bin/$program
because the length of $PATH should not depend on how many programs you install
>/sbin/$program
>/usr/sbin/$program
because all superuser binaries belong in a separate place
>/etc/$program/
because all system-wide configuration belongs in a single place
>/lib
>/lib64
because all system-required shared libraries belong in a single place
>/usr/share/$program/
because the files of programs shared by all users belong in a certain place
>/usr/man/$program/
because all manuals belong in a single place
>/usr/doc/$program/
because all other documentation belongs in a single place
>/usr/include/$program/
because all headers belong in a single place
>/usr/lib/$program/
because all shared libraries belong in a single place
>/usr/lib64/$program/ 64-bit libraries should be distinguished from 32-bit libraries

>~/.cache/$program/
because all data cached a use belongs in a single place
>~/.config/$program/
because all configuration made by a user belongs in a single place
>~/.local/share/$program/
because all program files specific to a user belongs in a single place
>~/.$program/
because not everyone gives a fuck about freedesktop.org
>/tmp
because all temporary files belong in a single place
>/var/cache/$program/
>/var/lib/$program/
>/var/lock/$program/
>/var/log/$program/
>/var/run/$program/
>/var/spool/$program/
>/var/state/$program/
because all system-wide software-modified files belong in a single place

What the kekkin' kek