- 84 Posts
- 616 Comments
1·8 days agoThose are all good reasons. XFCE aims to support Wayland with the next release, so if they choose to use an established compositor it shouldn’t be too buggy.
With XFCE porting their apps over the setup shouldn’t change much, unless you’re using Xorg specific tools.
Over the last few years most features I’d expect from a windowing system were added to Wayland, so I expect the drama to cool down. (I don’t even know what’s still missing (except accessibility), with VRR, tearing, DRM leasing (VR), and global hotkeys being done. It’s just apps like Discord that have to cave in under the pressure to fix their apps.)
Once everything works, there’s no point talking about it.
@Furycd001@fosstodon.org
They don’t take money from investors but grow organically, which limits their resources quite a bit. With more users being on other platforms and Linux being a bit more complex when it comes to amount of possible filesystem and other combinations I see why it takes them a while. Iirc they also do e2e encryption of (meta-)data which does increase complexity.
Hopefully they’ll finish it at some point, as it’s been a long time since they announced Proton Drive. As I’m not paying for Proton, I understand a paying long-time subscriber might not share my acceptance of them zaking their time.
Afaik the OSTree snapshots use BTRFS deduplication […]
Note: OSTree will transparently take advantage of some BTRFS features if deployed on it. [1]
Interesting, I didn’t know OSTree takes advantage of BTRFS features.
On my current system I use ext4 instead of btrfs which I regret specifically because of the missing transparent compression and reflink copy.
I prefer to stick to defaults whenever possible.
Same goes for me.
E.g. changing vim keybindings on my local system to better suit my non-QWERTY keyboard would be annoying since they don’t transfer to remote systems. That’s a reason I like fish, because it’s defaults are modern and useable, compared to zsh/bash which benefits strongly from plugins.
I like all editors to have as many diverse sets of keybindings as possible. Sadly most apps don’t, which is a main reason why I never bothered to properly learn emacs bindings, as I wouldn’t be able to use them anywhere else.
It’s definitely just my opinion. Honestly did not mean to imply otherwise.
For my opinion I usually create a comment below my post to seperate my opinion and the post itself.
On-topic: I do believe it’s useful to have this switch and there’s nothing stopping distros to change their default. Completely replacing the default keybindings might be surprising to long time users, but I also believe it should be done at some point. For the meantime this switch can be simply added as an alias.
People who only use the terminal to edit a few config files are usually fine with nano. Even more so with these new keybindings.
For more involved edits an editor like VSCode is usually more useful anyway.
For me vim works well, but I’ve already taken the time to learn its basic usage.
Maintaining btrfs is more work than maintaining ext4, which basically doesn’t need any. I.e. running btrfs scrub is important to keep performance up. Monthly scrubs are good because they don’t take as long if done regularly.
Btrfs balance can free up some space, but otherwise isn’t important on SSDs.
It’s amazing to see how Alyssa Rosenzweig took Faik Ekstrand’s NVK and repurposed it for Apple Silicon. I think this is a great example of the strength of open source, where code can be repurposed (if a competent enough individual comes around).
I’ve heard before that NVK is good building block for the future to make better drivers for all GPU’s, but I’d never thought it’d be reused this fast. I wonder whether they’ll be able to take NVK improvements easily to Honeykrisp, and vice-versa in the future.
Also, it’s incredible how the state of Linux on MacBooks is better than in the late Intel days, now that such competent developers focused on getting the hardware running (it’s been quite difficult to install Linux on some Intel MacBooks, I believe because of their security chip).
deleted by creator
11·1 month agoYes, Linux OS are usually lighter on hardware. But if we’re talking about gaming and other heavy applications usually have the same hardware requirements.
Windows Defender, update checker and other system services on Windows do tank performance by a few percent as shown by those “debloated” Windows images.
But DXVK also usually reduces performance by 5-15%, even more so for VKD3D. This outweighs the performance gains of less background services. Not to mention I’m (and I guess most people are) running apps like Discord, Spotify and Firefox in the background.
There’re games running better on DXVK than native D3D, but that’s usually because they are using an older graphics API that isn’t optimized on newer GPUs. Both GTA IV and Sims 3 use DirectX 9. Interestingly, running older titles om Windows with DXVK also results in performance gains.
I certainly didnt notice any difference […]
Me neither, except for a few games where my hardware was already struggling. Without direct comparisons I’d say a 10% performance overhead is negligeble too.
They likely don’t play Valorant, Fortnite, Roblox, Rainbox Six Siege, Destiny or League of Legends.
Basically all of my games run well on Linux, but I wouldn’t dare say they run better on Linux than Windows. Some do, e.g. Minecraft, but almost all other games have at least a bit lower FPS.
If games build for Windows in general ran better on Linux it’d be pretty surprising, given the amount of investment into Windows gaming there’s from many more big corporations than we have on Linux.
Linux gaming is better than ever, but there’s enough people expecting too much and going back to Windows because of Linux gaming shilling.
I’d call it ppa without the drawbacks, aka. breaking the OS on upgrade (from wrongly packaged or out of date ppas).
Thank you, that’s a really useful list. A week or so ago I didn’t know there was an (unofficial) Firefox Nightly flatpak remote, so I had to use a tarball. This would’ve saved me a bit of time.
I also didn’t know flathub subsets for verified/floss apps were already available.
7·1 month agoTorrents are based on the idea that everyone using them pays for it with their bandwidth and hardware cost. Except for those leechers who don’t share.
I’m paying more for my seedbox than for my usenet subscription. If I used my own hardware I’d pay with stress on my hardware, e.g. the disks aging and failing earlier because of seeding. The power consumption is also not negligeble, altough the server is also used for other purposes.
With private trackers this idea of an equal exchange is more obvious because of ratio requirements.
Edit: I’d say it’s similar to open source in that no single individual has to pay for it, but someone does have to, for it to exist. Most often with their (valuable) time and knowledge. If no one helps out and does their part (through money or time+knowledge), a project won’t survive for long. Same is true for torrents.
Same. It’s been great on a few occasions, but I’m not playing much in general. It still came down to a third of my playtime being on Steam Deck last year.
Though I have to say I did use it more than I expected over the last two years.
I will be surprised if Spotify won’t announce a new more expensive HIFI subscription with their support for lossless audio. Imo this still makes it less interesting than Tidal/Deezer/Qobuz since it’ll still be impossible to permanently download music from Spotify.
Nonetheless it’s great that Spotify will provide lossless audio for those who want it.
11·1 month agoAre you using multiple monitors? With X11 multi-monitor setups one of the monitors always tears if the framerate aren’t multiples of each other (e.g. 120Hz + 60Hz works fine, 144Hz + 60Hz results in tearing with one of them). This is also the case with variable refresh rate (FreeSync), but VRR shouldn’t be an issue as it’s not enabled by default on X11 iirc.
You’d have to manually enable Wayland, because PopOS disables it by default (does not show in the login menu/GDM). Keep in mind that PopOS is based on Ubuntu 22.04, which is quite old at this point. Wayland might not be as good of an experience for you because lots of improvements happened over the last two years.
PopOS will release their new COSMIC wayland desktop environment with updated packages in a few months, which should work well for gaming and fix your tearing issues.
If you want to try whether Gnome Wayland solves your issue, you can edit
/etc/gdm3/custom.confand setWaylandEnable=true. After a reboot you should be able to select Wayland in the bottom right corner at login.
1·1 month agoYou’re right, thanks for correcting me.
From systemd licenses readme:
I can understand critism of systemd for its tools only working with itself and not with any other Unix tools. But it’s absolutely a conspiracy theory to think they’d want to charge for systemd. Though I do agree that if someone was charging for systemd (which they can’t because its open source), open source alternatives would pop up.