• 29 Posts
  • 43 Comments
Joined 2 months ago
cake
Cake day: October 2nd, 2025

help-circle
  • ashx64@lemmy.worldtoFirefox@lemmy.mlSo Long, Firefox, Part One
    link
    fedilink
    arrow-up
    3
    arrow-down
    7
    ·
    edit-2
    8 hours ago

    I don’t like Brave’s leadership or crypto, but the problem for me is that Brave ticks the most boxes

    • Adblocking
    • Privacy
    • Security
    • Multiplatform
    • Web Apps

    There are browsers that do stuff better, like Vanadium and Trivalent, but those are locked to specific platforms, have poor built in ad blockers, and encourage you to never install extensions for security reasons.

    And if I want to avoid the Chromium monopoly, there’s Webkit which still manages to have good security and privacy, but there’s no Webkit browser on Android and on Linux, Gnome Web feels slow to use and doesn’t have a good adblocker.

    That being said, I’m still on Firefox right now. Chromium has some weird quirks on the desktop that annoys me so much.





  • In my experience, many Gnome apps make doing complex tasks pretty easy compared to third party apps. However, it is at the cost of customization and questions like “why can’t I do this???”

    But in general, Gnome’s simple design works for me, most things feel clean and polished. I don’t need the vast majority of features offered.

    In the cases where Gnome’s default aren’t powerful enough, often times the KDE equivalent isn’t good enough for me either despite offering more features and customization.

    As an example, Gnome Text Editor vs Kwrite and Kate. GTS has the basics I need like line numbers (Apple’s text editor does not have this…) and that fits 80% of my needs. But what about more advanced things? Well, no markdown support but I don’t think Kate has that either. What about coding? I’d rather use a dedicated IDE than Kate or GTS.




  • That’s valid.

    That’s also part of the reason I like Webkit. It’s in a nice spot between Firefox and Chromium when it comes to security and performance. And importantly, is not from an ad company and often passes on browser specs that would be harmful to privacy and security.

    I forget what the site is called, but I saw one that nicely layed out different browser specs and gives the explanation why one of the engine developers decided against supporting or implementing it.

    I just wish there was a good Webkit browser on Linux. Unfortunately, Gnome Web just feels slow and unresponsive despite good benchmarks.
















  • The for argument is basically the following

    • Wayland as a protocol was designed around CSDs, protocols for SSDs came years later
    • Having the client control the CSDs simplifiies things for the compositor and apps
      • The compositor has less things to implement and test
      • Modern apps tend to prefer CSDs anyway since it provides more flexibility, very common on MacOS and Windows
      • It’s difficult to coordinate things between the client and compositor.
        • Something that annoys me about KDE is that they do this headerbar look where the top part of the application will match the color of the the titlebar. However, the top part of the application is drawn by the application and the titlebar is drawn by the compositor. But when the color changes (such as going from unfocused to focused), they do not update at the same time, so for a frame or few the top part of the application is a different color than the titlebar. That wouldn’t happen under CSDs.