• 0 Posts
  • 34 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • yoevli@lemmy.worldtoLinux@lemmy.mlGIMP rebranding as WLBR?
    link
    fedilink
    English
    arrow-up
    50
    arrow-down
    4
    ·
    4 months ago

    I can understand the desire to change it given that the current name is arguably a slur in some contexts, but this is a terrible new name. There was a fork awhile back with this same motivation called “Glimpse” - I really think they should have chosen a name with some continuity from the original, and certainly not what looks to be an initialism (I never would have come to “Wilbur” on my own).


  • yoevli@lemmy.worldtoLinux@lemmy.mlGIMP rebranding as WLBR?
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    “Git” is only really a word in British English which implicitly gives it lower worldwide cultural penetration than a general English term. For most non-British programmers (and honestly I would imagine many British ones given how ubiquitous Git VC is now), “Git” refers to the software first and the pejorative second, if they’ve even heard of the latter before.


  • The second paragraph isn’t accurate - Android uses the Linux kernel. Hardware manufacturers typically ship their own proprietary modules, but in principle there’s nothing stopping you from running a mainline kernel image as long as support for the specific device or SoC is present. Granted, this isn’t the case for the majority of phones, but this isn’t a limitation of Android itself and you’d run into the same issue trying to run postmarketOS or really anything else on an unsupported device.

    I also want to point out that there really aren’t any good alternatives to Android (and its derivatives) at the moment. Mobile Linux distributions are getting better, but at least in my personal experience and from what I’ve heard from others it’s still a pretty janky experience in comparison and arguably is only suitable for enthusiasts.






  • It’s overall a pretty good experience, but there’s occasional weirdness you may run into. For instance, up until a month or two ago I was encountering a bug that caused my phone to basically slow to a crawl after running Android Auto for 20 minutes or so, with a reboot being the only solution. This happened once while I was driving somewhere unfamiliar and it took about 5 minutes to start back up due to app optimization (which, incidentally, I don’t remember being a thing on other Android flavors after 2018 or so) so it turned into a whole adventure.

    There’s also a fairly persistent issue I’ve run into where GrapheneOS starts very aggressively killing background apps, like as soon as another app gains focus. Not sure what that’s about but I haven’t really encountered it on other Android versions to the same extent, so I’m inclined to think it’s GOS-specific.




  • Fedora Workstation has been really good in my experience. The available software is shockingly up to date and I haven’t run into much breakage of any kind in the year or so I’ve been using it across 2 systems (despite my best efforts every few months when the urge to tinker hits me). I do occasionally run into issues caused by the default SELinux policies, but they’re not especially difficult to work around if you’re comfortable using the terminal.

    I do share your sentiment about the AUR - I definitely miss it at times. That said, Flatpaks and the fact that pre-built RPMs are so commonplace have both softened the blow a lot.








  • The way I look at it is that most of my time spent fighting with the compiler is usually made up for in time saved debugging. I’m in the process of RIIRing a hobby project and so far most of the ported code just works, and I only end up needing to fix a few dumb logic mistakes before it’s fully up and running.


  • I’m not familiar with the specific install/upgrade process on Gentoo so maybe I’m missing something, but what’s wrong with forcing new installations to use time64 and then forcing existing installs to do some kind of offline migration from a live disk a decade or so down the line? I feel like it’s probably somewhat uncommon for an installation of any distro to be used continuously for that amount of time (at least in a desktop context), and if anyone could be expected to be able to handle a manual intervention like this, it’s long-time Gentoo users.

    The bonus of this would be that it wouldn’t be necessary to introduce a new lib* folder - the entire system either uses time64 or it doesn’t. Maybe this still wouldn’t be possible though depending on how source packages are distributed; like I said I dont really know Gentoo.


  • yoevli@lemmy.worldtoLinux@lemmy.mlLinux middle ground?
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 years ago

    The fact remains that Arch generally requires more work to maintain an installation than a typical point-release distro. I’m speaking from experience - I had two systems running Arch for over 2 years. I switched away when each system separately had a pacman update somehow get interrupted resulting in a borked install. I was using Mint before and Fedora now, and both are a lot more hands-off at the cost of some flexibility.

    Also, just to be clear, I’m not trying to disparage Arch at all. I think it’s a really cool distro that’s perfect for a certain type of user; I just don’t think it’s great to lead people to believe it’s more reliable than it is in the way that I’ve been seeing online for a while now.