Actual problems with linux

92 replies
9 attachments
Started >30d ago

Guix has no software though

Replies: >>2480

[DE] [TOR]

I don't see any free software missing from the guix repo THOUGH


[DE] [TOR]

>>783
Alpine Linux is a server OS, not a laptop OS.
Replies: >>10404

[US-TX]

>>1156
wtf just compile from sauce

[US-TX]

>>936
yes

[US-TX]

>>779
i triedinstalling void and it wouldn't work on my fucking intel only laptop and intel is the #1 hardware for open sores. this stupid fucking bullshit is so fucking crazy it doesn't work on 8 year old intel hardware

once again only the bullshit just works

[SE] [TOR]

I think we just need to appropriate and invade (just like troons did) small oss projects, like NetBSD, which hasn't been totally destroyed by them

[SE]

linuxVsBSDsFS.jpg
linuxVsBSDsFS.jpg
OpenBSD supremacy.
Linux has many big issues that make me angry.
Attachments:
Replies: >>10409


>>2479
>Alpine Linux is a server OS, not a laptop OS.
It works fine as a laptop OS.
Replies: >>10414


>>10403
Basilisk is not available for OpenBSD therefore it's rubbish

[NL]

>awful software distribution, especially for proprietary
having a list of official packages directly from the distros and if there is anything you want yourself you can just flatpak , download the files and compile it yourself if not made for your distro. I don't see how this is worse than hunting and discovering .exe's to download for windows seems like you a problem there.
>corpo tranimals running every project, making it subject to die overnight out of nowhere(just like the devs)
there is no corpo bloat in my pc are you using ubuntu
>insane defaults everywhere, often not following any standards at all
it's because you're using shit , try using suckless software if you can wrap your head anything more than GUI point and click software
>the "customization" that's often advertised is massively exaggerated, instead of having 100 different choices for each part of the system, realistically you get like 2-5 at most with even less being of high quality, which is even debatable
Who is advertising this.. I can change any part of my system at will? I don't like my i3 wm bar at the top of the screen? I can change it to anything even program my own and use that instead.. make it however I want to look

Your thread as a whole: I've used ubuntu for years , I don't know what I'm doing , I can't make anything of my own , I love my propriety software , i was better calling home on microsoft


>>10404
>its a server os
>alpine works fine on my laptop

Any distro can be used as a server.. most server distros can be used normally , Think to yourself what the fuck is a server distro and what makes it different. I can install arch with no display manager , no wm or de and run the server simply based on terminal and it'll make a far cleaner and efficient server versus any " server distro "
Replies: >>10418


>>10414
Alpine is just Arch with muslc, a better init/configuration system, and a release model that doesn't require constant maintenance.

[US-HI]
[AutoMod] action=keep R:9 E:10 N:10 C:10 | Highly relevant to the thread's topic, provides a detailed and structured critique of Linux's kernel with multiple points of improvement, and introduces fresh technical insights (e.g., firmware binaries, syscall redundancy, architectural support).

Linux is bad because:
1)The kernel is bad (composed of 40% firmware binaries)
2)The kernel is bad (the devteam nearly never throws away old code)
3)The kernel is bad (inconsistent code quality, style(7) is hardly ever applied)
4)The kernel is bad (takes hours of waiting to just git clone and build a tiny executable)
5)The kernel is bad (constant CVES remediated by OpenBSD plagarism)
6)The kernel is bad(linus known for accepting obfuscated code)
7)The kernel is bad(linus accepts non-free drivers)
8)The kernel is bad(initially a sys-V UNIX freeware clone, now has no identity/goal)
9)The kernel is bad(500 syscalls are VERY excessive for a system with file-heavy I/O)
10)The kernel is bad(support for awful architectures like x86 and POWERPC)
11)The kernel is bad(grows massively, even Linus claimed it was 'bloated' in c.2005)
12)The kernel is bad(dynamically loads modules instead of text-based configuration)
13)The kernel is bad(The allocator often overcommits and has NUMA locality issues)
14)The kernel is bad(The scheduler is unpredictable, over-configurable heuristic soup)
15)The kernel is bad (Poorly-implemented concurrency)
16)The kernel is bad(Supports inexcusably terrible hardware like modern GPUs & NVMe)
17)The kernel is bad(Has Rust, a lang with poor backwards compatibility & performance)

...This isnt even to speak of DEs, GNU, Poetteringware, xwindows, sys-V init, XDG-complaince, balkanisation, awful package naming and so on and so forth

[AU]
[AutoMod] action=keep R:7 E:8 N:3 C:9 | The post is constructive, appreciative of Slackware’s stability, and provides a specific suggestion for alternatives like GoboLinux. It avoids inflammatory language and focuses on practical improvements.

Slackware has given me no problem lately on a test laptop. sboinstall just works. I get what I need only. If only GoboLinux based off of slack..

[AutoMod] action=queue R:2 E:3 N:1 C:1 | The post is a crude and dismissive remark ('just a bunch of morons that know nothing about anything') directed at an entire community or group of users, rather than addressing a specific issue or constructive criticism. While the thread is about technical problems with Linux, the post itself lacks constructive engagement and contributes to a negative, nonproductive tone.

just a bunch of morons that know nothing about anything

[DE]
[AutoMod] action=queue R:3 E:2 N:1 C:1 | The post contains a direct quote of a religious verse (Matthew 6:21) in the context of a tech discussion, which is not constructive or relevant to the thread's focus on Linux issues. While the verse itself is not inherently offensive, its abrupt insertion into a technical debate disrupts the thread’s purpose and tone. The post does not contribute meaningful discussion or address the original poster’s concerns about Linux’s software distribution, corporate influence, or defaults.

Matthew 6:21

>actual problems with linux
the learning curve + using distros other than debian (and close derivatives)
that's it.
i enjoy my lightning fast and stable gtk2 only desktop.
of course if you are still in your gaming, java+wasm enabled bloated corporate browser, shiny new software phase than you have much to learn.
i would stop playing with electric toys before id, age verification comes around if i were you, at least just one computer you have should be tor only, lightweight, encrypted, anonymous, etc.
i enjoy making things work on linux more than watching 5 minute ads on jewtube and having microdicks advertisement telemetry 8gb spyware idle with ai screenshotting my desktop.
user-friendly distros are a meme, bleeding edge/rolling muh updoots is a meme.
i understand the corporate defective design of modern linux, you can go back in some cases 10+ years with debian repos.
if you want an OS recommendation: devuan (its 99% debian)
>t. less than a year of real linux experience

you can only cure distrohopping when your computer is truly yours.

[LU] [TOR]
[AutoMod] action=keep R:9 E:8 N:9 C:8 | The post offers a deep, well-articulated critique of the Linux development structure. The writing is engaging and uses strong analogies effectively. It fits well within a serious tech discussion.

You scratch my back, I scratch yours.png
You scratch my back, I scratch yours.png
Linux's big weakness for me that I've seen is that it puts too much power in the hands of too few people. This wasn't so bad a few years ago before every project decided to grow a CoC and slap everyone with it, but in a post-CoC world the entire Linux development hierarchy is very similar to a collection of third world dictators. Each one trying to play showmanship with one another while they play a notoriously tenuous game of "I'm not touching you" with their userbase. Each time unilaterally deciding to remove or change features, much to the unpopular protest of the users, which get responded with "So? I'm not changing it. You won't change it. Stop complaining, or I'll ban you, CoC reasons, this is harassment, etc."

This has also resulted in a culture of favoritism and back-scratching, much like third world dictatorships which operate on favors and bribes. Take this exchange, for example, two developers working on a piece of software made for other developers. The play being to not argue a technical merit but to instead remind the developer about who took his side during the Main-Master Git renaming debacle that happened several years ago. The debacle that resulted in the mass permabanning of hundreds of users from multiple projects and breaking hundreds of projects more.

Illustrating that, again, technical merit takes a backseat to backroom dealings, and politics of projects is about favor collecting over making projects of technical merit. You scratch my CoC and I scratch yours, as it were.

[US-FL]

Reply

Posting anonymously. Your IP address will be recorded for rate limiting purposes.





Max 10MB per file. Allowed: images, videos, audio, PDF, text, zip