But this only speaks about what some GUIs lack, it's not necessarily true that GUI apps can't be composable, it's just that seldom they are made as such. The true potential of a GUI app is much richer than what terminal currently offers (unless it starts to receive capabilities usually present only in GUIs, as we can see with some of them - but then it's a GUI with the severe terminal restrictions, a strange beast).

Is this planned to be addressed/fixed? (single-client model) Maybe there were previous attempts?

No, because there's nothing to fix (at the system side).

Apps should use the right API from the right layer; when they skip something, no wonder they will miss whatever the skipped layer provides. When they do not need exclusive access to the device and want to play nice with the other apps, they should use pipewire/pulseaudio.

For 99% of apps, using ALSA directly is the wrong approach. You don't use IOKit directly in Mac apps either.

Pipewire/Pulseaudio install a plugin for ALSA library so that ALSA applications audio is rerouted to audio daemon. So apps using ALSA can work at both systems with and without an audio daemon.

At this day and age there should not be a system without an audio daemon. At least not one, that is not broken. Apps should not certainly accommodate for broken systems, and forcing workarounds for the correct ones.

Whenever Nix/NixOS gets discussed I always see same points being brought up again and again. And again. I've never seen anything which is discussing solutions or the roadmap (however distant) to solve those issues.

Can it be that nothing is happening in this regard or is that really so that people only list same cons over and over again? :)

It's like complaining about C++. It will always be there. Ignore it, it's just people venting about the fact that solving hard problems is hard.

Every time I open the site and it pops up some weird "subscribe to this and that awesome content" in my face, I immediately close it. Each time I really hope that owner has some analytics set up and they will learn that having this thing is not a good thing to do to your readers.

Same, I wonder why they keep doing it. Are they fine upsetting 50% of the users so that 5% subscribe? Or am I underestimating the sign-up rate?

Would be cool if I could control it from this webpage ;)

Actually i think you can: (if you have rights to it ofc)

http://op-webtools.web.cern.ch/op-webtools/

It looks awful with Xfce default theme. Gedit = Gnome Edit (I guess) - and it looks well and integrated really well when used in GNOME environment (gnome-shell).

So its not fair to judge it this way. Try to open some Xfce apps in GNOME and it will look like horror too (compared to gnome ones) :)

What I find funny is that this website uses flash itself.

I don't think it does. It uses swfobject2 [1], a js project, to detect if flash is installed and give you a frowny face if it is.

[1] https://code.google.com/p/swfobject/

Can't vote this comment down (not enough karma?), but I would. React is great library, it is not very constructive to call it a hack just because webcomponents are there.

I'm not saying React is a hack. I'm saying that all libraries that try to provide true "web components" that hide their implementation details for the user, are only achievable trough a "shadow dom" implementation in the browser.

Thats just a fact, based on how browser work. With the shadow-dom, customer elements, and templating you can achieve true componenets, like in uix toolkits such as Android, iOS and Java Swing.

Me too. FF 33.0.3 Linux

Interesting project. Looks like it's somewhat stalled, do you know anything about its current state/plans?