• 82 Posts
  • 1.3K Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • That’s not entirely true. Because even if you buy a strong PC, you have to make choices, depending on the game. It’s just the fps and settings we are talking about are higher floor. In example on PC people can enable RayTracing, which tanks the fps a lot. Do you go for 120 fps or 60 or maybe lower fps with higher fidelity and RayTracing in example.

    So the question to answer is still the same, its just on PC we have a bit more individual choices to make.

    Edit (added): Most people don’t have the strongest PC anyway. Look at the Steam hardware survery, most have common graphics cards like the 4060 in example. Or look at handheld PCs and laptops, with fixed hardware. And as said, even in high end with lots of money people need to make cuts in fidelity or performance; just on a higher level in that case. So your question applies to PC as well.


  • I think this question also applies to PC. Why? Because we are limited too. I try to reach 120 fps and consider it performance mode when dialing back quality settings, and enabling upscaling to reach that. If not, 90 fps is also pretty good. For certain games, 60 fps feels like what you describe of 30, but that does not apply to all games. There are single player rpgs played with a gamepad, that I would even consider playing at 30 fps if there is no other option. The problem is, games are not designed to be played with that low fps, as the input latency increases.

    I’ll compare this to the Switch, playing Zelda (emulated with Yuzu). Breath of the Wild on original Switch is designed to be played at 30 fps. Playing it on my PC like that felt like a slideshow, but one can get used to it. If I didn’t had the 60 fps patch, it would still be fine at 30. The next game in the series, Tiers of the Kingdom, was not stable at 60, so I was “forced” to play at 30. And after some time playing it felt pretty good and not upsetting like in the first few minutes.

    What I mean by that is, performance mode if possible, I would sacrifice quality. But not too much, because at some point the image looks really bad.






  • You don’t need to understand a command in order to copy paste an alias or Bash function. Especially newcomers could tend to do it, without knowing what the command actually does. We are also in a posting with helpful commands, so its double harmful. And you doubling down without adding any sort of disclaimer shows you don’t care.



  • Here is on that I actually don’t use, but want to use it in scripts. It is meant to be used by piping it. It’s simple branch with user interaction. I don’t even know if there is a standard program doing exactly that already.

    # usage: yesno [prompt]
    # example:
    #   yesno && echo yes
    #   yesno Continue? && echo yes || echo no
    yesno() {
        local prompt
        local answer
        if [[ "${#}" -gt 0 ]]; then
            prompt="${*} "
        fi
        read -rp "${prompt}[y/n]: " answer
        case "${answer}" in
        [Yy0]*) return 0 ;;
        [Nn1]*) return 1 ;;
        *) return 2 ;;
        esac
    }
    

  • For the newer version of program, that’s why we have the $PATH. You put your program into one of the directories that is in your $PATH variable, then you can access your script or program from any of these like a regular program. Check the directories with echo "$PATH" | tr ':' '\n'

    My custom scripts and programs directory is “~/.local/bin”, but it has to be in the $PATH variable too. Every program and script i put there can be run like any other program. You don’t even need an alias for this specific program in example.


  • I’m not sure what you mean with the question. If you have any alias like alias rm='ls -l' in your .bashrc in example, then you cannot use the original command rm anymore, as it is aliased to something else. I’m speaking about the terminal, when you enter the command. However, if you put a backslash in front of it like \rm in the terminal, then the alias for it is ignored and the original command is executed instead.

    Edit: Made a more clear alias example.




  • i also have the chmod one, but mine is named just x:

    alias x='chmod +x'
    

    I also have the yt-dlp "$(wl-paste)" one, but its build around a custom script. So sharing it here makes no sense. Its funny how often we do same thing in different ways (extracting or creating archives in example). Often aliases get development into function and then they turn into scripts. For some of the more simple aliases, here a selection:

    alias f='fastfetch -l none'
    alias vim='nvim'
    alias baloo='balooctl6'
    


  • With how many new Linux users we get recently, I don’t like this joke at all without a disclaimer. Yes yes, its your own fault if you execute commands without knowing what it does. But that should not punish someone by deleting every important personal file on the system.

    In case any reader don’t know, rm is a command to delete files and with the option rm -r everything recursively will be searched and deleted on the filesystem. Option -f (here bundled together as -rf) will never prompt for any non existing file. The / here means start from the root directory of you system, which in combination with the recursive option will search down everything, home folder included, and find every file. Normally this is protected todo, but the extra option --no-preserve-root makes sure this command is run with the root / path.

    Haha I know its funny. Until someone loses data. Jokes like these are harmful in my opinion.





  • What negotiation? I have a hard time to follow what you mean. Which operating system does turn off when shutting down? If it does not, then either its configured to do so (or not to) or there is an issue that needs to be handled and resolved. You don’t want your PC turn off immediately, so it can do stuff that is needed (such as wait for all drives to write the data) or remove temporary files and unmount drives and so on. Otherwise an instant turn off is equivalent to a crash (including all background services and running applications, losing data, corrupting drives…).