• 2 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle

  • Regarding my original comment, it’s mainly frustration at the hypocrisy some people have who make every excuse to avoid using someone’s preferred name or pronouns, but then have no problem switching when it’s someone else’s pet

    yeah I got that message. it really shows the hypocrisy, and it makes me wanna scream.

    I wonder if a far away vision of a world where the gender just slowly disappears from the language is really the best. (When i get asked about preferred pronoun, i feel i want to answer “i don’t care and no one should, let’s collectively try to really not give a f*k”.) I feel like in the ideal world all pronouns would just be gender-neutral.

    But language vs. gender is yet another fascinating rabbit hole. My first language is Czech, where basically every word – even unanimous and abstract concepts like “book” have gender, and the grammar is such that effect of word “gender” spreads to other words as inflections and such. Eg. “ona spala” ~ “she slept” vs. “on spal” ~ “he slept” but “ona spal” is an obvious grammar mistake. I wonder if this makes it worse or actually better: while it makes it harder to have a gender-neutral language (the plural trick does not work: “ony spaly” ~ “they (females) slept”, “oni spali” ~ “they (males) slept” … siiigh…), I also feel it could make it less problematic in the sense that the concept of gender in language is not actually tied to identity of a person–it’s just a weird thing present in the language.

    Of course, none of that applies to intentional misgendering, which is just being a huge asshole, with little to no excuse.


    Edit: I missed the last–the most important—part of your post, so I was just replying casually (and nerd sniping myself on the language part).

    Yeah, that’s really disgusting and alarming. I totally believe. I don’t know what to do about it but I do believe and wish nothing but failure to these hateful, cruel people.


  • keeping all these containers up to date

    Updates are a good way to get the security holes fixed, but unfortunately it’s also often how the holes get in in the first place.

    I mean, for most projects it’s kind of sensible to assume that over long time, the code will become rather more secure and less buggy, so eventually the pros/cons might come out in favor of a strategy of updating every time. But it’s good to know that every update is inherently a double edged sword.

    That’s why I like the model that distros like Debian do: they keep the code stable for long time, and only send updates for which a typically independent party (package maintainer) has already decided that a given update indeed is a necessary bugfix, or even specifically a security fix. Similar policy of course could be applied to a Docker container as well, but I don’t know how many projects do this, and it would be a per-project policy, most probably not quite independent.





  • (As a trans person, I have more to say on how easily people pronoun switch for animals but that’s a different topic for another time)

    It is different topic, although I’d love to hear more about that as well. Eg. as a cis male with no transgender friends (well, not that I know of), I find myself thinking ruminating about how impolite/distracting it is to misgender a trans person, provided one can just switch after being corrected and move on… How bad it is to make the (honest) mistake repeatedly? How is it compared to other kinds of faux-pas, like, messing up someone’s name? (Eg. repeatedly calling someone John when they are Joe, or forgetting someone’s occupation. These things do happen to my distractable mind that seems to love lossy data compression.)

    But yeah, it’s a huge, fascinating topic, but a different one from my intention in the OP. :)





  • Don’t want to sound unappreciative, but the apps you refer to (and others in these threads) are not actually CLI’s but TUI’s.

    • CLI (command line interface) is when all interaction actually happens in the command line, ie. command + arguments. CLI’s are much simpler to implement, have little dependencies (pretty much just argument list, two data streams—stdout and stderr–and exit status) and typically one invocation means one independent task. All this makes CLI’s ideal as building building blocks of (semi-)automated workflows, but many CLI’s are also optimized for direct invocation from interactive shell, eg. by adding features such as output coloring, interactive yes/no steps or command completion (although that part is actually driven by the shell, and is quite independent from the execution of the app.)

    • TUI (text user interface, i think) on the other hand, is more like GUI but replicated within the confines of terminal emulator. The interaction heavily depends on terminal features such as moving cursor, resize notifications, etc. Also when TUI is ran, it’s normally used for zero to may tasks: e.g. I could start htop and investigate no process, 1 process or many, before quitting. Unlike CLI’s, TUI’s pretty much make no sense within automation.

    Don’t get me wrong: I love TUI’s (htop is one of my favorite and thanks for recommending nmon, i’ll have a look)–and often prefer them to GUI’s (eg. my text editor is nvim, which is a TUI app!), but in my post I was specifically interested in exploring CLI’s. I would actually love a similar post to mine but focusing explicitly on TUI’s as opposed to CLI’s.

    Sorry for long post – I hope it can kind of serve as explanation for people who are new to this and stumble upon this thread and aren’t quite familiar with the distinction.