• 0 Posts
  • 25 Comments
Joined 4 months ago
cake
Cake day: March 2nd, 2024

help-circle











  • poorly written code and tight code

    This is where you guys lose me, it’s just code that not optimized for size and that’s because most people don’t give a shit about that. People want want their 4k assets, their localization, their accessibility features, their application to run on any device… All this comes at a cost. You want to change things, that’s fine, but start by understanding why things are the way they are because shitting on developers won’t get you anywhere.


  • Size doesn’t matter much when you have SSDs that read upwards of 5000mb/s. It’s why we’re seeing an advent of web-based apps despite them being woefully inefficient, and why games regularly go above 100gb. The reason file size gets so large is that assets can take up a lot of space and they come with plenty of libraries that they just have to bundle. These “small size” software optimize for size at other costs, like speed, asset quality, development time… Reducing file size is just not relevant anymore and if anything you should be wary of software that do it.








  • imecth@fedia.iotolinuxmemes@lemmy.worldGnome developers in a nutshell
    link
    fedilink
    arrow-up
    1
    arrow-down
    3
    ·
    edit-2
    2 months ago

    If your code isn’t up to par, or your feature isn’t relevant enough and doesn’t fit “the vision”, it’s correct to deny it. On top of diluting the project contributed code add a maintainership cost that the random contributor will probably not be footing.

    Accept everything in your cake and tomorrow it’ll be an inedible mess that nobody wants. It’s ok for software to be aimed at different people.