• 0 Posts
  • 160 Comments
Joined 2 years ago
cake
Cake day: September 15th, 2024

help-circle
  • The bit about “comparability”. Where do you see that they will? (I mean, aside from the original article that claimed it without evidence.)

    A submodule is “just” a pointer to a specific commit in an external repo. It was at one point entirely done via shell scripts, and unless I missed an update is still obnoxiously slow compared to the rest of git.

    I can’t fathom why the SHA-256 support for submodules would do more than just treat the SHA as a foreign key.and go from there. We’d potentially be in trouble if SHA-1 support is being removed, but I don’t see any reason why git would do something so stupid.

    (I honestly can’t fathom why SHA-256 hashed commits couldn’t be the children of SHA-1 commits. A bunch of reasons why you may not WANT to, but that’s a separate concern that seems like it’d be outweighed by comparability.)



  • I read that whole article, and aside from an unsourced statement that GitHub et al will need “new and distinct servers” exactly zero of that seemed to support the thesis that a SHA-256 default was going to be “expensive”.

    Submodules are not the preferred way to incorporate third-party code for any environment I know. And while web-exposed URLs for management tools like Jira or AzureDevOps will need to adapt before the new default can be used, doing so even with a wholesale re-hashing of every commit isn’t technically difficult.

    What would be terrible and dangerous would be if git 3.0 entirely dropped SHA-1 support. But just as you’re free to keep on using “master” instead of “main”, i expect that extant projects will still be supported until a version after every major project has converted to SHA-256 or what have you.




  • Sudden abscorbic rejection is the tolerant reaction to facist sea-lioning.

    There are a handful of other issues where a similarly strong rejection is appropriate, such as “surely a little rape is OK” or “why can’t a grandfather fuck a 12 year old”.

    It may seem extreme to respond with such vitriol just to a political choice, until you remember that the politocian in question is a rapist and a pedophile.






  • Delete means to remove from database, no recovery

    From a technical standpoint, this was not at all the case historically. By the time we moved from floppy disks to standard UNIX commands the presumption was that your data would be backed up and thus recoverable, and early RDBMs treated the equivalent to a DELETE SQL command the same way FAT did.

    Nowhere in the English language semantically will you find that “delete” implies that you can recover it.

    https://english.stackexchange.com/questions/518243/origin-of-the-word-delete

    Delete as originally brought into English from Latin referred to smuding out in your wax slate, and later blotting out your writing to hide a mistake. In both ancient usages the mistake was potentially recoverable, a non-contradicting inference that continued on to the computer age.

    Note that we don’t generally say “delete” to mean “remove unrecoverably” in other contexts, either. The rules for handling classified material do not merely say “delete”, but always compound it with qualifiers or expansive instructions such as “delete unrecoverably” or “delete files and backups”.

    As far as the hardware you are executing “delete” should follow that command.

    Final point: the actions of a user with regard to their posts on Lemmy are not hardware commands. They are pure software concepts that interact with a distributed and abstracted system that is several steps removed from such.