• 1 Post
  • 55 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle




  • I used to prefer Gnome before the KDE 6 update due to the rough edges in KDE. After KDE 6 came out I’ve tried it again, and it’s incredible. The team has spent a lot of time on polish for this major release and it allows KDE’s suite of more fully featured applications to shine. GNOME apps like gedit, nautilus, and gnome terminal tend to provide the minimum level of functionality, whereas KDE’s applications feel like they’re trying to work for power users. Kate goes as far as supporting the LSP for code autocompletion. KDE’s desktop is much more customizable as well, so you don’t really need extensions to get the functionality you’d be looking for in GNOME, stuff like the application launcher are built in. KDE connect is a really useful application you can install on your phone to get file transfers and notification sharing, among other things, between your phone and computer while connect to the same local network. Performance wise they seem pretty equal, even on older hardware, but KDE might have a bit of an edge in terms of RAM usage, YMMV depending on how you customize the desktop. The one thing I miss about GNOME is their “start menu” experience, I haven’t found a way to replicate that in KDE, but I haven’t looked very hard either. Overall I wouldn’t hesitate recommending KDE, plasma 6 makes me actually feel like the Linux desktop is ready for mainstream.




  • I don’t really think it’s any of those things in particular. I think the problem is there are quite a few programmers who use OOP, especially in Java circles, who think they’re writing good code because they can name all the design patterns they’re using. It turns out patterns like Factory, Model View Controller, Dependency Injection etc., are actually really niche, rarely useful, and generally overcomplicate an application, but there is a subset of programmers who shoehorn them everywhere. I’d expect the same would be said about functional programming if it were the dominant paradigm, but barely anyone writes large applications in functional languages and thus sane programmers don’t usually come in contact with design pattern fetishists in that space.




  • NFS is generally the way network storage appliances are accessed on Linux. If you’re using a computer you know you’re going to be accessing files on in the long term it’s generally the way to go since it’s a simple, robust, high performance protocol that’s used by pros and amateurs alike. SSHFS is an abuse of the ssh protocol that allows you to mount a directory on any computer you can get an ssh connection to. You can think of it like VSCode remote editing, but it’ll work with any editor or other program.

    You should be able to set up NFS with write caching, etc that will allow it to be more similar in performance to a local filesystem. Note that you may not want write caching specifically if you’re going to suddenly disconnect your laptop from the network without unmounting the share first. Your actual performance might not be the same, especially for large transfers, due to the throughput of your network and connection quality. In my general experience sshfs is kind of slow especially when accessing many different small files, and NFS is usually much faster.






  • Back in the Gnome 2 days this wasn’t as much the case. Plus KDE was kind of a mess back then so the main choices were Gnome or XFCE which had fewer features. When Gnome 3 came around the devs switched hard to a much more opinionated approach, leading to Gnome 2 forks like Cinnamon since KDE was still very underpolished. It’s a bit regrettable that all that effort was poured into Gnome forks instead of improving KDE especially considering how great it is now.