frankfurt_schoolgirl [she/her]

  • 0 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2022

help-circle




  • frankfurt_schoolgirl [she/her]@hexbear.nettoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    10 months ago

    I’ve been using Wayland for 5 years. There were a few bugs in the beggining, but now it works great. These threads are such a waste of time.

    I have over 100 confirms X11 developments

    That’s great dude. Why don’t you go maintain it then, apparently nobody else wants to: https://www.phoronix.com/news/RHEL10-Removing-X.Org

    Wayland took too long

    Look up how long btrfs has been in development, or at audio subsystem churn. These things take time, because it’s mostly volunteers working on them.

    Systemic complexity has doubled in the last two years

    What does this even mean?

    Mir was better

    It turns out the Canonical dumping random stuff over the wall is not the same as creating a legitimate open source community around a project.

    Unfixable amount of race conditions

    As if there’s never been a synchronization bug in X… But also System76 and others are writing Wayland compositors on Rust anyway.








  • rootless containers

    Are you managing dotfiles in rootless containers? IMO you shouldn’t install nix in a container. If you want to customize your container, run nix outside of the container and tell home manager to apply itself to the container’s file system (home-manager build will put the result into a result directory, which you can copy). Or, you could just mount your host ~/.config on the container maybe.

    Ansible

    Ansible is a big project, but at the end of the day it’s just a Python package. If you already have Python installed, it’s not really adding that much.

    Also obligatory advice for anyone new to Nix: use flakes. Flakes are good and right. It sucks that Nix is in a confusing transition process to flakes, but if you just adopt them completely from the start it makes everything easier. Your home manager config can live in a single flake somewhere that you find convenient, and you can apply it from there.


  • I would use nix home manager for this. Home manager has basically three separate layers. The ability to install nix packages for a user, the ability to generate config files, and special modules that combine these things things as an easy way to manage popular programs (like vim or tmux or something). You could probably just stick to the config file generation (see the xdg.configFile module).

    A big downside is that you will have to install the basic nix package manager to get home manager working. You don’t have to use it to install all of your software, but it will still need a /nix and a system daemon for home manager as far as I know.

    nix doesn’t play well with container environments

    I’m not sure what this means. What specific things are you trying to do with containers and nix?

    If you don’t want to install a bug, complicated piece of software just to manage dotfiles, maybe you could consider Ansible? I know some sysadmin types who keep their local machine configs in Ansible. It has some nice bonus features, like deployment over ssh (nix can do this too btw).


  • I totally agree. The real problem for Linux gaming tho is that games are almost always distributed as compuled binaries, but Linux is built around open source. It you had a model where you paid for the source code of a game, and then it got compiled for your machine right when you downloaded, Linux gaming would probably work great. You’d have better fps too. (I actually really like this idea, somebody like GOG should make a client that does this).


  • As a big Linux fan, it makes me said that Wine needs to exist. But, maybe it’s not such a bad thing. Linux is just a kernel, with no associated libraries for app developers. App devs don’t want to manually write system calls, so it’s always been the case thar they lick and choose which set of libraries to target for their Linux apps. A popular low level choice is the GNU standard C library, and a popular high level choice is the GTK/GDK/Gnome stack. But these aren’t the only choices. I mean you can use the MUSL standard C library if you want. You can choose between OpenGL, Vulkan, and WGPU for graphics already.

    I see Wine and Proton as just being another set of standard apis to target. Maybe they don’t have the best design, but is traditional Unix really the best design either? Now the Valve and company are supporting Wine, it’s one of the Linux targets with the most actual developers. And of course it has a huge advantage over the glibc + Vulkan stuff: it retains binary compatibility forever.



  • you’ll need a special Xorg implementation

    Ok it’s true that op would need XWayland for some things, but that will be installed alongside the rest of the Wayland packages, and will run seamlessly.

    Most applications are specific to your Wayland implementation

    This isn’t true. Some applications will use features that aren’t available in all Wayland compositors, but they are rare. The main offenders are apps that interact with other apps, apps that take screenshots or record, or apps that draw outside of a window (like docks).


  • This is not possible. A socks proxy forwards tcp connections over another TCP connection. A wireguard vpn sends encrypted generic IP packets over udp. A socks proxy can’t understand the types of things wireguard sends.

    However, you could just install wireguard on both your vps and your phone, and you probably wouldn’t even need the proxy. If your VPS is hosted by a big public cloud provider, be aware that many sites restrict incoming traffic from known up ranges because public cloud vms often used by spammers.