us.zoom.Zoom VS nix-gui

For example, let's say we want a separate instance of Zoom (Zoom on Flathub) to run along the default one.

It seems to divert the discussion to something that doesn't make too much sense. X and Wayland are two different things by design, this probonopd sounds extraordinarily salty that moving an application under a new server breaks some things, making some applications entirely useless, but I say, that is to be expected. Saying that Wayland breaks stuff by design, as if that was their only objective is just petty, of course it's a pity that those devs have thrown in the towel, but let's not pretend like theirs were the only options, e.g. screen recording works perfectly fine with OBS, at least it has done so on my machines with AMD/Intel GPUs; Jitsi works now; Zoom screensharing being GNOME only is Zoom devs being dicks that can't be arsed to support standards, the community came in to work around it and also I don't know how they could bring up a proprietary application that has not made the Flatpak package themselves as an example, the whole thing is a community effort there apparently; etc. etc. (I'm not going to debunk all the others that are invalid, the internet is there for everyone)

Can you be specific about the problems with X11? I've been using X11 for decades and it's been ROCK SOLID. And that is exactly what you want from something so essential. Wayland feels like an expensive boondogle, frankly. Wayland breaks everything and only provides 20% the functionality that X11. It also forces application and DE developers to implement special tools and solutions for wayland which have always been provided as a common interface by X11, like screenshots/ recording and screen sharing, e.g. https://github.com/flathub/us.zoom.Zoom/issues/22

For college and therapy, I've had to use Zoom. I've been using the zoom flatpak, as I try and use flatpak for any proprietary software. That being said, it is not officially supported (by zoom), and also doesn't listen to Pop!_OS's tiling window manager. Certainly, I'm not the only one who has questioned which client to use, but I'm curious what y'all think. I like flatpak because I can trust that, worst case scenario, the proprietary software (read: Spyware) only has access to a limited amount of my system. But it'd also be nice to, ya know, use the tiling feature.

I've gathered a coredump and a stack trace, which might be useful.

You can get it as a flatpak too which should (presumably) take care of any dependencies automatically. :)

Here you go: https://flathub.org/apps/details/us.zoom.Zoom

Check this out https://github.com/flathub/us.zoom.Zoom/blob/master/zoom.sh

Link to the github issue for the flatpak

This is pretty close https://github.com/nix-gui/nix-gui

Nix based aiming at beginners. If it combines/works with https://github.com/nix-gui/nix-gui, then an amazing distro may be created. It would be user friendly, but also extremely powerful, allowing basically everything to be configured via the gui. Both softwares are alpha state, but I am excited to see what they bring.

Maybe https://github.com/nix-gui/nix-gui? I dunno if it can do userspace config though.

Would it make sense to integrate something like nix gui into this?

I remember when I first started using NixOS, as a confused beginner I tried to find a graphical application to manage and edit my configuration. I stumbled upon Nix-Gui, however, I didn’t really like the look, it crashed a fair amount, and I never really figured out how to use it. That said, their idea and all of the hard work they put into their project inspired me to make a similar application that focuses more on simplicity and ease of use.

I was wondering if you are aware of https://github.com/nix-gui/nix-gui and how your tool compares to it

There is also a GUI in development, hopefully it will help casual users in the future.

There's https://github.com/nix-gui/nix-gui for a gui like experience.

Configuration language usage: Probably a major win for programmers, but a major negative for non-programmers. However, nix-gui has shown that there's potential for gui-based nixos configuration. And this might one day be extended to use as part of the graphical installer. https://discourse.nixos.org/t/why-is-there-no-installer-for-nixos/16644/21. Since nix can be serialized and deserialized to json, there's actually a fair amount of interoperability able to be done to manipulate nix configuration using existing libraries.