• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: November 16th, 2023

help-circle


  • This is…kind of stupid? There’s such a plethora of options in the Linux space for desktop environments, workflow customizations, configurability, etc. nothing is locked down by taking a Windows-style approach to a DE. Instead it follows a tried philosophy that’s only really been hampered by Microsoft’s decision to funnel users into an frustrating hole that removes the choice to disable or modify features you don’t like. KDE in particular has always been a Windows-style DE, and it’s currently one of the best options for modern features and extensive customizability. Hyprland is literally designed for linux enthusiasts. Gnome is the Mac analog, Xfce is your light-weight but functional, etc.

    You’re upset because people are looking for more options? That’s bizarre. I came from Windows, but I guarantee my setup is different than someone else who comes from Windows because that’s the flexibility that’s offered. No one coming from Windows wants it to be exactly like Windows, they just want to be able to use their computer in a way that allows them to work, to play games, to watch media, etc. It’s a computer. It’s your computer. It should be able to do what you want.








  • I see this comment every now and then, and it always forgets the cost of the transaction, confirmation time, and of course, the need for miners to exist to process these confirmations/transactions. The energy cost is extraordinary, and the end user is taxed for the use of their own dollars.

    It’s not really feasible on a broad scale. Bitcoin is a holding stock, not a valid currency. Its value only increases because it manufactures its own scarcity. And as its scarcity increases, it naturally moves toward centralization since mining becomes too large an activity for the individual to reap any benefit. You can argue for proof of stake to eliminate the need for mining, but then you open the doors to centralization more immediately.



  • Imo, plugins should have separate config files, with uniform, consistent formatting. Separating them ensures that plugins never modify primary configuration details, they can be updated independently, or deprecated without affecting future functionality. It also means you can take regular and reliable backups of each config.