she/her

  • 1 Post
  • 15 Comments
Joined 3 years ago
cake
Cake day: January 11th, 2022

help-circle


  • (who btw farms montages in low rated btb games)

    Typical, so many of the people who complain about the existence of SBMM in games are people who want to be able to constantly stomp players who are worse than them (when people complain about “not wanting to sweat all the time”, this is pretty much guaranteed to be the actual reason)

    While I don’t doubt that Halo and CoD have flawed matchmaking, people usually use those to say that SBMM as a whole is a bad thing, or even that it’s “ruining gaming”, when it exists for good reasons and benefits a lot of games

    You rarely see people complain about it in fighting games for example, usually when people do it’s because the developers of a given game have designed an original system that does a bad job at actually matching skill, when a typical Elo-style system would’ve worked far better




  • That’s not mentioned in this specific blog post, but that’s always been one of Vanilla OS’s defining features, it’s “apx” package manager to install those various types of packages

    It’s even using Distrobox actually, but the point is to make it simpler to install packages for those contrainers, with the user not worrying as much about managing the individual containers, and not having to memorize the specific commands for each individual distro’s package manager

    Basically, like the rest of Vanilla OS, the point isn’t that you can’t do this stuff elsewhere, it’s that it’s trying to make it easier to do it




  • because the package build script isn’t available?

    What are you talking about? Every Flatpak on Flathub has their build manifest available on GitHub, you can fork or download it for yourself and change it how you’d like, just like you can with an Arch PKGBUILD

    And the problem still isn’t solved because now the people who can set bad defaults still exist, they’re just different people.

    For one, unlike with distro packages, lots of Flatpaks are made by the developers of their apps, so bad defaults aren’t really going to be a thing for those since the developer would want to choose what’s best for their own app

    And for packages maintained by a third party, bad defaults are less common because maintainers don’t need to account for each individual distro’s unique package situation or specific dependency versions, and only have to package it once for every distro