• 0 Posts
  • 108 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle














  • I voted in WA State. Not that my vote is really going to sway things on a federal level. I didn’t have one federal-level vote on my ballot this year. That said I saw a ton of young minorities going up against a bunch of white old people for local positions. While I still voted for who I thought would do a great job, that person was usually the younger minority folks over the white old folks.

    One thing I did vote for is https://www.tacoma4all.org/initiative01 which a bunch of the against arguments boiled down to “the landlords will sell and tear down the buildings and we’ll all be homeless if we enact a law that says landlords need to be responsible people!” It was really shocking to see such a weak argument in the voter’s pamphlet. Check it out here: https://i.imgur.com/HH6HNRk.png



  • MJBrune@beehaw.orgtoProgrammer Humor@lemmy.mlNo rest for the virtuous
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    8 months ago

    Feels like this is entirely just blaming the driver which isn’t the cause of 99% of Wayland issues. I know obs, another open sourced project, has caused a lot of issues with Wayland. It’s not driver related.

    As for xorg not being a problem, in the same regard why even bother with a display server at all. The point isn’t that’s it’s bad it’s that there are better ways of doing things.


  • Frankly, the only reason I care is the end-user drawbacks that Wayland seems to have. There are tons of bugs and issues. On top of that, I use Nvidia proprietary drivers which also causes more drawbacks and issues. It feels like at this point a third option needs to be made available. It’s been 15 years since Wayland was released and it still has a large amount of bugs and isn’t ready for most distros to adopt it.

    I’ve not touched the Wayland or Xorg code, and I’ve not looked into why Wayland is so broken, but the major issue I see is that it’s taken them 15 years to still have a buggy display server. Display servers need to be the most stable you could possibly make them. They need to be made with desktop and fullscreen exclusive apps in mind. They need to be made modern and extendable while also ensuring those extensions aren’t able to crash the entire display server. They need to be robust and that’s just not what you are going to find with Wayland, or Xorg, or perhaps even Linux in general.


  • MJBrune@beehaw.orgtoProgrammer Humor@lemmy.mlNo rest for the virtuous
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    8 months ago

    Honestly, the biggest issue for me is that it’s someone else’s code that is usually not following industry standards of maintaining something. Usually, it goes off in some open-source standard way of doing something. If more projects were better at standardizing toward the known industry standards then it’d be far easier for me to jump into.


  • Yeah, I mean if it’s a static website unless it’s using a generator, the source is accessible by just visiting the website. So having it public shouldn’t matter too much, right? Even if it’s using a generator, it’s not like what you are writing is secret. That said I use GitLab and Hugo on a private repo. I have no reason to make it public and all the highly experienced web developers told me it simply doesn’t need to be public so why make it public?