Linux

48255 readers

925 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

166

Are there any things in Linux that need to be started over from scratch? (lemmy.ca)

submitted 7 months ago by sepulcher@lemmy.ca to c/linux@lemmy.ml

269 comments fedilink hide all child comments

I'm curious how software can be created and evolve over time. I'm afraid that at some point, we'll realize there are issues with the software we're using that can only be remedied by massive changes or a complete rewrite.

Are there any instances of this happening? Where something is designed with a flaw that doesn't get realized until much later, necessitating scrapping the whole thing and starting from scratch?

you are viewing a single comment's thread
view the rest of the comments

[–] bjoern_tantau@swg-empire.de 109 points 7 months ago* (last edited 7 months ago) (2 children)

Happens all the time on Linux. The current instance would be the shift from X11 to Wayland.

The first thing I noticed was when the audio system switched from OSS to ALSA.

[–] Max_P@lemmy.max-p.me 73 points 7 months ago (1 children)

And then ALSA to all those barely functional audio daemons to PulseAudio, and then again to PipeWire. That sure one took a few tries to figure out right.

[–] bjoern_tantau@swg-empire.de 41 points 7 months ago (1 children)

And the strangest thing about that is that neither PulseAudio nor Pipewire are replacing anything. ALSA and PulseAudio are still there while I handle my audio through Pipewire.

[–] angel@iusearchlinux.fyi 28 points 7 months ago* (last edited 7 months ago) (1 children)

How is PulseAudio still there? I mean, sure the protocol is still there, but it’s handled by pipewire-pulse on most systems nowadays ~~(KDE specifically requires PipeWire)~~.

Also, PulseAudio was never designed to replace ALSA, it’s sitting on top of ALSA to abstract some complexity from the programs, that would arise if they were to use ALSA directly.

[–] lemmyvore@feddit.nl 9 points 7 months ago (1 children)

Pulse itself is not there but its functionality is (and they even preserved its interface and pactl). PipeWire is a superset of audio features from Pulse and Jack combined with video.

[–] tetris11@lemmy.ml 9 points 7 months ago* (last edited 7 months ago)

For anyone wondering: Alsa does sound card detection and basic IO at the kernel level, Pulse takes ALSA devices and does audio mixing at the user/system level. Pipe does what Pulse does but more and even includes video devices

[–] pete_the_cat@lemmy.world -1 points 7 months ago (1 children)

And then from ALSA to PulseAudio haha

[–] Molecular0079@lemmy.world 6 points 7 months ago

They're at different layers of the audio stack though so not really replacing.