Keyoxide: aspe:keyoxide.org:KI5WYVI3WGWSIGMOKOOOGF4JAE (think PGP key but modern and easier to use)

  • 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle


  • wayland is the norm at this point. The distros still on X11 are mostly the slow moving ones, but I would say we are on the trailing end of adoption now overall.

    Wayland is still lacking features, and due to its newness also lacking documentation and tools available for X11.
    But those are looking like more of a specialty application for X11. The main painpoints are gone.

    The hardware (gpu) situation is fine to my knowledge, drivers have caught up. 10+ year old Nvidia cards (like a gtx 780) may need nouveau, but not sure if even that is still the case.
    Some workflow stuff is just now appearing (like restoring the window positions when a program restarts) or still missing (like some custom input scripting functionality), this also impacts accessibility.
    As an example I used to have a script that would input ctrl+pgup/pgdn into the window under my cursor without changing focus, so I could change pages the same way I can scroll in unfocused windows. That was done with some x tools for setting focus and sending keyinputs. It’s possible to input keys with root permission under wayland, but changing focus from a script is not possible to my knowledge.

    This is all important stuff, but something most people won’t run into, and many more (like me) will accept as a tradeoff for the many advantages of wayland. Doubtless the protocol side will eventually implement apis for all of those missing features, and the tools making use of them will become widely known same as X11 used to be.




  • Hey, there is an entire wayland bad x11 good article hidden in the last 4/5ths of the article!

    Anyway, the article seems to argue that “toxic elements within Xorg projects, moles from BigTech, are boycotting any substantial work on Xorg”.
    It seems to me that now that wayland has become the clear focus of development, most devs sinply want X11 to remain as a legacy element, not causing unnecessary issues elsewhere, just remaining on lts.
    The train has sailed, wayland is the norm and everyone is working on implementing the last leftovers the article is parading in its weird latter half, rather than through much greater efforts achieving worse results in patching up X11.
    They should have forked X 10 years ago, when people were still interested in improving it.

    It being left behind is a logical and fully adequate explanation, arguing eee makes little sense when wayland is clearly a simpler protocol. If you wanted to harm linux or foss, and your plan was the transition to wayland and freezing of X11 development, I would call you stupid.

    I don’t see why this fork, and this article, have to get conspiritorial about something this easily explained.

    Now that we have the conspiracy crap addressed: wayland defense time

    The Reg FOSS desk is nearing 60, […] He doesn’t care about […] high and variable refresh rates, tear-free video,

    My fancy new monitor I got in '22 doesn’t work on X11. I’d have to replace my other monitors with matching new ones for a few grand, or keep watching videos and all else at 15fps, getting a headache. If you wanna keep your crt, why not keep an ancient X11, why this fork?
    X11 doesn’t support normal modern hardware, my monitor wasn’t even special, it’s just higher fps than my other monitors and 4k.

    Wayland does not currently allow controlling window position. This means that when you open KiCad, it cannot remember where you last placed your windows.

    The window pos remembering api (name made up by me, I forgot the real one) has been finalized, and will be in this or the next KDE version, etc… The wayland people are fixing the criticism faster than the critics can shorten their list of remaining issues.

    .

    uhhhh… ok that’s all the wayland criticism, 'cause surprise, the last 2/5ths of the article are actually a rant about … gnome? I think?
    Something about no more shortcut support or how removing title bars is bad and the gnome disk manager has bad ui.
    Idk my shortcuts are better than ever and my title bars were still there last time I checked.
    But maybe this “big no-accessibility” is why absolutely no tiling dwms have ever been seen for wayland ever. If you switch to wayland you will have to tile by mouse exclusively, you heard it here first!



  • He asks ChatGPT to help him develop work that would be difficult for students to complete by simply feeding it into a large language model.

    *insert picard facepalm here*

    That, while not as bad as what I expected from the summary (i.e. AI detection tools etc.), is still hypocritical.
    This is the exact mindless use of AI yielding subpar results anyone can beat with a bit of practice.

    LLMs are not good at introspection, if you ask them what they struggle with they will go off of their datasets, focussed on the time before chatGPT, and summarise with the typical AI quality and deep understanding of the applicability of the known limitations to your text.

    And all that when the actually correct answer is right there: ask the AI for solutions and learn what breaks it.
    But that would take at least a few minutes of time, maybe even hours on the first attempts. Ain’t nobody got time for that, why learn useful skills for the future when you can just vibe out your ai-proofing?