/tech/ - Technology★

Also, what else should I be wary of?

Systemd?

>>NetworkManager

What's wrong with system NetworkManager?

Get ready for 100 replies mewling about "bloat". Anyways, Wayland is genuinely good, and on Gentoo you can use pulseaudio with jack. (I still prefer ALSA + apulse.) GNOME is garbage, D-bus is okay, and NetworkManager is useless. Because you can't mention GNOME without touching on systemd, I think the concept is interesting--the execution on the other hand, is an abject failure. I hope the Funtoo project starts working on their "modern" init soon.

>PulseAudio

Pointless Poetteringware

>Gnome/GTK+3

Manages the impressive feat of growing more slower and fatter as it removes features

>dbus

yet another shit serialization protocol

>networkmanager

webscale dog shit that breaks on 90% of networks, literally using plain wpa_supplicant is easier

>pulseaudio

dunno why i'd ever use that

>gnome

bloated mobile-first (((UX))) design

>GTK at all

literally every GTK program ever spams assertion errors to stderr. and >muh object oriented API

>wayland

at least it renders to the framebuffer correctly, but the way they do it causes mouse lag (and more wrist pain due to mispredictions caused by mouse lag)

>>965343

I would use alsa if it had a decent mixer like pavucontrol

Also why isn't sndio more popular?

>>965333 (OP)

>>D-Bus

Because it's shit. Back when the initial push occurred, I tried converting one of our tools that does the kind of IPC it's intended for to it. Was amazed at how bad it was. There was no way to react to an IPC traffic jam as it provided no feedback, it would silently queue messages it couldn't deliver forever (they called this "non-blocking" which I guess technically it is), it and every message sent was 100% reliable. So a single application pushing at max rate would destroy it and itself. And destroy every program using dbus as there was no QoS at all (maybe there is now). I asked them and I got the retarded answer back that it wasn't designed to handle sending frequent messages and if I wanted to I should use it to exchange a file descriptor with a client and communicate using my own message framing over that. So basically use this massively bloated and overly complex daemon but re-implement almost everything it was supposed to be doing and in a similar way to how I was already doing it, forcing users to have it installed for no reason.

And by "overly complex", the bindings are xlib-tier insanity so most people use the glib bindings as middleware to reduce the autism but that pulls in another 5MiB+ of glib bloat. The program I was modifying was about 1MiB and I ended up increasing my dependencies by 15MiB and would have had a lot more code if I hadn't just abandoned it like everyone else did other than the desktop faggots who don't understand IPC, anyway (remember their push for CORBA?).

>NetworkManager

Obscene bloat, poor management, gets in the way of everyone doing more than run a facebook machine as it wants to do things its own way rather than Linux's which means anything even slightly advanced requires using something else.

>pulseaudio

>GNOME & anything related

>GTK+3

>wayland

Irrelevant desktop stuff. Linux is shit on the desktop.

>>965373

>Linux is shit on the desktop.

N-no it's not!

>>965333 (OP)

>D-Bus

<wanting to have one daemon that can access all processes

<the implementation is trash

>Network-Manager

<It's bloat and breaks often

>pulseaudio

<Bloat and comes with a server that's works over network

<bugs

>GNOME

<they remove features

>GTK

<QT is better

>SystemDick

<bloat, no one can understand the code

<less-secure, easier to add backdoors

<developed by (((Red Hat)))

<binary logs by default

<bugs

<poettering is tard who refuses to acknowledge the existence of bugs

<tries to become added as a dependency on all software

<tries to consume all, SystemDick is trying to be everything

>>965361

Good question. It's very comfy on OpenBSD

DBus is a genuinely good thing. PulseAudio is one of those things that would be pretty nice (its audio rerouting capabilities are insanely powerful; try to do that in Windows without shady third party kernel-installing software) if polished and with saner defaults. Wayland is good, but I think the designers are getting a bit ahead of themselves with redesigning stuff that worked for the sake of redesigning it, and backwards compatibility will be ass; I don't even want to think how terrible will games be without mouse capture, which was removed because "it's a shitty hack".

GTK is shit because it's trying to be not C despite being written in C. GNOME is shit because it is a bloated tablet-tier animationsfest which makes hides its configuration options via plugins (no, I don't want to install a plugin to hide that huge ass Accessibility button; I am not disabled and most people are not disabled, so give me a fucking option to hide it). NetworkManager is redundant.

>>965463

PulseAudio is shite compared to JACK for rerouting.

Wayland is fine, libinput handles mice and can provide an xinput fake if need be.

Much better to redesign and break shit when it hasn't been adopted instead of keeping it around for another 30 years.

>>965463

double/triple buffered vsync is a shitty hack and adds 1 frame of input lag. you can reduce the frame time from 16.66ms (60Hz) to 8.33ms (120Hz) or even further, but then you're using more CPU to do nothing, and exponentially reducing the chance of being judder-free, not to mention contradicting yourself. what other benefits does it offer? security? linux has no security

>>965333 (OP)

>D-Bus

Red Hat

>NetworkManager

Red Hat

>pulseaudio

buggy and bloated

>GNOME

They don't use their own WM, developers mostly focused on removing features and handing out diversity participation trophies.

>GTK+3

bloated

>wayland

Nothing wrong with it, an elegant piece of software that will hopefully persist despite Canonical's NIH syndrome.

I still don't get what D-Bus is even meant for

>>965467

Point is, mouse capture is not a hack. These people are not thinking of the windowed shooter usecase, in which you definitely do not want your mouse to leave the window. The way it's usually achieved is a hack, the usecase is not, and they forgot about it.

This, the way they are doing network transparency (the guy doing it seemed to have no fucking idea about nothing, judging by some comments in his blog), and the triple buffered screen make me think two things:

1) They are amateurs getting too ahead of themselves.

2) They do not believe gaming on GNU/Linux is a usecase. Which it is, despite all the memestry about it around here.

The idea of replacing X with something simpler, more modular, and granular is sound. Some of the specifics are just downright dumb.

>>965467

wacom and synaptics still broken or shit in wayland trash

>>965627

rtfm

polite sage

>>965337

Because wpa_supplicant exists.

>>965864

Is there a gui frontend for it?

>>965820

i've implemented the d-bus protocol and i still have no idea what it's for

>>965538

>GNOME

>removing features

and yet it is still a slow buggy bloated piece of modern UX bullshit

>>965877

Yes, it's called network-manager-applet.

>>965898

So that's a sarcastic no?

>>965905

wifi-menu for wpa and nmtui for NM are convenient cli interfaces

>>966094

>Have systemd as a hard dependency (that measn you cannot have it without each other)

You can use KDE without systemd on Gentoo, and that depends on NetworkManager. But it's still shit.

>>966120

>using Google's intern-maintained distro

I'm using KDE Plasma with Devuan and it's smooth as silk, everything works great.

>>966137

But I have autism, and that means I have to micromanage every part of my system, while neglecting my hygiene. Also, Devuan has pulseaudio.

>>966140

>not simply installing apulse and going poettering-free

You can even do this on Ubuntu.

>>965360

volti

>>965538

>GNOME

>not saying Red Hat

>GTK+3

>not saying Red Hat

>>965333 (OP)

You didn't even mention flatpak or pipewire.

Wayland is the only thing I've been excited for in a while.

>>966146

It's quite easy to build too.

https://github.com/i-rinat/apulse

>>966177

>You didn't even mention flatpak or pipewire.

whowhat or whatthefuck?

>>966195

Gentoo is used as a base for Chrome OS

>>966195

Gentoo is literally curated by slack-jawed transfaggot interns working for free for Jewgle you idiot.

>>966318

So? That doesn't make Gentoo maintained by Google interns. That means that it's used as a base for a Google project. The Linux kernel isn't owned by Google either, and it's used as a base for Android and Chrome OS, it isn't owned by Microsoft for being a base for Azure, and it isn't owned by Tivo for being used in their devices.

>>966357

https://www.gentoo.org/inside-gentoo/developers/

A quick random lookup of about 10 of them found none that work at Google, and none that are transfaggots, and none that are interns. About half of them were actual PhDs. How about you stop talking out of your ass, you stupid lying faggot?

>>966359

You didn't look hard enough if you couldn't find any Jewgle employees or transfaggots in that list. You argue like a Jew, as well.

>>966366

Show me.

>>965333 (OP)

>pulseaudio

it literally caused hearing loss in people due to a functionality that allowed other programs to influence global volumes, lel.

So you'd be listening to your music on half global volume with your nice hi fi headphones that need an amplifier so they're nice and drivey, and then some other shithead program set it to 100.

Bammo.

>>966217

Both Red Hat products. One is an over complicated method of distributing executable packages, and the other is a media system as complex as systemd.

>>966405

And the defaults for years caused extreme CPU usage in order to "accurately sample audio".

It was regularly forced by distros that targeted original atom CPUs, leading to garbage media playback.

>>965877

Yes. It's called wpa_gui.

>>965864

This, after I learned how to actually use wpa_supplicant I ditched NetworkManager for good and never looked back. wpa_supplicant can do everything NetworkManager can and more, while at the same time being not the least harder to use.

I don't like D-Bus because it's constantly spawning a bunch of processes and daemons for functionality that I can't use or don't want. I couldn't avoid it as a depdendency so I just did chmod -x on the whole suite. Nothing I use broke from it.

All of those are bloat from freedesktop.

essentually cancer that pulls in bloated uneccesary dependencies.

It acts as actual cancer by invading the natural way of doing things growing more and more until everything depends on it and the system dies.

I see a lot of people complaining about systemd but holy shit is Dbus a shit ton worse.

With systemd you can atleast avoid it by isntalling a distro that doesn't use it.

But with dbus almost fucking everything want it for no good reason.

>>975258

for instance, fucking glib depends on dbus.

WHICH IS USED BY A FUCK TON OF PROGRAMS.

>>975260

> equery u dev-libs/glib | grep dbus
-dbus

Feels nice being a Gentoo user.

　　　　　　　　 /　　 /ﾍ/　 /　/　 　/ 　　 / 　　／/　 /　　/ ヽ　 ＼ 　 　 　 ＼　＼

　　　　　　　 ./　＿/　/　 /　/　　 / 　　 /　 ／　/　 / 　 ∧＿ヽ 　 ＼　　　　 ヽ.　 ヽ

　　　　　　　/／　/! /　　.ｌ　 l　 ／,.-‐'フフヽ.／/　 / 　 /´ヽヽ ｀＞.､ .!　 　 　　 ',｀ヽ 〉

　　　 　 　 /　　 / |/　 　 |　 l／／ ／／　／.: /　ノ 　 /. :.:.ヽ ＼＼　｀ﾄ､ 　 　|　 | ／

　　　 　 　 { 　 ./　|| 　 　 l／　　／ン-‐＜、 :/／:/　 ./: :,ｨ─ヽ-＼ヽ. |　| 　　| 　|′

　 　 　 　　 ＼､.--|l-‐"_,. -‐",. =,＝￢ﾐ､／: : :/　 /: : : ノﾞ,ニ＝=ミ､ |　|　 　| 　|

　　　　　　　　/ ￣||￣　　　{: :く 　 ﾄ-'　　}　 : : / .／: : : : :　ﾄ-' 　 }　// /　　 j l　!

　　　　　　　 /　　 .!',　 　 　 ＼:.｀　ゝ　-‐'　　./／　　　　　　ー-- 　./ /　　 /j | /

　　 　 　 　 / 　 　 ', ヽ　　　＼ゝ､　 　 　 　 ノ　: : !　　　　 　 　 　 ノ／　 .／/ノ'

　　　 　 　./　　　 .∧　＼　　　＼　　　　　　　　 　 　 　 　 　-┐ ∠ -‐''"　/

　　 　 　 /　　 　 /,ハ ＝ ゝﾍ､_　 ゝ､ 　 　 　 　 　 　 　 ＿_ノ）　 　 　 /〃/

　　　　 /　　 　 //　　ヽ〃 ヾ ヽ￣￣ 　 ､_,..　-－'' ´￣ 　 ／　　　　 /＜/

　　　／　　　 ,r'"´￣了ゝ､rｰ､　ヽ　 　 　 ｀　ー──‐ ''　´　　　　　/ｌｉヾ/

　 ／　　　 ／ ゝ, -‐'7｀ーｲ__.｣､ 　＼　　　　 　 　 ｰ　 　 　 　 　 ／　　　|

／　　　, f´￣／ 　 /　 ノ／ヽゝﾝ‐.､V丶、　　　 　 　 　 　 　 ／｜ 　 　 |

　　　／ 之／　　 /　　／　　 ヽ ヽノ1ヽ-､.｀丶､　 　 _,. -‐'"´ 　/|ヾ ｢l〃|

　 ／　｢　/ 　 　 /　／　　 　 　',　∟|　ヽ ＼　 　￣ 　 /　　 ／　|＝　＝l

／　　.ゝ/ 　 　 /／　　　　 　 .ｉ ｌ , -ｲ 　 ヽ. ヽ　 　　 ,ｲヽ ／　　｜〃iｌ ヾl

　　　,r/　　　　/　　　　　　　 ｜| L.､|　　　l　 ｀丶、 f |　 ｀ヽ、　｜　　 　 !

　 ／./　　 　 /　　 　 　 　 　 ｜|　ヽjヾ||〃ｌ　 ,. ‐-､ヽｌ　 　_　 ＼| 　 　　　ヽ

／　/　 　 　/　　　　　　　　　｜|　ノj＝ ＝|／　, --ﾍ}⌒}´_＼　 ＼　､ ヾ r ヽ

>>975437

desu

Hey there. I'm sitting here with a relatively fresh gentoo and I want to avoid most of these, except GTK and wayland maybe. I don't really have a problem with the Network Manager either but I don't need it.

I need software mixing capabilities like pulseaudio though because otherwise, with my audio ffado interface only one application can play at once. Which route to go and what depends on what? No systemd installation.

>>966195

>>Google's intern-maintained distro

Ohhh, that explains Will Hubbs I guess...

dbus is harmful because of its implementation. It can, for instance, pile up messages consuming more memory than needed, drop messages without warning, the list goes on. This article explains better:

https://dvdhrm.github.io/rethinking-the-dbus-message-bus/

The funny thing is that the idea of a dbus-like system was already implemented in a better and simpler way as the plumber on Plan9. As noted by a Debian developer:

https://lwn.net/Articles/453529/

Networkmanager (nmcli(1), nmtui(1) among others) is a wrapper around stuff like wpa_supplicant(8) so, in short, it is unnecessary and learning it won't bring you benefits like learning ifconfig(8) and route(8) (now just ip(8) on some systems).

I dunno about the others.

>>975595

If you need flexible audio, use jackaudio, where you can route everything into everything.

Add USE="jack" into make.conf

emerge --changed-use @world and then emerge qjackctl

If you need applications that can't into jack, you'll need to route audio from alsa through loopback device, which means non-trivial /etc/asound.conf config and other stuff. I can provide the configs if needed.

>>979480

>I can provide the configs if needed.

Please do

>>975280

weird. I tried emerging glib without dbus and portage shouted at me that it must use dbus.

>>965473

Is this (the image) a Permutation City reference?

>>965343

>PulseAudio

>pointless

Meanwhile I can chat with my friends, play Don't Starve Together and listen to my music and seamlessly control where sound comes out from and control the volume of each stream individually. I could also pipe my music through the mic if I wanted to. All in real time, without modifying any .config files or restarting the server.

Audio in GNU is garbage, and PulseAudio is a mediocre hack, but it beats using ALSA or Jack for everything that doesn't care about latency.

>>980515

I ALSA don't give JACK shit about your PULSE audio when shell scripts could do all of that.

>>979480

Oh cool, didn't know this thread was still alive. Gotta try using jack, definitely. But wasn't there a 5th, relatively new alternative to oss/alsa/pulse/jack too?

>>980518

>>979480

But why would joy do that when Pulse exists? That's just overcomplicating the process for no reason.

>>980523

I can only speak for myself here but Pulse just doesn't seem to be accurate. There are little crackles in the audio that make it hard to bear on good headphones. I checked the levels qnd everything because it sounds like clipping, but it isn't. It's either little dropouts or some kind of coil whine (which would be strange as it isn't there under win). Jack doesn't do that but has longer dropout occasionally (xruns).

My setup is somewhat pecculiar though as I'm using a ffado card, so maybe there just is no perfection in that. Straight alsa, well it's been a while but I think it had the best audio quality. It sucks though when only one application can play audio at the same time.

Also pulse just steals away your control and just always does something you didn't ask for. It's as annoying as the automounting of devices on some distros.

I'm hats this about alsa only allowing one application at a time? I've been using it for years with multiple programs playing sound at once just fine. Did I break the matrix?

>>979598

You may need to adjust periods, you'll also have to match frequency to the one you set in qjackctl.

/etc/asound.conf: https://0x0.st/sYj6.txt

Add modules="snd-aloop" into /etc/conf.d/modules

Then you'll always need to run the following upon qjackctl startup (you can specify that in configuration)

# create jack device connected to the loopback
/usr/bin/alsa_out -j ploop -dploop -q 1 2>&1 1> /dev/null &
/usr/bin/alsa_in -j  cloop -dcloop -q 1 2>&1 1> /dev/null &

## give it some time before connecting to system ports
#sleep 1

# cloop ports -> jack output ports 
jack_connect cloop:capture_1 system:playback_1
jack_connect cloop:capture_2 system:playback_2

# system microphone to "ploop" ports  
jack_connect system:capture_1 ploop:playback_1
jack_connect system:capture_2 ploop:playback_2

And I almost forgot, but you'll also need to set some permissions. I think you'll need to add yourself into the audio group and add (tabs, not spaces)

@audio          -       rtprio          99
@audio		-	memlock		unlimited

You may have to create that group yourself and then tell jack to use it. Or not, I'm not sure. There are some guides on the official jack website.

>>980521

I think redhat was working on something that should be able to route video and audio from containers and if I recall correctly, it should also have capabilities similar to jack.

>>980523

It also makes recording and stuff easier.

>>980533

Forgot to uncomment the sleep 1 bit, you should do that.

>>980532

ALSA can do everything Pulse can. Pulse just makes it easier to do.

With Pulse you can play sound through network into other computers, manage several outputs/inputs at the same time, select which application can use a specific input/output as well as it's volume, pipe the output of an application to an input, manage Bluetooth devices and multiple sound cards, etcetera. All in real time. At the end of the day it all plays through ALSA though.

>>980539

Whats the alsa equivalent of virtual sinks and sources? I would love to ditch pulseaudio, but I don't know how to pipe the output of one program to the input of another. I tried jack a few years ago and was too much of a brainlet to get it to work.

>>979480

>jack

Literally nothing that can't be done in a .asoundrc

>>979603

if you got gtk3 with +X flag, it'll pull in dbus regardless

>>980539

I have -gtk3 set in make.conf. It was the test flag that did it. I set -test for glib in package.use and it compiled without dbus just fine.

polite sage. Forgot to mention LibreOffice tries to pull in dbus if you have the bluetooth flag set. It's set in the desktop profile. another one to add to package.use if you aren't using a bare bones profile

>>980532

It depends on whether your soundcard supports mixing. if it does, like all the consumer onboard ones, it'll work. If they don't you'll ne pulse or anything as a software mixer or there'll only be one app able to play at the same time indeed

>D-Bus

Complete trainwreck of a protocol that needs wrapper libraries to be even remotely usable.

>NetworkManager

Program wrapper that somehow manages to be less usable than the program it wraps.

>pulseaudio

Broken shit on release, terrible hidden defaults that could actually cause hearing damage. Most people don't need it, those that do need it should use the completely superior Jack.

>GNOME & anything related

GNOME is a bunch of retard developers trying to be open source apple. Even though they constantly remove features to pander to retards and "build their brand" (quote), it manages to become larger every time.

>GTK+3

Using a GTK3 program should instantly tell you why. Also, hard dependency on dbus and ten million accessibility daemons for no good reason.

>wayland

"Let's fix X11 by removing the stuff people don't need. Oops, they actually needed that. Oops, they actually needed that, too. Oops, …"

The Wayland people have no fucking clue how to prevent the major thing that killed off X11 development, the extension mess. In ten years Wayland will be the same unmaintainable clusterfuck that X11 is today. Also the typical dishonest freedesktop.org advertising. Remember "there are no key loggers on Wayland" and "just use VNC lol"?

Additionally, they try to push other crapware through their position, like the client-side decoration garbage. "Just link this 2MB GUI toolkit into your simple X11 program so window decorations work under our new protocol lol, Linux desktop 2018!"

>>965343

>Pointless Poetteringware

but muh per-application volume levels

>>980797

>>pulseaudio

>Broken shit on release, terrible hidden defaults that could actually cause hearing damage.

How? Are you talking about its clipping-like artifacts?

>>980797

>>GTK+3

>Using a GTK3 program should instantly tell you why. Also, hard dependency on dbus and ten million accessibility daemons for no good reason.

Have you actually managed to keep it (and dbus) out of your setup? Once I try to avoid it nothing ever can be emerged.

>D-Bus

Not that bad. It's just a simplified IPC.

It is bloat though.

>NetworkManager

It's just bloat. I only use it on laptops where I may need to change my connection easily but really wicd works just as well for that.

I would use wicd if it were installed by default on Slackware

>pulseaudio

Been using it since Slackware adopted it. I never really cared for audio junk much before but it makes things easier for me using obs and stuff. pavucontrol is easy to use.

Yeah I like some things being spoonfed to me.

>GNOME & anything related

GNOME is pure cancerous bloat. Always has been from day 1 and always will be.

>GTK+3

It's not that bad but I like Qt, FLTK, or even gtkmm better for writing though.

I won't get into what I like about what but I will say that GTK+3 going full on MCV for a simple list view is complete stupidity.

>wayland

"oh we can do everything better than X11 because X11 is old and messy"

then there were all the insufferable wayland fanboys.

>proceeds to find out why X11 is the way it is

>gets their ass completely wrecked for years by old ass crufty code

At least they tried though

>>980847

Normally, system-level volume and application level volume stack, so if system is at 33% and the application at 200%, you'll have the volume at 66% of the normal one. This is predictable and makes sense. However, the idiots at Microsoft needed to "fix" this because apparently the average user is too retarded for multiplication. So they made a horrible thing where if you raise the application volume over the system volume, the system volume goes up as well, because that's "intuitive" according to some UX designer shitstain.

Now the Pulseaudio people wouldn't be who they are if they didn't implement this too, because surely it will bring forth the Year of the Linux Desktop. Of course, they turned it on by default and documented it so badly that lots of maintainers didn't even know about that option.

Unfortunately, many programs set their volume on startup, which together with the system-wide volume increase then frequently used to set the volume to ear rape levels. This happened in particular with Youtube videos back in the day. Taking off your headphones before you start any video was FUN. By now this is probably fixed, but I'll forever remember it as a prime example of why Poettering is a fucking moron.

>>980849

I did, but I had to switch a few programs out. Note that Firefox has a hard dependency on GTK3 (and thus dbus) now.

>>980864

And of course, right after posting I remember how this shit was called. "Flat volumes". Jewgling for that gave me this post that might illuminate the problem more than my adhoc rant. >Reddit, but what can you do.

https://www.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_volumes_in_pulseaudio_a/

>>980797

The problem with X is not the extensions, but rather that the design itself is shit and unsuitable for modern PCs. Wayland was made to be secure and to add everything as extensions.

Personally, I'd prefer Mir a thousand times over Wayland.

>>980864

That's still the default on most distros except Arch. That's technically not a bug, but intended behaviour. Not that it's any less of a retarded default.

The only problem I've ever had with Pulse is a long standing Firefox bug: whenever it starts playing an HTML5 video, Firefox sets its volume to 100 % which is essentially earrape. This only happens when Pavucontrol is installed, which means it's a fuck up on Mozilla's part.

>>980895

>the design itself is shit and unsuitable for modern PCs. Wayland was made to be secure

Does this even mean anything?

>>980900

>Any program running as any user with no isolation can steal everything you type / click / see.

Great job Xorg really well designed system.

>>980906

Oh, it's muh keyloggers again.

>>980900

>X.org doesn't automatically switch between desktop resolutions if you have a full screen application with a custom resolution running

>X.org doesn't restore gamma (which can be perceived as increased brightness) settings on application exit

>X.org allows applications to exclusively grab keyboard and mouse input. If such applications misbehave you are left with a system you cannot manage

>Keyboard handling in X.org is broken by design - when you have a pop up or an open menu, global keyboard shortcuts/​keybindings don't work

>For VM applications keyboard handling is incomplete

>X.org architecture is inherently insecure - even if you run a desktop GUI application under a different user in your desktop session, e.g. using sudo and xhost, then that "foreign" application can grab any input events and also make screenshots of the entire screen.

>X.org server currently has no means of permanently storing and restoring settings changed by the user (xrender settings, Xv settings, etc.)

>X.org has no means of providing a tear-free experience, it's only available if you're running a compositing window manager in the OpenGL mode with vsync-to-blank enabled.

>X.org is not multithreaded. Certain applications running intensive graphical operations can easily freeze your desktop (a simple easily reproducible example: run Adobe Photoshop 7.0 under Wine, open a big enough image and apply a sophisticated filter - see your graphical session die completely until Photoshop finishes its operation).

>There's currently no way to configure mouse scroll speed/acceleration under X.org. Some mice models scroll erratically under X.org.

>There's no way to replace/​upgrade/​downgrade X.org graphics drivers on the fly (simply put - to restart X server while retaining a user session and running applications).

>Adding custom modelines in Linux is a major PITA.

>X.org totally sucks (IOW doesn't work at all in regard to old applications) when it comes to supporting tiled displays, for instance modern 4K displays (Dell UP3214Q, Dell UP2414Q, ASUS PQ321QE, Seiko TVs and others). This is yet another architectural limitation.

>HiDPI support is pretty much non-existent

>Fast user-switching (and also concurrent users' sessions) under X.org works very badly and is implemented as a dirty hack: for every user a new X.org server is started. It's possible to login twice under the same account while not being able to run many applications due to errors caused by concurrent access to the same files

>>980900

Oh, and the source for >>980921 is: https://itvision.altervista.org/why.linux.is.not.ready.for.the.desktop.current.html

It contains many links to bug reports and such.

>the basic problem with X11 as a display system for desktop systems today is that none of the apps written for it actually use X11. Your multiple monitors work because of Xrandr - which isn't part of X11. Your 3D effects work by bypassing the X server and making OpenGL calls - not part of X11. It's supported by all the hardware vendors - and most of that support is in kernel drivers, not in the X server itself. VT switching works... more... or... less... until you'd actually like to switch VT before you get back from your coffee break, or your X server doesn't recover correctly. And, in case you missed it, they're not provided by X11. And I'm not sure what boot times have to do with it?

>Your apps draw using Cairo or similar, not X11. They draw onto a buffer provided by the compositing extension, not X11. The buffer gets put into video memory by the compositor, not X11

>So why exactly are we keeping X11 hanging around? Why not get rid of it and halve the size of the display server code base, making it much easier to program against in the process? Why are we carting around a heuge amount of code that is of no modern relevance except to be able to claim that it is an X server? The maintenance burden of the current X server is too much and any thought of adding new capabilities horrific.

https://m.slashdot.org/thread/40603337

Here's another article talking about X: https://www.phoronix.com/scan.php?page=article&item=x_wayland_situation&num=1

The X11 devs also want to replace X11: https://www.x.org/wiki/Development/X12/#Errors.2C_Oversights_and_Omissions

On screen lockers and X:

http://blog.martin-graesslin.com/blog/2015/01/why-screen-lockers-on-x11-cannot-be-secure/

More X vulnerabilities: https://lists.x.org/archives/xorg-announce/2014-December/002500.html

>>980925

>there are some flaws with X as currently implemented

>instead of fixing them, let's just create a whole new windowing system which will be trustworthy because the government goons at Red Hat are making it

Sorry faggot I'll be sticking with X.

>>980864

hm, what about seamonkey and chromium? I guess netsurf or w3m won't be enough.

>>980878

>Flat volumes

Hm, you really mean the system volume is raised, the mixers master? I haven't noticed that ever, neither on Linux nor on Windows. On my Arch setup (which has pulse, contrary to my gentoo) The master volume control sits peacefully at 85%. Then on the other hand, applications putting out audio at clipping levels happens all the time. I try not to ever have any volume control in the (digital) signal chain at 100%, with a top down priority. I don't know if this actually true in the digital realm, but I approach it kind of like I would approach it in the analog realm: First I see the source is at a safe level. Then I, less carefully, back off the master a little. My reasoning here would obviously be, that the signal can already clip before ever hitting the DAC because there always might be some DSP algorithm in the signal chain that can clip. Once you've brought it to the analog realm clipping-free, it's not that much of a problem, most mixers even sound relatively clean when you hit the reds a little. But digital, once you're over 0 your ears will get cancer and depending on the volume your tweeters might burn.

But the thing with pulse is, it doesn't even seem to even matter anymore if it's clipping, because there's that jitter going on thats just as annoying. Still not gonna boot Windows - lots of vinyl to listen to

>>980935

>Muh Red Hat, muh ebil gubmint

They could easily infiltrate the X development or hell, just infiltrate the maintainers of any big binary distro or make an AUR/PPA and serve users modified versions of any program, since any program under X can read and modify the inputs and contents of the screen.

>fixing them

How are they supposed to fix the lack of multithread, permissions and the clusterfuck that are inputs without rewriting the entire thing? That's the whole point of Wayland (which, by the way, has many of X11's developers.)

>>980936

That's because Arch and Ubuntu are the only distros that disable flat levels by default.

>>980895

>>980925

X11 is an abomination, it makes me wanna shitpost about putting 3D drivers into the kernel so that we can blur out the init script log after booting and fade in the login screen with a similarly cool way (It's just a login shell though. Maybe an openGL rendered ncurses window). Then there'll be a sexy computer voice greeting you. I mean, why not, after all, finally make the future like what we imagined it to in 80's and 90's movies?

>>980895

That doesn't really address my point. The developers have no plan how to prevent Wayland from turning into the same clusterfuck X11 is now, and the shortsightedness so far doesn't inspire confidence in me that they won't need one. Will they just continually start over from scratch in the style of GNOME?

>This only happens when Pavucontrol is installed, which means it's a fuck up on Mozilla's part.

You'll have to explain this logic to me.

>>980936

I haven't tried Seamonkey or Chromium, but I would expect at least chromium to pull in even more cancer. Lynx is surprisingly usable for a lot of things, even though initial configuration is somewhat of a pain in the arse because you have to explicitly enable in a config that certain config options can be changed. Don't ask me why.

Right now I'm still keeping the last GTK2 Firefox around for the few incompatible sites I need to use, but when support for that is dropped (or it becomes too much of a security issue) I'll have to look for something else. Maybe somebody will have written a small shell on top of cargo or something similar by then.

>Hm, you really mean the system volume is raised, the mixers master?

I'm pretty sure it was, but I've been Pulseaudio-free for several years now. You should be able to reproduce this behaviour on Windows 7 at least.

>>980942

>he thinks X needs to be multi threaded

It ran fine on a single CPU running at 8 MHz and hasn't changed much since. How do we make ls or cd multi threaded?

You fucking cuck.

>>980945

You're samefagging now, this board really needs IDs.

>>980948

>That doesn't really address my point. The developers have no plan how to prevent Wayland from turning into the same clusterfuck X11 is now, and the shortsightedness so far doesn't inspire confidence in me that they won't need one. Will they just continually start over from scratch in the style of GNOME?

The Wayland devs have made many, many stupid decisions. That's why they worked with X, seems to be kind of a requisite.

Wayland has also it's shortcomings: XWayland is apparently locked at 60 FPS max, Wayland lacks many functions, introduces input lag and the idea of putting everything into the window manager is stupid, wastes developer's time and means that once again every DE will have to implement basic stuff like font rendering and mouse acceleration by themselves.

Wayland is shit, but that doesn't mean X is any good. If anything Wayland is at least safer than X.

Mir would've been a better solution, just like Upstart would've been better than systemd; but then again Canonical is stupid and the community is too busy sucking Red Hat's cock to support them.

>>This only happens when Pavucontrol is installed, which means it's a fuck up on Mozilla's part.

>You'll have to explain this logic to me.

The bug has been reported several times and the solution is always "uninstall Pavucontrol."

Since it works fine without Pavucontrol and Firefox is the only program to do this, I can only assume either Firefox or Pavucontrol are at fault. However, Firefox should not set the volume to the max when playing a HTML5 stream.

>>980950

>>he thinks X needs to be multi threaded

>It ran fine on a single CPU running at 8 MHz and hasn't changed much since

A program could easily crash the entire X session and bring down all other programs with it.

>How do we make ls or cd multi threaded?

No since their operation isn't affected by the amount of threads it uses.

>You fucking cuck.

No u

>You're samefagging now, this board really needs IDs.

?

>>980972

>A program could easily crash the entire X session and bring down all other programs with it.

>easily

Programs like that either don't get installed, or get fixed promptly. Anyway X is extremely lightweight, why go looking for a solution to a problem that doesn't exist?

Sorry, nobody's interested in your CIAnigger Wayland shit.

>>980997

OpenGL at this point tends to work perfectly on X, unless you're an NVIDIA cuck anyway.

>>980983

Enjoy your keyloggers, lack of vsync and retarded design then.

>>980913

It's still true.