• 1 Post
  • 159 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle
  • Yeah, the COSMIC desktop environment is relatively newly developed. I also just checked on the PopOS webpage and their newest version is still 24.04, so you actually tried a version from two years ago when COSMIC was truly newly available.

    They’ve been working on the 26.04 release (based on Ubuntu 26.04) since April, but at some point, I read that they’re still also heavily working on fixing up COSMIC to be actually decent, which is why that release is so delayed.

    So, it could be that in a few months from now, it’s been released and it won’t be so buggy anymore.
    But it still won’t be nearly as customizable as KDE Plasma, as that just requires years of work and a big community, so make of that what you will. 😅




  • Just in case you’re new-ish to the Linux world: The customizations you mean are probably from KDE Plasma, which Fedora just …well, distributes. 😅

    So, if you switched to openSUSE with KDE Plasma or Kubuntu or such, those customization options would still be there.

    And yes, KDE is excellent. 🙂


    Side-note: Fedora does have its own crash reporter (ABRT), but KDE has one, too (DrKonqi), so you’re right either way…


  • Yeah, I always wonder, if it was an intentional decision or just some first draft that stayed in.

    Because I do think, it’s kind of smart. Some macros make sense to call with either () or {}, depending on if you pass a code snippet that’s multi-line or not.
    So, you could come up with a complicated syntax to define which bracket types are acceptable, or you could just not bother. 🙃



  • Oh man, that’s a good point. The longest answer is likely either the ridiculous answer when you’re supposed to catch the odd one out, or when you’re supposed to pick the correct answer, then it’s likely the nuanced take.

    I had not thought about it this much yet, but I’ve definitely also started only reading the short answers, if none of the long answers sound right.


  • So,

    • someone googled “racist joke”,
    • decided to include it into a presentation on how not to be racist,
    • decided they themselves don’t want to be racist, so the joke should be told between people of different skin color, and
    • at no point did they get up and just walk into the woods, never to return to human society again.

    That’s certainly not the choices I would’ve made, but sure.




  • Functional programming is definitely worth a look in this regard as well, but what really drove this home for me is Rust.

    Its ownership+borrowing concept is exactly that, it enforces that you’ve got one place where an object is managed and in particular mutating can only be done in at most one place.
    Obviously, there’s also ways to get out of that, in case you do want some memory managed centrally, but it just isn’t the default.



  • Moreso correctness, not security. In the end, your user is shooting themselves in their foot, if they mutate a variable that they shouldn’t, and by making the variable private and only offering a getter, we document that.

    Having said that, there’s also big differences between languages and paradigms, though.
    In object-oriented / garbage-collected languages, you often pass around references to an object into so many places that you need to code defensively versus your own codebase. That’s why getters/setters were taught religiously during the height of OOP.

    In other paradigms, you often just have one place that uses an object and then you can …simply not shoot yourself in the foot there. When you control both the definition and the access, you don’t need to protect yourself from yourself. In particular, you would probably think twice before mutating an object anyways.





  • Well, you have to fill in how the downloading and the uploading is implemented, but the orchestration of when the steps save→download→merge→upload should be done, that’s pretty useful IMHO.

    Yeah… locking the file on the remote would be the absolute minimum for an actual sync tool.

    Hmm, I guess, you could upload a lock-file, then download the database + re-upload with changes, then delete the lock file.

    I mean, I do get why they didn’t implement it (yet), as it adds quite a bit of complexity and it’s just not relevant for personal use.
    Hell, at $DAYJOB, we used to have a KeePass database on a share for the entire team, where everyone would just hit save whenever, and I’m not aware of there ever being a problem with conflicting edits, because you just don’t add/modify passwords that often.