The Enchilada Programming Language
enchiladacode.nl
enchiladacode.nl
"Every ID of an Enchilada Value is calculated by taking the SHA1 hash of the Value's contents."
The docs suggest that this can be used in a consensus protocol. Many nodes can compute the same result, and quickly test for equality by comparing the ID. Seems nice to have this built-in to the language, but I have to wonder:
a) Why SHA1? Why not a member of the SHA2 family? b) If you're creating a distributed system and want to implement a consensus protocol, a hash ID isn't really sufficient. Who is going to end up using this feature?
So like I said, it's nice to have that hash for every reference, but I wonder if it's worth the storage overhead, and if a developer will use it when he's building his own distributed system anyway.
edit: i am making life too complicated. in short, if it can be calculated quickly, it doesn't have to be stored.
Green Computing: mutating lesser bits generates lesser heat.
This is just silly.Is this not the case?