• 0 Posts
  • 54 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle
  • Haha, I guess many dog owners just can’t see it how it is; probably an addiction to the lopsided unconditional “love”. I used to comment something similar back in Reddit, just to see the flood of downvotes and outraged dog owners.

    Same reaction to supporting the idea that some breeds are generally more dangerous and/or more aggressive. “Oh, my MY pitbull is a sweetie!!” (adding this here just to test :D )





  • Dogs were hardwired by selective breeding to worship their owners. Not long ago they at least were loyal companions. You got one off the streets, fed it leftovers, washed it with a hose, it lived in the yard, and it was VERY happy and proud of doing its job. Some breeds now were bred into painful disabling deformities just to look “cute”, and they became hysterical neurotic yapping fashion accessories. Useless high maintenance toys people store in small cages (“oh, but my child loves his cage”) when they don’t need hardwired unconditional lopsided “love” to feed their narcissism.


  • Spaces are not the end of the world, but very annoying:

    On a bash command line, they make it harder to handle a list of files returned by a command as argument to another.

    On the command line (lin or win), they require escaping or quoting when used as arguments or script/executable names.

    On many programs, if you cut&paste the complete path to the file (for example in a network drive), you can click on the path and it will access the file, but spaces in filenames or directories breaks that (and it’s not bad programming, the program simply can’t guess where the link ends).

    When you mention the name of the file in a documentation or message, it may lead to misintepretation, and it’s just fugly:

    “You can find more information in the attached document file.pdf”.

    What is the name of the file? it can be “the attached document file.pdf”, “attached document file.pdf”, “document file.pdf” or “file.pdf”.

    Also when mentioned in a text, the file name may end up split in separated lines or even pages, and will more likely be subject to autocorrect.

    When copying the file name in a text, in most environments you can double-click to select the whole name, but it doesn’t work if it has spaces.

    Now, if you never ever type or copy/paste a file name, and only ever access files through a graphical interface, then it makes no difference.

    But then you start getting to comfy and if anything goes, why not non-ascii chars too? And that opens a different can of troubles.



  • if I’m not going to do it, someone else will happily do it

    This “justification” works for everything, from parking on the disability park spot to genocide.

    Having said that, my first task at a new job in '94 was “you see these three workers counting, stacking and feeding the product into the packing machine? You’ll design a stacker to replace them”. “ah, three workers three shifts, so you’re saying my first task is to make 9 people jobless?”. “yup, but we’ll replicate it to other lines, so…”.

    Someone would do it anyway.












  • When vlemmy.net died permanently, it took my only login into lemmy, and my list of subbed communities.

    Having learned the hard way about the volatility of theninstances, I don’t want to have to go through the login creation and resubbing communities everytime this happens, and I like my login (it’s the same for everything sinxe the 90s), so I created “fallback” logins in other instances (sh.itjust.works, feddit.nl, lemmy.world), as backups, and also to “reserve” my login name.

    I have all of them configured in Jerboa, when any of them is down, I just switch. Interestingly, the one that I’ve never seen down is the smallest, feddit.nl.