this post was submitted on 23 Nov 2024
18 points (76.5% liked)

Linux

8178 readers
305 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
[email protected]
18
Btrfs should've been Wayland (lemmy.zip)
submitted 2 days ago by [email protected] to c/[email protected]
79 comments fedilink hide all child comments
 

I think the problem with btrfs is that it entered the spotlight way to early. With Wayland there was time to work on a lot of the kinks before everyone started seriously switching.

On btrfs a bunch of people switched blindly and then lost data. This caused many to have a bad impression of btrfs. These days it is significantly better but because there was so much fear there is less attention paid to it and it is less widely used.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 2 days ago

The problem is, I wouldn't know what to report and where. I've never been able to find any relevant logging, neither in /var/log nor in journalctl. I doubt opening an issue with 'desktop locks up randomly when using Wayland' is really useful without any logging. And where would I do that? At the Wayland bug tracker? Gnome or KDE? Kernel, as it indeed might be a driver issue? And there is of course the time component: I use my laptop for work, so I simply cannnot spend hours on debugging this. That's time I don't have, I'm afraid.