• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle





  • Mpd has always served me well. I use ncccmmmmppp (however its spelled) to manage playlists and such. For album artwork I run sxiv pointed at file in /tmp/. I forget how that part works, actually. I have a grid layout on a second monitor, so I just square up the mpd client and sxiv. Doesn’t look too bad.

    Semi-related, but as a project I ripped out the pressure/impact pads of an old midi keyboard for use as prev/(pause/unpause)/next buttons, so if the song sucks I can literally punch my desk to skip it.


  • Wayland has mostly positive user reviews because it presents nicely to the user (VRR, scaling, etc.) On the developer front it seems there’s a lot of struggle over things that were solved in X11 but for some reason require a lot of debate in Wayland.

    • There’s still no way to universally configure monitors and input devices, so the startup cost to checking out a new “WM” (compositor in Wayland terms) is non-zero - you have to reconfigure everything from the ground up, and for anyone with complex input systems (see: accessibility devices) this will take a lot of time because each compositor insists on using a different format for configuring these things.
    • Each compositor is tasked with coming up with solutions for all parts of the user experience (hence the last point) and thus anyone who wants to experiment with making their own WM now has to worry about a billion things that wouldn’t have had to deal with in X11. Yeah, there’s libraries for dealing with that stuff, but it’s not as simple as it was and lot of innovative WMs won’t ever be able to make the jump.

    These are the two biggest issues I can see that are entirely chalked up to its design. Technical issues (like the “load balancer” thing that keeps Firefox from crashing on Wayland) will be solved in time. However, the above points are unlikely to ever be addressed. Should they be? I don’t know.



  • Every major update has broken something or fundamentally changed my workflow to such a degree that I no longer feel I understand the program. I currently use it in a semi-automated setup and I’ll likely have my package manager ignore its upgrades in the future barring total breakage of the package. Note: I’m not saying the program is bad, it’s just not something I’m interested in constantly tweaking/relearning if a future update is just going to break it.

    I just learned about Ansel, which is a fork by someone who did a ton of work for DT but was ultimately too opinionated and got the boot. Apparently it’s way more streamlined and easier to work with. YMMV.

    I’ve also heard about vkdt, which is very early, but still something to look at.





  • 0x0@social.rocketsfall.nettoLinux@lemmy.mlRicing Linux
    link
    fedilink
    arrow-up
    12
    arrow-down
    3
    ·
    1 year ago

    Horribly offensive term. Webster’s Dictionary defines ricing as a tiling window manger with 64px gaps, minimalist Naruto/anime background, useless bouncing bar EQ meter, entire window dedicated to song lyrics, obnoxious monospace fonts, nonsensical colors, task bar showing time/date/IP+MAC address/GPS coords/moon phase/crop yield/barometric pressure, and a Vim buffer with Rust’s “hello world” tutorial.



  • It’s good! I don’t think I felt any jump in performance from X/i3 -> Sway, though, but have definitely seen people reporting that.

    It’s taken a while to get everything set up how I like but multiple games behave well here and not on X

    In my experience most games still run under XWayland. It’s possible some aspect of your X11/herbstluftwm config was causing your issues in that regard.


  • If linking to a Wiki entry counts as toxic then I don’t know what to tell you. Users need to hear that their problems aren’t unique and aren’t worth anyone taking time out of their day to handcraft a response to. This isn’t Ubuntu - you are expected to be able to DIY, and if you constantly need someone to hold your hand through the process then you need to uninstall and start over elsewhere until you understand why Arch exists. It’s like declaring you’re going to build a shed to keep your mower in, but you call your contractor buddy every five minutes asking where to drive the nails and place the studs. Your time is best spent driving to the hardware store and buying the shed outright.

    If someone is contemplating installing Arch, they need to be asked why. If they can’t explain it or give a poor answer (“I saw a video” etc,) direct them somewhere else.





  • I remember threads like this from back when Valve was pushing Steam Machines. Won’t name names, but there were very successful developers throwing tantrums once the bug reports started to flood in. Many weren’t prepared to actually provide support and spent years regretting it (according to postmortems.) I managed to get a refund on one game after the developer’s Twitter rant went completely off the rails re: Linux being unfit for desktop. Weird that they were 100% fine with Linux when it meant getting my $15, $20, or $30. Makes you think!