3 ms·
> Rust's memory safety and strong type system. As a user, I don't care about Rust's type system, as long as the data I'm storing is valid. This is not a featur
by linkdd 5y ago
> Rust's memory safety and strong type system.
As a user, I don't care about Rust's type system, as long as the data I'm storing is valid. This is not a feature.
"Being written in *" should never be a feature. In fact, it never is and never will be.
> Replacing OIDs with UUIDv4s.
Why?
According to Wikipedia[1]:
UUID - Universally Unique Identifier. These are not
absolutely unique, but statistically unique. [...]
OID - Object Identifier. We tend to want to use these more
often as they are more structured and thus allow for some
additional ways to create Unique Identifiers. The structure
also allows for more accurate TRUE/FALSE comparisons. And
when it comes to diagnosing problems, their structure can
also come in handy.
So this decision seems a bit weird to me. Unless I'm missing something?
[1] - https://wiki.ihe.net/index.php/Creating_Unique_IDs_-_OID_and_UUID
- wtetzner 5y ago> As a user, I don't care about Rust's type system, as long as the data I'm storing is valid. This is not a feature. It may not be a feature to a user, but it could be considered a feature to contributors.