If you move from twitter thinking it’ll not end up like twitter you’re wrong. It’ll go through the same growing pains process and you’ll end up right back where you started with nothing to show for it.

Yet

No. The less code for a given set of functionality the better… often. Removing functionality just to reduce code is daft. Otherwise stop adding any features. Remove all features of the kernel until machines only just boot. Lot less code!

But that’s true of all code in the kernel. If any change can break something then all broken bits will need fixing. Why not remove all drivers in case an update breaks them. Things can’t be preemptively fixed before breaking changes are made. A driver can be complete and only need updating if someone else breaks stuff, so leave it alone until then and only remove it I’d no one comes to fix it.

Removing functionality just in case is daft.

Why clear them out if they still work and are useful? Seems like a backwards step. What’s that phrase that people throw about:sometimes things are just done and don’t need changing.

I’ve never heard anyone say ZFS broke, corrupted their data or failed in any way at all. With btrfs it’s a consistent complaint. And btrfs literally has modes of operation that are known to be broken. I could understand if it was a new file system, but it can almost drink in pubs.

So, what you’re saying is, “it works on my machine”

You’re right to give up on btrfs. It’s been so long in development and it just isn’t ready. Ext4 or ZFS are mature and excellent file systems. There’s no need for btrfs these days. It always has and always will disappoint.

Everyone singing the praises of it are the sysadmin equivalent of the software engineer yelling ‘it works on my machine’ when a user finds an issue.

That was my point

If it’s for more than a minute I’ll screw in VGA and DVI cables

20 years ago there were 2000000000 fewer people in the world.

To send to the same account?

I haven’t paid anything for it

As long as there are no problems with the btrfs code? Hahahahaha!! There are.

It was forked but somehow lacked a huge amount of functionality that Emby had (and still has) Like I think it only supported films, not music or TV shows. The app infrastructure was awful across fire stick, Roku and android and wasn’t backward compatible with the Emby apps. I just didn’t see the point of forking it if you’re just going to make it worse or only address the server side and neglect the clients. The whole thing has to work together with good clients and server.

Last time I tried it it was a much worse experience than Emby across all devices and for all media types. I don’t understand all the love it gets.

None of them…

ssh-keygen -t ecdsa -b 384

Then get it signed and use the certificate.

SSH certificates are where its at.

KDE Connect

Signal

Email

Using Eternity and very happy with it, just as I was when it was Infinity for Reddit.