2 ms·
Would you want to see code you depend upon arbitrarily change, content you linked to become invalid through a 404, etc.? I didn't say "mutability needs to be c
by hobofan 7y ago
Would you want to see code you depend upon arbitrarily change, content you linked to become invalid through a 404, etc.?
I didn't say "mutability needs to be completely eradicated". It's mutable-only (what we currently have) vs mutable-by-default vs immutable-by-default. Each of them has their own trade-offs.
- pfraze 7y agoFWIW Dat is going to add "strong links" in the near future, which are links that include a version & content-hash for pinning to a specific version.
- hobofan 7y agoThe end of my first comment explains why I don't think that's good enough: > Yes, I know that there are some fringe efforts to enable more immutability with "hypercore-strong-link" etc., but they look like an afterthought, that won't be supported by most of the Dat ecosystem if it finds major adoption.
- pfraze 7y agoWhy do you figure? If it's part of the protocol, wouldn't clients use it?
- hobofan 7y agoSame reasons that you can't use many edge cases of email addresses (or even common "+"-addresses) with a lot of websites, even tough they are valid according to the spec: - Most developers don't read spec and add e.g. validations in end-user applications where they think they are being clever - Multiple fully fledged implementations of the core protocols are usually hard to come by. This means that rarely used features are that are not supported in all implementations won't be used and so organically wither