The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
GNU Abyss said:
The browsers are the hardest GTK dependency that people tend to have installed.
Click to expand...
I looked at this in the past, and your alternatives are pretty crap.
You can use the KDE browsers Falkon or Konqueror, they run using Chromium these days (qtwebengine) which works fine for the modern web but last time I looked they had no extensions support, which was a deal breaker.
Falkon does come with an adblocker and userscript manager out of the box at least, so its not totally unusable. Can't remember if Konqueror did.
A shame too since they are both really nice browsers. Falkon is super quick, lightweight and has no telemetry, if it somehow got support for Chromium extensions I would switch instantly. Konqueror is a bit more clunky and old school but some may prefer it.

Vivaldi in Gentoo has use flags to remove GTK support in favour of Qt, which seems strange to me as its proprietary software only shipped as binaries.
No other distribution or Chromium browser seems to have this option available unfortunately, which is a shame as the Qt version runs way better under KDE with far less bugs.
1749818825004.webp
Pretty much every other application you can think of has a valid Qt/KDE replacement you can switch to, so its not too difficult to stop using GTK programs.
The main issue is if you don't like KDE, there's basically no alternate for Qt desktops, LXQt is basically KDE Lite these days.
Everything else is using GTK shitware and should be avoided, unless you go super minimal with a basic window manager (either tiling or floating works).
 
Last edited:
Akerman said:
sic

EDIT: Joborun from the blog you shared earlier seems to align with your goals, unless you already considered it and rejected it.
Click to expand...
My bad for not including it in the list, Joborun is definitely in the running. What irks me about it isn't the philosophy, they're on point in that regard, but the fact that they're the downstream of a downstream with a 2 man active dev team. It is source-based, which is good, but the chain of dependencies leaves me somewhat skeptical. Obarun is one degree up, and has me leaning slightly more in its favor. Also yes, Antix is a little heavy handed with their political autism, it is what it is.

Honestly, at this rate, I am seriously considering trying Open/FreeBSD instead. It should have everything I need, and I have heard very good things about hosting VMs with bhyve or qemu. FreeBSD is getting its 15.0 release this year anyway, so the timing is certainly not bad for a little switcheroo.
 
Akerman said:
Were the anti-systemd conspiratards right all along?
Click to expand...
Always.

Akerman said:
I hadn't heard anything about that distro so I looked it up, and wtf:
View attachment 7496347
(src)
Yeah, something tells me they won't ship XLibre.
By image and branding alone it might be the worst offender of this type of shit I have seen in Linux. Once again I am reminded of "Burgers?"

View attachment 7496760
:story:
Also, what the hell is this old dude wearing?
Click to expand...
Yeah, Antix is the antifa distro.
 
It seems anything that can be daily driven had been infiltrated by freaks. The moment Wayland requires more systemd (you know it will at some point), the principle would override everything else and AntiX will have to embrace XLibre.
 
Last edited:
YoRHa No. 2 Type B said:
Vivaldi in Gentoo has use flags to remove GTK support in favour of Qt, which seems strange to me as its proprietary software only shipped as binaries.
Click to expand...
It is open source to an extent. The tarballs for their Chromium fork get released every major update, but I don't believe it gets updated whenever the minor updates roll around, so there is some degree to which you could recompile Vivaldi.

Also, Vivaldi is arguably the best Chromium based browser on the market that isn't some direct Chromium fork like Ungoogled Chromium or Thorium. So much so that it pains me there isn't an equivalent Firefox fork given how Manifest v2 extensions will inevitably stop working in Vivaldi.
 
Slav Power said:
It is open source to an extent. The tarballs for their Chromium fork get released every major update, but I don't believe it gets updated whenever the minor updates roll around, so there is some degree to which you could recompile Vivaldi.

Also, Vivaldi is arguably the best Chromium based browser on the market that isn't some direct Chromium fork like Ungoogled Chromium or Thorium. So much so that it pains me there isn't an equivalent Firefox fork given how Manifest v2 extensions will inevitably stop working in Vivaldi.
Click to expand...
Vivaldi is "partly open source" because they're afraid they will be outcompeted if they publish their UI features. In reality, doing this only hurts their potential userbase, since many of the people who would want to use something like Vivaldi care about free software, and in fact some distros recently dropped Firefox in favor of a modified version of Brave, because Firefox is spyware now and modifying Brave was the best option. If Vivaldi was FLOSS, that probably be a superior option for these distros. There is a Vivaldi-like Gecko browser called Floorp, you can use that if you like, but Gecko is dying and it will only get worse and worse at rendering the evolving web. The only difference that manifest v3 makes is for adblocking, but Brave and Vivaldi develop their own built-in adblockers that apparently work pretty well, and because they aren't extensions they aren't affected by the limitations of manifest v3, although they don't give you the same power as Ublock. If your concern is that you use old extensions that you don't expect to be updated to manifest v3, try looking for new versions.
 
Betonhaus said:
HDR support doesn't sound too hard to pull off, but how is the multi monitor thing hacky? And how hard would it be to fix,
Click to expand...
Multimonitor support on X11 is usually done by tricking X11 into thinking your monitors are one big screen. Thats why compositors cant handle multiple monitors with different refresh rates and fractional scaling doesn't work. X11 does have multihead support, but that comes with the catch of it essentially being two seperate instances of X11 and applications cant move between them, only the mouse.

There was asyncflipsecondaries that made it so that instead of compositors using the lowest refresh rate it used the highest, fixing the issue of seperate refresh rates, but that comes with the issue of tearing if the monitors are not similar (120hertz & 60hertz = 60hertz tearfree, 144hertz & 60hertz = tearing on 60hertz).

It would require changing the way X11 views monitors, so ig pretty hard.
 
Rust Troony said:
It would require changing the way X11 views monitors, so ig pretty hard.
Click to expand...
I suspect it's not as hard as people want to believe. The problem is that the freedesktop people have been gatekeeping any improvements to XOrg for more than a decade at this point, in order to "encourage" development of wayland, so nobody has actually had the opportunity to make the changes.
 
teriyakiburns said:
I suspect it's not as hard as people want to believe. The problem is that the freedesktop people have been gatekeeping any improvements to XOrg for more than a decade at this point, in order to "encourage" development of wayland, so nobody has actually had the opportunity to make the changes.
Click to expand...
I would like to know the theory behind the change though, as it sounds like the framerate gets set before the buffer is split off into different screens.

Maybe you could have something like each display is it's own x11 instance but have applications belong to one instance but the part that's on the second screen be "mirrored" to it with a sort of screen capture system that will pass mouse clicks back to the main app in its original x11 instance, then jump to the other. That would mean that the app could have v-sync issues on the second screen when it's overlapping but it wouldn't be as severe.
 
teriyakiburns said:
I suspect it's not as hard as people want to believe. The problem is that the freedesktop people have been gatekeeping any improvements to XOrg for more than a decade at this point, in order to "encourage" development of wayland, so nobody has actually had the opportunity to make the changes.
Click to expand...
Might be optimistic, but I am inclined to believe that XLibre will fix a lot of the persistent artificial issues X11 has been dealing with for years in a fraction of that time, especially if developers from Artix and other anti-RHEL communities contribute.
 
Betonhaus said:
Maybe you could have something like each display is it's own x11 instance but have applications belong to one instance but the part that's on the second screen be "mirrored" to it with a sort of screen capture system that will pass mouse clicks back to the main app in its original x11 instance, then jump to the other.
Click to expand...
This is kind of similar to one of the solutions previously employed, before the whole "merge the monitors" thing, and very similar to the solution Apple uses in MacOS (IIRC, anyway). Having windows cross display servers is a very complicated problem to solve, though probably not insurmountable.
 
Ferryman said:
Might be optimistic, but I am inclined to believe that XLibre will fix a lot of the persistent artificial issues X11 has been dealing with for years in a fraction of that time, especially if developers from Artix and other anti-RHEL communities contribute.
Click to expand...
teriyakiburns said:
I suspect it's not as hard as people want to believe. The problem is that the freedesktop people have been gatekeeping any improvements to XOrg for more than a decade at this point, in order to "encourage" development of wayland, so nobody has actually had the opportunity to make the changes.
Click to expand...
I think it will be a slow burn, it is only like 4 developers from what i can see. We will get a huge bugfix that will make Xlibre worth it to change to but it will fizzle out into a slow burn of updates. It would probably take at least a year or two before these issues would be solved, if ever.

Rust Troony said:
There was asyncflipsecondaries that made it so that instead of compositors using the lowest refresh rate it used the highest
Click to expand...
I decided to try this out as i hadn't ever actually touched it. Using xfces' built in compositor gave visual glitches and turning the compositor on and off too fast ended up hard crashing the system lmao. Switched over to picom and it was solved, however even using the "similar refresh rate" my secondary monitor still has screen tearing, and didnt really change much worst when i went to my main monitors highest refresh rate (144hz), main monitor is still buttery smooth without screen tearing, so im staying with it. Good to see it actually works though, this was one of the pain points making me want to switch back to Wayland, now i guess im here permanately.
 
teriyakiburns said:
This is kind of similar to one of the solutions previously employed, before the whole "merge the monitors" thing, and very similar to the solution Apple uses in MacOS (IIRC, anyway). Having windows cross display servers is a very complicated problem to solve, though probably not insurmountable.
Click to expand...
Can an application be transferred to a different display server seamlessly without visible glitching?

What would be the overhead if you had split the display server into two parts where each window gets its own for one part and each display gets its own for the other part?
 
Rust Troony said:
I think it will be a slow burn, it is only like 4 developers from what i can see. We will get a huge bugfix that will make Xlibre worth it to change to but it will fizzle out into a slow burn of updates. It would probably take at least a year or two before these issues would be solved, if ever.
Click to expand...
Considering the sheer volume of (attempted) contributions Enrico added to X11, the burn might be slow, but it will certainly be better than the ditch it now lies in. Even incremental improvement is still categorically better than what amounts to total stagnation.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom