Linux

8159 readers

83 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:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 1 year ago

MODERATORS

[email protected]

Btrfs should've been Wayland (self.linux)

submitted 11 hours ago by possiblylinux127 to c/[email protected]

61 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] 1 points 11 hours ago (19 children)

Wayland didn't work out networking, even to this day, which is why I'm still using Xorg.

[–] [email protected] 1 points 7 hours ago (13 children)

X's network transparency is overrated IMHO. Since ages most data on desktops is sent via shared memory to the X server (MIT-SHM extension) otherwise the performance would suck. This does not work over the network and so X over the network is actually quite slow. Waypipe works way better for me than SSH X forwarding.

[–] [email protected] 2 points 7 hours ago (3 children)

@hummus273 I have a 1gbit network connection at the co-lo, and 180mb/s cable and I don't have any lag using X tunneled through ssh.

[–] [email protected] 2 points 7 hours ago (1 children)

Not having any lag is physically impossible. You don't notice it maybe. But if I open Firefox with X forwarding on the same network (1gbe) it is very noticeable for me.

[–] [email protected] 2 points 7 hours ago (1 children)

@hummus273 Perhaps not because I'm not trying to game, and I can't detect any changes faster than about 1/50th of a second anyway so fps faster than 50 is more or less moot for me.