• 41 Posts
  • 865 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • Because of idiots like them, either not understanding what woke means, or by taking it to comical extreme, real issues get buried under. I wouldn’t be surprised if this list was created by an Ai or was meant to be funny in the first place. I would say some stuff there has nothing to do with wokeness at all, such as gay relationships is too woke for them. I go this far and say whoever made that list seems to be anti-gay.

    And that’s my take, going too extreme is always bad and destroys any nuances and makes real problems hard to find and discuss.



  • Salty developers who got blocked on Twitter, lol. First, who cares what opinion some person has on Twitter. It doesn’t affect or is related to Godot. Without context or being involved, i have to assume the community manager had reason to block those people who got annoying. You guys make problems out of nothing. Also how serious can we take it, if this is documented on knowyourmeme and are events happened on Twitter? About Wokeness of games?

    The fork of Godot won’t change anything of this subject. It only supports toxicity towards the developers and splits the community for no reason. Your fork won’t solve the problem that you got blocked in Twitter.





  • If I do ps aux | grep root, then the newline is preserved. So I’m not sure what exactly the problem is. There is a user option for ps, but it does not work with aux, ps --user root . You can ps ax --user root, but I’m not sure if this output is what you want.

    Btw if you grep, then I recommend using ^user , so it only matches the beginning of each line (the actual username), as ps aux | \grep ^root (notice the backslash). Do you have an alias for grep? Try \grep instead. The backslash in front of the command will use the actual command and ignore your alias.












  • I like these self made scripts. Some ideas to improve this: a) instead ls, use find command if you want use its output as input in another program (will yield fullpath too), b) fzf has a preview functionality, which I like a lot to use when it comes to directories or script files. As for the run command, I’m not sure why you use xargs and what i3-msg is needed for. Here is an alternative way.

    (Edit: I always forget that beehaw will convert my ampersand to &. Have this in mind if you read the below code.)

    bash -c 'cd "${HOME}/.local/bin"; path="$(find . -maxdepth 1 -type f -executable -printf "%f\n" | fzf --preview "cat {}")" && "${path}"'
    

    below same command in a bit more readable standalone script:

    #!/usr/bin/env bash
    cd "${HOME}/.local/bin" || exit 1
    path="$( \
        find . -maxdepth 1 -type f -executable -printf "%f\n" | \
        fzf --preview "cat {}" \
    )" && "${path}"
    

    The biggest problem with fzf is, that scripts that need an argument are not covered here. One could either use the input string from fzf as arguments or like that, or an optional input after fzf selection.







  • Then why do you bring that up, after the argumentation that people did not want to learn? Look I try to be constructive. There are people who do not want to learn, but saying that all security issues is to attribute to that is wrong. Lot of the best engineers and programmers do their best, long time experts and groups, who still make mistakes.

    What i"m saying is, that your example is not applicable in this discussion, because you are not writing systems programming for operating systems (such as Android or Windows or Linux), which are used by millions of people and ton of hackers try to find vulnerabilities. The best programmers in C and C++ make these mistakes that Rust would prevent (or make it much easier to find and eliminate).

    That’s the point. It’s not about these experts not wanting to learn or not caring. We are not talking about the typical programmer for a website for company x or a fake game programmer for Android.