• 0 Posts
  • 114 Comments
Joined 1 year ago
cake
Cake day: November 20th, 2024

help-circle


  • I nearly died. They say I must journey into the AUR realm for legacy GPU drivers, and I would have fallen into the text-only abyss had I updated days later (assuming I had not heard the news). My internet is too slow for regular updates. Continue onwards without me, I’ll just rest here at this long-outdated version.

    Generally I don’t think rolling release is the issue itself (I have been using it for years), but it seems like every packaging/updating scheme out there sucks for one reason or another. Every time something looks like it has the answer, there is something else that works contrary to what is expected/desired.




  • You’re right, I wouldn’t. None of what I said is specific to 3.1, and I do use Blender for ancient techniques (visible vertex color) rather than old software (even though I would like something simpler).

    As to why anyone would do it? Familiarity and a “workstation” feel I’d guess, especially the more in-era stuff is added (software workflow, CRTs, scanners/printers). Maybe it’s just another way to avoid the modern mess of ads, AI, frequent updates/changes etc.

    For someone producing a retro project, I could also see using an older OS as something akin to method acting (similar-to but-not-quite ‘dogfooding’). Stew in the exact design language and technical sensibilities you’re trying to replicate, rather than reading about it or looking at screenshots.

    Bryce 3D was also just an example (and LGR’s video being the exact sort of energy I’m talking about), though I’m not sure how the newest version would compare on workflow and aesthetic. Seems like it’s more focused on realistic landscapes.




  • insomniac_lemon@lemmy.cafetoComic Strips@lemmy.worldGuns
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    19 days ago

    The artist actually does do advertising stuff (including merch and crowd-funding) on imgur (+reposting/rehashing too) and reddit so I sorta get it, but posting art by someone-who-conducts-themselves-in-a-manner-you-dislike is counterintuitive.

    I wasn’t even entirely sure it was this until I saw the mention of Patreon on the image, as the talk of signatures in the comments is jumping the shark a bit.


  • It’s pretty easy to uninstall and make certain packages taboo

    I remember reading that you couldn’t turn it off unless you outright disabled recommended packages. Reading again, I see conflicting statements and it seems like a common thing people take issue with. Though even locking seems to me like it should just be something that happens during explicit removal, if that is a fix.

    So I still kind of hate stuff like that.

    Making a system either unresponsive or worse, broken. I feel it would be a workflow nightmare of a scale that would beggar belief and it would need constant attention from the maintainers…Something we’d probably not see in our lifetimes

    My system is currently outdated and mostly usable, but has 4 different application issues (1 crash, 1 flicker, 1 compiling/library error, 1 feature error)… before I stopped updating, rolling updates gave me a few bad rolls that did not fix some of these issues (and if I’d have rolled not even week later w/o reading the news, I would’ve been toasted into terminal-fix-it-now-land).

    So I’d say there’s a lot of room for improvement here. I dream of something that works like this:

    • bin.fast: Major.minor.greatest, 7…30 days
    • bin.stable: Major.minor.greatest, 30…180 days
    • userspace: any version (including non-system package formats), total install/non-shared-dependencies size may influence update frequency (or budget)
      • small things may update always, big programs may even get to the point where it switches the install over to a bin version for you rather than compiling again
    • userspace packages may also slow down dependencies

    Non-critical applications may be updated less. Security updates or marked-as-needed-fix more. Alternatively, supporting explicit branches (like Godot’s 3.X and 4.X) in official repos helps. Maintenance updates (nothing known broken) may be delayed if something seems/is-known wrong (build-bots, user reports or comments, upstream fix needed or dependency too new, admin/maintainer intervention etc)

    Ultimately, this could mean an update about every week or slower than once a month depending on packages and if the user encounters issues or not. And I’m sure this may be possible with some package system, but again not something default (and less effective if a package system doesn’t provide the needed structure/information).

    Hardware wise, yeah I’m otherwise still pretty happy with the performance level I have (and it’s a fine target for my own stylized projects, still working on that). A smaller(+more efficient) system would be nice, but GPUs seem to still be behind/lower-value than CPUs though. Polaris would be fine just to make things easier though, not that I want to buy a sidestep especially when the market is so stagnant. Same thing with workarounds that won’t be really cheaper either (esp, w/RAM etc pricing).

    This is why I am very careful to use a small amount of them as there are a few apps

    What I’m talking about was an issue with 1 package due to sandboxing, and it was Krita IIRC (something I don’t care about sandboxing on). I think KDE stuff was being pulled in too (I don’t use it, but I do use Kate and few other things that use Qt).


  • For me, I didn’t like patterns (or the work-arounds). A shame because it (or now, maybe slowroll) might be closer to what I’m looking for, especially if the talk of smoke-testing is true. (though I’ve also seen someone say that Zypper is slow)

    I like some of what I’ve seen with NixOS, though I see quite a few things that make it seem like not the answer either. And some of the things (like distrobox) seem like they probably add weight to updating as well (and/or clunkiness, if I have to manually do it).

    Also some of my issue is I’m still running a 1050Ti (and Arch putting the legacy drivers on the AUR, a bit of a pain for me… not sure if that has changed though), I know that’d likely be even worse on Nix as well.

    EDIT: I’ve tried Flatpak for user apps as well, and needing to download graphics drivers again really defeats the purpose.

    Ideally I’d like something that has an update system intended for slower internet. Something that can pull (/keep) slightly older dependencies when user-land stuff is a bit slow, or outright delay/reschedule possibly-broken (for any number of reasons) updates rather than wasting a user’s time and bandwidth. Guessing it doesn’t exist, though (or if it does, it has some other huge workflow flaw).

    Mentioning @LostWanderer@fedia.io because they’ve talked about Tumbleweed and Nix.








  • insomniac_lemon@lemmy.cafetolinuxmemes@lemmy.worldFeature parity or get out
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    5 months ago

    Yeah I tried it for XFCE yesterday*, noticed a few things I wanted weren’t there (because XFWM isn’t ported over) and promptly switched back. Didn’t seem to me like it was more responsive or anything like that**.

    But I am still using a 1050Ti, so who knows. That also kind of kills my interest in the idea even if I didn’t have fixed-if-you-use-this-specific-DE type issues. I also don’t really like the idea of CSD.

    * after looking up that labwc not being installed was why the session wouldn’t launch before

    ** entirely possible it is better in very specific scenarios, but the screen tearing that I see on X11 is diagonal (like the screen is 2 triangles, desynced) and honestly I don’t even know the exact game to test (as I don’t see tearing in videos or any other usage as far as I know)