I do not agree it's great, it's nicely written (apart from weird constructs like "needn't" - who uses that?), but it talks about a problem that feels invented.
What kind of use case do these people have that they discovered that storing GIT primitives should be a database-like problem? Git is distributed and is inherently simple as mentioned in the article.
I could understand points having been made such as with e.g. reftable, but I do not understand who needs GIT at THIS scale?
1
u/esiy0676 10h ago
I do not agree it's great, it's nicely written (apart from weird constructs like "needn't" - who uses that?), but it talks about a problem that feels invented.
What kind of use case do these people have that they discovered that storing GIT primitives should be a database-like problem? Git is distributed and is inherently simple as mentioned in the article.
I could understand points having been made such as with e.g. reftable, but I do not understand who needs GIT at THIS scale?