Programming

28764 readers

452 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Git 3.0's upcoming SHA-256 default will be a costly mistake (blog.gitbutler.com)

submitted 4 days ago by pylapp@programming.dev to c/programming@programming.dev

25 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] chris@l.roofo.cc 1 points 3 days ago

Yes I read the article. I don't agree with all the conclusions.

Now is the best time to change to a new algo. SHA1 is not completely broken yet. It most probably will be at some point.

Also AFAIK they will have compatibility tools for SHA1 repos in git. I don't see the big deal with the path they chose.

We will probably nor agree on that one. I think the hashes are important and that they are mutable right new with effort and later without. It's okay that we don't agree though. The git maintainers have made their decision anyways.