RADV is the default community Mesa driver, made by Valve engineers.
AMD’s own Vulkan implementation is called AMDVLK, which is just a port of their Windows Vulkan libraries repackaged for Linux. AMDVLK usually moves faster than RADV and got raytracing much earlier. And even though RADV added raytracing as well, RADVs raytracing is much slower than AMDVLK. Maybe this changes will finally close the gap?
I really like Kagi. If their browser is half as good as their search engine is its going to be fantastic.
Wipr is pretty nice.
I can’t believe Microsoft is still using this piece of crap filesystem. If they had a CoW filesystem they could even paper over the mess that is Windows Update without having to actually fix it, they could save petabytes of storage over the world and significantly improve reliability all in one go. Let’s not even mention how NTFS is amazingly slow on hard drives, manages to fragment to hell and back without doing anything, requires offline repairs like it was FAT32 and its compression barely does anything while massively slowing down the computer.
Yet here I am envying btrfs, APFS, ZFS and even fucking XFS for their reflinks and CoW.
In fact, not even WSL uses a modern FS, I think Microsoft is allergic to modern FSs.
Functional fractional scaling on GNOME.
I moved to a 4k monitor and could never get an experience I was happy with, had to move back to Windows. I could use it at 150% scaling and get blurry apps, or 200% scaling and get no screen space.
Now, most programs did work fine or I could tolerate them (I don’t care if Spotify is a bit blurry). But gaming was just bad, GNOME told the games a fake resolution and then rescaled them, so they looked awful. The best solution I found was using a Python script to disable scaling before launching a game, but it was clunky at best.
Now, the new fractional scaling extensions did add the ability to have the app handle scaling by itself, so I’m really just waiting for an option to disable scaling for X11 programs or for Gamescope to add a “tell the compositor I will handle scaling but then don’t do anything” option so I can actually get full resolution for my games.
I’m also waiting for variable refresh rate, but I can live without that as GNOME Wayland doesn’t really get tearing ever.
I love it. I have used it for very long time with and without extensions. I love the overview in particular, pressing meta and having everything presented to you is fantastic. I used it by mostly running maximized windows, then each time I wanted to switch to another program I pressed meta and clicked on the app I wanted. I used workspaces to keep separate groups of programs for each workflow separate too.
If I used extensions it was small things like Appindicators and small cosmetics like blur my shell.
Now, I don’t think GNOME scales very well if you use tens of windows at once, you would need to use too many workspaces, which are slow to navigate, and/or have tiny windows in the overview, which are hard to click because their position is unpredictable unlike traditional taskbars, where the programs are always visible and never move on their own.
My workflow never involved too many windows, so I never had problems with it.
Something else I wish would change is that the top bar should go away or actually do something other than show the time. I would say either just take it away entirely and only show it in the overview. Or turn the clock into a notch. Or just make it a half-traditional taskbar, with the clock and options moved to the right and the left side showing as many programs as they fit in thin bars.
I would say that it’s extremely unlikely.
Websites in general are never limited by raw code execution, they are mostly limited by IO. Be that disk IO as files are read and written, database IO as you need to execute complex queries to gather all the data to build the user timeline, and network IO to transfer data to and from the user. For decentralized social media like Kbin or Lemmy its even more IO limited as each instance needs to go back and forth to other instances to keep up-to-date data.
Websites usually benefit much more from caching and in-memory databases to keep frequently used data in fast storage.
This is why simple, high level, object oriented, garbage collected languages have become so common. All the CPU performance penalties they incur don’t actually affect the website performance.
While I like secure boot and leave it enabled when possible, to be honest it only protects against a type of attack so elaborate its pretty much useless. Whenever its minorly inconvenient I just disable it without worry.