Hi!

My previous/alt account is yetAnotherUser@feddit.de which will be abandoned soon.

  • 2 Posts
  • 550 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2024

help-circle
  • To be honest, DNA is stupid anyway. Worst data format ever invented.

    I mean, a single mutation to get sickle cell anemia? Use fucking error correction codes, dammit! No, having everything twice is not error correction. It’s only error detection and the detected error is just silently ignored and randomly passed on to your offspring.

    Where are the damn backups? 3-2-1 should hold for every data format! How would an offsite backup be designed? I don’t know I’m not evolution incorporated.

    Why are viruses even a thing??? There is no reason EVER to be able to insert new DNA into your genome. Make it read only! With checksums! Why is there no Denuvo DNA-DRM?

    Slightly unrelated but even worse, your immune system is literally only controlled by the equivalent of HTTP. Deactivate completely? Attack everything on sight? No authorization required whatsoever! Just use the public API! Surely nothing could exploit this, right??


    Small Edit as a response to everyone mentioning the need to change for evolution:

    Maybe, just maybe use a test environment? You don’t just push to production the moment you make a change. Move fast and break things my ass. Since women already have the production environment just create a similar structure in men! They already have TESTicles after all.



















  • Nope, the treaty with Ukraine (purposefully) never specified consequences for anyone violating it. It only said (I’m paraphrasing here because I don’t want to look it up) that the signatories will respect Ukraine’s borders.

    The US respects this treaty still and doesn’t recognize Russia’s claims to Ukrainian land. The lack of specified consequences for anyone violating it makes the treaty nearly worthless.

    Signing “I will respect your border” is very much different from “I will defend your borders”.



  • I think it can apply to the most general workflow with branches as well, where branches are used to develop features and then later merge them.

    After all, any new branch is basically a “remaster” until merged back in, which is when the original master becomes the remaster.

    Sure, the analogy isn’t perfect because in music the original master isn’t supposed to change – but the entire purpose of a version control system is to change the “master record”, i.e. what’s deployed to production.