• 0 Posts
  • 228 Comments
Joined 2 years ago
cake
Cake day: September 9th, 2023

help-circle

  • Idk if that’ll make you happy. The different POSIXy shells have so many subtle differences and footguns that I personally feel best

    • using nushell as a daily driver, as it’s sane and makes sense and errors out when it should
    • using bash when forced to interact with things that are written in bash (I don’t know anything written in fish or ZSH)
    • using Python or Rust or so for scripts living in projects that are written in that language

    I can’t be bothered to look up the weird arcane sigils that make bash not shit itself when e.g. using arrays as command args or so, so I will author only the most pedestrian bash scripts where pipes are already a bit much.






  • flying_sheep@lemmy.mltolinuxmemes@lemmy.worldFeature parity or get out
    link
    fedilink
    arrow-up
    4
    arrow-down
    5
    ·
    edit-2
    2 days ago

    Plasma devs are currently focusing on input devices. Ideal time to offer them to help test your device and get amazing support out of it.

    Or you could sit on your ass and do nothing, which is essentially gambling that they’ll happen to support it (or your next device) when you’re forced to switch at some point in the future.





  • The issue is that in the political landscape, that word has shifted away from its social meaning. “Conservatives” in the US and parts of Europe are actually reactionaries, i.e. people pushing back against the status quo wanting to “return” to some idealized past that never existed like that.

    So using the word “conservative” in its original sense might not be understood by people.


  • People who just complain and stay in some deprecated tech (instead of reporting bugs and working with the new way) will have a rude awakening when it’s just no longer supported.

    I’m not saying everyone should be a early adopter, but this timeline was more than forgiving. People who did nothing but keep using the X11 GNOME session might run into Wayland session bugs now that they could have reported years ago.



  • Almost everyone uses it. We just never make posts about “our configuration works effortlessly, give us attention”

    Only people with a bone to chew and shit to stir feel the need to post such things. Back in the day it was people who felt superior for debugging their steaming pile of init shell spaghetti, now it’s people who just can’t live without diving into X11 configuration files.



  • flying_sheep@lemmy.mltolinuxmemes@lemmy.worldFeature parity or get out
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    2 days ago

    Possibly, yet against their best efforts, their shit works better now, see the end of this comment. But first:

    I’ve ranted about this before, but Zoom is bone-chillingly badly written software. It’s also the only piece of software that I’ve never seen the code of, but will make comments about code quality and development practice with 100% certainty.

    Zoom has broken for me in so many many completely insane and creative ways that the only explanation is that they have nobody keeping things in check and just an army of interns hacking away at things half-assedly until they “work”.

    If there are 3 nice and standard ways to do things that can be easily googled, Zoom does a given thing in 2 more ass-backwards ways that make no sense and are fragile as fuck. E.g. they did screen sharing using GNOME’s screenshot API, at a time when every tutorial told you to use the dedicated cross-DE screencast API. When called out, they switched to a different GNOME API.

    I think at this point they finally fixed it by actually using the API people told them to use years earlier, but who knows what other inane mistakes are still there to prevent things from working.