The Linux Thread - The Autist's OS of Choice

  • Twórca wątku Twórca wątku tehpope
  • Data rozpoczęcia Data rozpoczęcia
Wyróżnienie
X11 is so great, nooooo Wayland is better!!!

ENTER:

1782899778599.png
 
Ostatnio edytowane przez moderatora:
Ferryman powiedział(a):
X11 is so great, nooooo Wayland is better!!!

ENTER:

Wyświetl załącznik 9216067
Kliknij, aby rozwinąć...

Been following that project for a long time now. Progress slow and all beyond my pay grade, but fascinating, and seemingly more practical and achievable than so many similar promises of grand unified perfection. Nice to see a new post from earlier this month. Wonder what little tidbit of text in some past poosting got him accused of the dreaded woke.
 
Betonhaus powiedział(a):
I might be wrong, but isn’t any app with the org.freedesktop.*.* nomenclature a flatpak?
Kliknij, aby rozwinąć...
No. If you look in /usr/share/applications/ you can see this naming convention at work. It helps guarantee a unique name scheme using only DNS as a central registry. You'll also see apps with com.github.xxx-app names.

Ferryman powiedział(a):
X11 is so great, nooooo Wayland is better!!!
Kliknij, aby rozwinąć...
I went from awesomewm to i3 to Sway/Wayland. One thing I noted is that problems with XWayland are probably problems in your compositor lib, wlroots or swc. I tried velox (swc) for a time and while it was interesting, I wasn't going to swap over for much the same experience, only more primitive. But I did notice that XWayland seemed less buggy under swc.

Arcan, huh? I wonder if it's an also-ran like Berlin, or is it actually more capable? Network-transparent graphics? Mmm, seems like 9P is a better solution to collect data from a remote host and display it locally, unless you're completely dedicated to ultra-thin clients...?
 
somercet powiedział(a):
No. If you look in /usr/share/applications/ you can see this naming convention at work. It helps guarantee a unique name scheme using only DNS as a central registry. You'll also see apps with com.github.xxx-app names.
Kliknij, aby rozwinąć...
It is called "Reverse Domain Name Notation". It is the norm when namespacing code modules in quite a number of programming languages.
 
Have a niche piece of software (windows) that I want to run and stream reliably 24/7

Shove the windows app into a docker container with xvfb. Have sidecars connecting to the x11 socket for things like ffmpeg, same with pulse audio for shuffling sound around. GPU mounted into ffmpeg sidecar for GPU encoding. Headless windows app streaming reliably with Linux in k8s success.

Wayland could never.
 
ZLUDA, a project trying to become a drop in replacement for CUDA on AMD using ROCM had a new release that brought preliminary support for 32bit physx, allowing AMD gpus to actually run older physx titles without abysmal performance. Sadly their funding dried up and so now its more of a hobby project. With them going to primarily focusing on physx, hopefully Valve steps in and contracts them to continue working on gaming focused CUDA support, since a lot of older games used physx and it was a genuinely a huge visually altering feature, moreso than raytracing.
 
Ostatnio edytowane:
Swapped from PopOS with X11 to CachyOS with Wayland and it's been like 99% positive. Not sure if it was X11 or Plasma KDE's interface with X11 but it really, really hated when I would turn off my primary monitor and had about a 50% chance to reset to default background. Had to do it frequently because it's an OLED monitor and prone to burn in which it counters by nagging you to do a 7ish minute reset cycle every 4 hours. This set up gives me a system notification when the monitor is fully disconnected (i.e. done) and moves the windows back to where they were when I turn it back on.
 
somercet powiedział(a):
I went from awesomewm to i3 to Sway/Wayland. One thing I noted is that problems with XWayland are probably problems in your compositor lib, wlroots or swc. I tried velox (swc) for a time and while it was interesting, I wasn't going to swap over for much the same experience, only more primitive. But I did notice that XWayland seemed less buggy under swc.
Kliknij, aby rozwinąć...
I'm having trouble understanding what you are talking about. Can you say this again but in fortnite Linux Mint terms?
 
https://guix.gnu.org/en/blog/2026/guix-substitute-pull-vulnerabilities/ powiedział(a):
Some additional hardening was also done, so that substitutes are restored inside a temporary directory and only moved to their final store item path once the hash is verified. This still restores them before verifying the hash, so it wouldn't have prevented (1)
Kliknij, aby rozwinąć...
This sounds retarded. Is there a good reason it can't verify first, and if so why wouldn't he explain this?
 
I just discovered that this retard has gotten DXVK_FRAME_RATE removed simply because he didn't like it:
"Users should use mangohud or other external solutions." he says as if all other methods don't introduce extreme input lag or horrible frame times.

I kept using that command until it just stopped working randomly. I even uninstalled a game, because vsync/mangohud were so fucking cancer to play with. Thankfully I found out that this works instead:
"DXVK_CONFIG="dxgi.maxFrameRate = 60; d3d9.maxFrameRate = 60" %command%"

But yeah, let's remove a short and straightforward variable which can be easily remembered and make people keep a text file with this long command instead. Great idea, thanks tranny!
 
Ostatnio edytowane:
⚞⛇⚟ powiedział(a):
I'm having trouble understanding what you are talking about. Can you say this again but in fortnite Linux Mint terms?
Kliknij, aby rozwinąć...
Never used Mint.

XWayland is the Wayland program that acts like an X Window System (X11) driver, translating X11 graphics to Wayland, the X11 replacement.

awesomewm, i3: X11 tiling window managers.
Sway: a Wayland compositor that clones i3's look and feel, but Wayland native.

wlroots, swc: two different Wayland compositor libraries. wlroots is about 1.1MB, wld/swc are about 288KB.
 
somercet powiedział(a):
XWayland is the Wayland program that acts like an X Window System (X11) driver, translating X11 graphics to Wayland, the X11 replacement
Kliknij, aby rozwinąć...
It’s not really a replacement as it’s basically running an x11 server on Wayland entirely. I think there was a project called way back to fully replace it but that project stalled and is currently yet another wrapper around x11
 
I wish there was a way to enable full font hinting in a web browser. I guess that feature is reserved for Windows.
 
I have been having a go with Alpine Linux on an old Chromebook. Honestly, quite a fun experience. Points of difference I came across from Standard Linux (Devuan):
  1. The setup-alpine install script is generally good, although it will do things like write your wpa_supplicant configuration for your initial network twice into the config file (which doesn't cause any problems) if you Ctrl-C halfway through. If you DO do that, it's probably better to reformat the target drive and start from the start. I also noticed that while apparently alpine has done the awful usrmerge change, the install scripts didn't seem to set things up that way. Which is interesting to say the least. So after getting things nicely set up I just YOLO-d it and the script doesn't seem to have broken everything.
  2. OpenRC works just fine. More normal and rational to deal with than the pedo Poettring's deranged nonsense, boots at least as fast as standard sysvinit.
  3. The initial install and the officially supported packages aren't really sufficient to use a GUI desktop, but the community repo expands that nicely. Those packages that are included are nicely up to date. Is it rational to use a distro that packages the man pages and shell completions separately from applications on a desktop (rather than a container where that actually makes a difference)- not really- but it's interesting.
  4. It's interesting to use Busybox ash, at least for a while, instead of bash. There certainly are a lot of things that are easy to get used to having in Bash, like extended glob matches and pushd/popd, that aren't standard POSIX shell features. Of course, the ultimate shell- pwsh- is available from the community repo. I fairly quickly gave up on actually using ash for user tasks and switched to fish.
  5. I haven't run into many issues with building software that isn't packaged due to the use of musl. There is one thing I wanted to try but have been running into problems with- it's a few years old and may have python incompatibilities as much as anything else, I'm going to try building it in a debian oldstable chroot and then a debian stable chroot and see if it's even possible to use it there- but basically, most normal software works.
  6. I chose to try out LXDE, which while very nice as a basic panel environment is lacking in support applications (besides the excellent pcmanfm-qt port of the original GTK utility). Any thoughts of keeping things as 'light footprint' as possible very rapidly went out the window as I first dismayed of getting a good barebones QT text editor from the APK repos, and installed kate (and hundreds of megs of other KDE crap as a result), and then decided fuck it, I'd just build featherpad from source (and installed a gig of QT dev libraries in the process). If I had just used a regular distro like Devuan with a wider set of binary packages, I would have less crap installed, but hey, this thing has a huge 32gb flash chip, and a SD card slot for things that don't need to be remotely safe from data loss, so it shouldn't be a problem.
  7. If you are using apk to install or remove things (add/del) it does not ask before doing more than you asked for. In the case of removing things, you probably want to add that '-i' flag on..
  8. There was one application that I did NOT want to build from source (I understand Electron doesn't actually work with MUSL), FreeTube. This taught me that there is no excuse for having an incompatible AppImage. Some very cool guys made tools that make it relatively straightforward to detect the use of and deploy all the relevant libraries as part of the AppImage, and a helpful chap made a FreeTube AppImage that, despite being compiled against glibc and on a completely different system, Just Works. It's about 30% larger than the regular, less compatible AppImage, but if you're building something that you know will be inferior to anything a distro could package, just suck it up and make the slightly fatter fat version the standard, or offer both.
Tap Water Enjoyer powiedział(a):
I just discovered that this retard has gotten DXVK_FRAME_RATE removed simply because he didn't like it:
"Users should use mangohud or other external solutions." he says as if all other methods don't introduce extreme input lag or horrible frame times.
Kliknij, aby rozwinąć...
Reading through that issue, there appear to be a couple of forks maintained by angry men like
which retain that environment variable.
 
all bungie had to do was allow proton and then theyd all be working instead of laid off on 4th of july
i wrote to sony. i said sony u gotta kill bungie they're not supporting the linux community.
and the ceo responded to me, he said you're absolutely right.
the linux relations with sony, they're the best they've ever been.
the talks, they were wonderful, everybody says so.
and then he laid off 300 people.
 
Wyróżnienie
Musisz się zalogować lub zarejestrować, aby odpowiedzieć.
Wstecz
Top Na dole