#nobridge

  • 3 Posts
  • 91 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle





  • The simple solution is to use another cloud, such as proton drive mentioned below.

    Another more technical solution is to setup a vpn at home and use vpn + smb to share files with your phones, this one fails if your computer isn’t always online at home or if your internet provider runs CGNAT.

    Your computer could be replaced with a selfhosted solution as nextcloud running on separate hardware, but now we’re firmly in selfhosting land.

    The VPN home could be replaced with a VPS that both your home network and mobile devices connect to as a CGNAT workaround.

    The KISS (Keep it simple, stupid) principle says that getting another cloud storage is the way to go. If you truly wanna own your cloud then a trip to selfhost land it is.

















  • anamethatisnt@lemmy.worldtoLinux@lemmy.mlI dislike wayland
    link
    fedilink
    arrow-up
    12
    ·
    edit-2
    4 months ago

    So the blog has these points listed:

    • Wayland’s client API is gimped. Understandably, any piece of software has limits on its scope. I’m not criticizing that, but the limit on the scope of the Wayland ecosystem is way too small.

    • Wayland’s lack of feature parity with Xorg cripples it. This brief section is now outdated and much to my surprise, the tearing protocol was actually merged thanks to Valve pushing hard for it. The text is left here for historical reasons.

    • Wayland’s render loop design is ridiculous. If you build a client from ground up specifically with Wayland in mind, sure this is easy. But many applications are cross platform and internally driven.
      There’s nothing wrong with an application managing how it should render internally. It’s a natural choice for any program that operates in a cross-platform manner.

    • Wayland’s Mesa implementations are leagues behind Xorg’s. Both the EGL and Vulkan Mesa implementations are, quite frankly, bugged and lacking when compared to their Xorg DRI3 counterparts.
      In EGL’s case, the spec isn’t violated, but swap intervals greater than 1 are completely broken.
      Vulkan is more dire. The indefinite blocking behavior outright violates the Vulkan spec. Giving a timeout in AcquireImage does nothing in practice because the blocking is done in PresentQueue. Only two presentation modes on Wayland actually work: fifo (well this works by breaking the spec) and mailbox.

    • Wayland itself has bad core decisions. The big and obvious mistake to point out is fractional scaling. Update: The fractional scale protocol has been merged, and it’s definitely a step forward.

    • Was it really worth it? We were told all along that Xorg is so bad and terrible that it needed to be started from scratch but at this point people need to be looking in the mirror and asking questions. If that 14 years of effort was instead focused onto solely improving Xorg, what would the result be? Surely, much more tangible results would have been gained at the end of the day.

      I’m not qualified to discuss render loop design or mesa implementations, but it seems 2/5 points has been rendered obsolete in the last 18 months. Progress! :)