sorted by: new top controversial old
[-] Espi@lemmy.world 1 points 10 months ago* (last edited 10 months ago)

Yeah with "lockable mode" I mean locking by default instead of requiring every program to specifically call for locking.

It would probably break lots of software, but only using such mode for the users home (or maybe even specific Downloads/documents/desktop/etc folders within the home directory) could reduce the impact.

[Edit] wait I think there is whole fs locking mode on mounting, with the "mand" option, going to test it.

[-] Espi@lemmy.world 1 points 11 months ago

I think files being locked is really intuitive, which greatly helps new users. Allowing files to be modified or deleted while they are open makes it really easy to shoot yourself in the foot. For example in the video of Linus switching to Linux he was uncompressing a file and tried to open it while it was still uncompressing, which failed since the file wasn't complete. He didn't understand why the file wasnt uncompressing correctly. That can't happen on Windows, since the file being uncompressed would be locked.

I think there should be a 'lockable mode', and for distributions oriented to new users the home directory should be mounted like that.

[-] Espi@lemmy.world 4 points 11 months ago

No, silverblue does all the work before you restart the computer, and the actual work doesn't involve replacing the OS itself but basically downloading some files and just checking a different git branch when booting.

[-] Espi@lemmy.world 76 points 11 months ago

This is a byproduct of one of the largest and more ignored differences between windows and linux. The fact that Linux let's you modify files while they are open whereas windows doesn't.

This means that you can update a linux system by just replacing the files with the new ones while it runs. On the other side, Windows can't modify its own files while it runs, so instead it has a second entire OS to update itself, and requires a reboot to unload all the files and boot from the updater without locking windows files.

[-] Espi@lemmy.world 1 points 11 months ago

I downvoted because I'm a hater /s

[-] Espi@lemmy.world 13 points 11 months ago

Local cat goes :3

[-] Espi@lemmy.world 5 points 11 months ago

With python and virtualenv you can also keep the entire source of your libraries in your project.

[-] Espi@lemmy.world 3 points 11 months ago

Is RCS encrypted? I still prefer signal above everything else. Whatsapp seems to be passable privacy wise, but it's Facebook so I don't trust it one bit.

One way or another, Whatsapp is the standard around the world and it for sure beats SMS.

[-] Espi@lemmy.world 9 points 11 months ago

I cant believe it, someone who actually knows what they are speaking about?? in my imitation Reddit forum????

Let's not forget that Britain also ensured the rights of Palestinians in that same declaration, I would like to see them act on that one.

[-] Espi@lemmy.world 5 points 11 months ago

While I think firewalls are overrated, they are also dead easy to set up, and the best kind of defense is defense in depth.

[-] Espi@lemmy.world 8 points 11 months ago

It works, nowhere near as good as AMD but it works.

[-] Espi@lemmy.world 5 points 11 months ago

I love Fedora! but sadly I have been burned twice by Red Hat already. I refuse to be burned a third time so I'm moving my servers over to Debian. I like to use the same ecosystem on all my computers, so I also moved my desktop and laptop over to Debian.

I tried OpenSUSE a few times, but I disliked YaST, disliked the unclear future of Leap and disliked the unclear future of ALP. I thought I would love Aeon (I used Silverblue when I used Fedora) but I didn't like being unable to compare my system against a "base" one. So for the time, at least until the situation over SUSE clears up, I'm going to stick with Debian.

Anyways, once GNOME 45 hits Debian Testing I think I'm going to move over to that, I would prefer to use Stable (which I use on my laptop and job) but I really want a recent GNOME for my Nvidia GPU. I have a bunch of BTRFS snapshots ready to go back to stable at any moment if anything happens, so I'm not too worried.

80
submitted 11 months ago by Espi@lemmy.world to c/linux@lemmy.ml

I mostly use AMD and have been using Wayland since GNOME 40 without any problems, loving the consistently perfect frames and fantastic scaling (with Wayland programs, but nowadays I use nearly no X11-only programs).

I tried Nvidia with Wayland a few times and it always was a clusterfuck. I remember when Nvidia just released GBM support on their drivers I actually compiled my own Mutter to try Wayland because there was a bug with the hardware cursor that overflowed the GPU memory. I even tried eglstreams a few times with the Nvidia-developed GNOME backend. No matter what, I always had problems with invisible programs, programs leaving trails like the cards falling in Windows 98 Solitaire when moving the window, slow programs, blurry programs, unresponsive programs, etc.

Today I tried again Nvidia with GNOME 43/Wayland on Debian 12 and also experienced lots of the same issues as I always had. I then moved to Sid with GNOME 44 and was pleasantly surprised to see nearly all my issues just go away. Have not seen any invisible programs, nor any trails behind windows when moved. I have seen abnormally slow programs though, the GNOME terminal seems to struggle when scrolling fullscreen, whereas my laptop with and AMD APU works perfectly.

Currently happily using GNOME 44 with Wayland on Nvidia, never thought I would get to say this. I'm hyped for GNOME 45 to drop in Sid!

view more: next ›

Espi

joined 1 year ago