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

help-circle










  • All the kernel access in the world won’t stop someone from having a secondary device hooked into the monitor output and faking a dumb keyboard and mouse.

    I guess that’s true, but that’d be a lot difficult to program and expensive to use compared to a simple program that can read data straight from the game’s memory in machine readable format and send inputs straight into the system’s input framework. by raising the entry bar you’re effectively decreasing the amount of people that will cheat in the game

    it’s ultimately the user’s decision if they want to sacrifice the purity of their kernel for a game like this, and I think it’s their problem if their kernel panics for them wanting to play slop made by AAA studios










  • Jumuta@sh.itjust.workstoLinux@lemmy.worldQuestion about Linux culture.
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 month ago

    there’s different ways to install things because they each have their use cases in which they’re better than others (or used to have use cases)

    • binary package managers (e.g. apt): fast and lightweight because it only downloads/installs the necessary binaries

    • flatpak: can be installed on any distro, but takes up more storage space because they’re installed in a sandbox and all the dependencies are also installed with it, for every application

    • snap: same thing as flatpak but a bit worse, but some applications are only packaged for snap because canonical paid a lot of big companies to package for snap (rhey didn’t incentivise against flatpak, they just didn’t fund flatpak)

    • appimage: the ‘windows exe’ kinda thing and has all the dependencies bundled so distro agnostic, but you have to manage the appimage files yourself unless you get a manager for it and you can’t update them centrally like you can do with other stuff

    • source code repos (e.g. aur): have to compile every new version yourself on your machine, so is slow to update, but often offers things not in the binary package manager

    • .sh files for installation: idk why these are used, they’re just annoying. a lot of proprietary software from corpos use them (probably so they can verify dependencies themselves and not trust the system)

    • binariy files (e.g. .deb): same thing as with appimage except they’re not distro agnostic

    • tar.gz: is just a compressed file format like zip