• 33 Posts
  • 17 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle






  • You can check if you are using Xorg or Wayland in the Settings -> System -> About -> System Details page. If you’re using Wayland, you’re all good, nothing changes. If you’re using Xorg, you may notice some changes. If you’re using NVIDIA on Ubuntu 24.04, you’ll be on Xorg by default. If you’re using a later version or AMD/Intel, you’ll be on Wayland be default.

    To keep it short, X11 was the old protocol for creating and managing windows. Xorg implemented this protocol. But both the protocol and implementation have many shortcomings that are difficult to address for a multitude of reasons (breaking compatibility, poor code base, a ton of work, etc).

    Rather than putting lipstick on a pig, a new protocol, called Wayland, was created. It was designed for modern needs and tries to avoid the pitfalls that X11, Windows, and MacOS have. It doesn’t just copy what those three did, it’s more opinionated, so some people love it a lot (like me) or hate it a lot because it changes the way things have to be done and simply does not implement some functionality, either purposefully or because the work hasn’t been done yet.

















  • Leaflet@lemmy.worldOPtoLinux@lemmy.mlThe Future of Flatpak | Sebastian Wick @ LAS 2025
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Don’t believe so, best that’s currently available is skimming through the video to look at the slides.

    Here’s my short summary of the presentation, I tried to denote what’s being worked on (open PR), what’s kinda being done (WIP), and things stuff they’d like to be done in the future (wishlist). May be somewhat wrong.

    • Flatpak is stagnant
    • Red Hat is working on a better way to preinstall flatpak apps (open PR)
    • Flatpak should is slowly moving towards OCI and away from ostree (more tooling available, don’t need to maintain their own tools)
    • Better permission handling that is more backwards compatible (open PR)
    • Should directly use Pipewire instead of Pulseaudio (WIP)
    • Allow user namespaces in flatpak sandbox (WIP)
    • Move dbus proxying into dbus brokers (wishlist)
    • Improve network sandboxing (wishlist)
    • Improve drivers handling, currently drivers need to be built for each runtime, could cause issues if using EOL app on new hardware (wishlist)
    • Work on portals directly improves flatpak






  • This is overly complicated. Just install Java then run

    flatpak --user override --env="FLATPAK_ENABLE_SDK_EXT=openjdk" com.vscodium.codium
    

    Note this works for all other SDKs too. It works especially well for programming languages like Rust that have their own package manager.

    Doesn’t work so well for languages like C/C++ where you use your distro package manager to install dependencies. In those cases it’s easier to install VSCodium inside a container where you do have access to a distro package manager.