Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ME
Posts
26
Comments
1,138
Joined
2 yr. ago

  • ChromeOS is so funny because it's either way too anal about what you can do or there's a part they forgot to harden against end users and the power of linux spews forth with endless destructive potential

  • Because the underlying dependencies of GIMP changed a lot, especially between GTK2 and GTK3. It pulls resources from writing code to figuring out how to migrate code to a new version, usually as changes in the toolkit mean you may have to rewrite stuff anyway, which can mean more bugs or regressions in functionality which must be addressed.

    Writing from scratch, you can write code that immediately fulfills the spec you're working to (They could've even skipped straight to GTK4!) and used the old code as a reference of what's needed for users whilst throwing out anything and everything else that isn't strictly necessary.

    It allows you to throw out old features and code that you had to work with in the past, but may not actually be used by anyone. If it WAS needed, it can be added later.

    Most importantly, there's little to no expectation that the new app will supersede the old one immediately, whereas during a toolkit migration you need to keep everything working for every release you do.

    It's like how building a new house can be faster than renovating an old historically-protected building to the same regulatory standard. There's red tape, you have to work around old masonry and brickwork, you have to avoid damaging the building and keep its appearance the same. A new house may be different in looks and miss the old charm or familiarity, but it'll be built faster, cheaper, and for the same price have more features to the old building.

  • That's different to how dependencies are managed when developing an application. When they're updating GIMP and updating it from GTK3 to GTK4, they have to upgrade a bunch of old code that was meticulously fixed to work with GTK3, and things may be changed, broken, or missing entirely. That's the kind of work you need to do when upgrading an app versus writing a new one from scratch :)

  • If the modern internet teaches us anything, its that everything is ephemeral even when you stringently catalogue every last byte of data. People just dont need access to 90% of YouTube's library, yet Youtube has to pay big money to make 100% of that library available 24/7 365.

    There's already rips at the seams of these systems. Time is not on the side of YouTube.

  • Im seeing more communities on my feed than ever. Even if it's shrinking, the ones who stay are active.

    Just FYI, every "wave" of signups from some reddit/other news relating to lemmy will always be followed by some falloff as people dont both signing in every day -- which is basically how people use reddit and other apps but with such a large installcount they're not as noticeable.

  • Because updating dependencies after a long time breaks most of that code anyway, so you have to do a lot of work just to get things working exactly how they were before, only now your code probably has a bunch more bugs that you now have to fix, and it's still not utilising enhanced features that updated dependencies may offer.

    Rewriting can take more time, but if your alternative is to slowly upgrade code originally written in the nineties, you're actually saving time by using your experience to rewrite something.

  • Eh, I wouldn't want him being torn asunder by the Labour party's internal politics which are pretty hostile to anyone vaguely progressive. Having him in Manchester at least means Manchester is partially shielded from both the Tories and Starver's Labour.