Earlier quoted context omitted.
Git exists, because Bitkeeper were being A holes. [1] A developer needed some metrics on the Bitkeeper repository that Linux used. Remember this is a proprietary and commercial product that granted a handful of licenses to the Linux community as a token of support. So when Andrew Tridgell reversed engineered the format that Bitkeeper used, they threatened to sue him under the DMCA. This caused a firestorm, some defen…
Events like this, even in the small, keep me from outright dismissing "hero based" (whatever it's called) theories of explaining history. Coincidences, accidents, grudges, misunderstandings coupled with path dependencies.
Dolt is Git for data
191–196 of 196 posts
Re: Dolt is Git for data
#192Earlier quoted context omitted.
Hi Sid, if you are curious about how it works internally, you can read some of the old docs from Noms here (Dolt uses a fork of Noms as its internal storage layer). https://github.com/attic-labs/noms/blob/master/doc/intro.md To answer your question, it is pretty easy to make Noms (or Dolt) into a CRDT by defining a merge function that is deterministic. We experimented with this in Noms but the result wasn't that sati…
Thanks for your answer!
The article was published with https://www.dolthub.com/blog/2020-03-30-dolt-use-cases/ and here is the short HN thread https://news.ycombinator.com/item?id=22751209
Re: Dolt is Git for data
#193Delphix has provided for years branching and test database functionality for real databases people actually use like Oracle.
Re: Dolt is Git for data
#194Earlier quoted context omitted.
How does Pachyderm deal with GDPR requests. Is it possible to remove a file not just from the present but also from the history? It would be no use to delete a file on GPDR request from the current version while still keeping it around in past commits.
Request to purge data are one aspect of the GDPR that Pachyderm makes trickier. It makes it easier to remove a piece of data and recompute all of your models without it, because it can deduplicate the computation. But to truly purge a piece of data deduplication becomes a hinderance, because the data can be reference by previous commits, and even by other user's data. You can delete a piece of data and have it not be…
But then wouldn't the storage and distribution of keys become a similar problem to the original one? If the keys get distributed, then it's hard to really remove them.
Re: Dolt is Git for data
#195Earlier quoted context omitted.
Request to purge data are one aspect of the GDPR that Pachyderm makes trickier. It makes it easier to remove a piece of data and recompute all of your models without it, because it can deduplicate the computation. But to truly purge a piece of data deduplication becomes a hinderance, because the data can be reference by previous commits, and even by other user's data. You can delete a piece of data and have it not be…
But then wouldn't the storage and distribution of keys become a similar problem to the original one? If the keys get distributed, then it's hard to really remove them.
Yes, all the keys do is scale the problem down. In general this is a very tough problem, everything else in the system is designed to avoid data loss, that's the biggest scariest failure case. But then when you want to lose data all the measures in the system to prevent data loss prevent that from happening.
Re: Dolt is Git for data
#196Earlier quoted context omitted.
> so how could Git have succeeded because of Linus, other than Linus originating the genius design of it? Perhaps that is exactly the point. There was a fair amount of hype and press coverage over Git when it was first unveiled. And it was because Linus wrote it, and wrote it in an unexpectedly short time. And it was on the coattails of the whole Bitkeeper saga.
Similar to how, say, Go and Rust became popular while nim and D have largely remained niche products PS: Hi, Steve!
Hi Tyler! :)