4 ms·
I didn't recognize the author, but came here to say the same thing: where are the ideas on how these improvements would be implemented? Without making an attem
by enasterosophes 4y ago
I didn't recognize the author, but came here to say the same thing: where are the ideas on how these improvements would be implemented?
Without making an attempt at implementation, you (the generic you, not the person I'm replying to) have no idea what the real issues are. Even failed or partial implementations are more instructive than armchair criticisms, or thought experiments where you can just handwave away all the competing constraints that need to be considered, whether in Git or in any erstwhile successor.
- niek_pas 4y agoFair, although I think we need to understand git’s shortcomings to understand what product needs to be built next. I’d argue that’s what this author is doing.
- hackernewds 4y agoThe skills necessary to solve a problem, are also the skills necessary to realize there is one in the first place.
- zaphirplane 4y agoI’ve got one, poverty I realise the problem no idea and I bet no one here has an idea how to fix it without breaking a lot of other things The list goes on
- Too 4y agoOf course concrete ideas are better. But even armchair criticisms can be important (or at least interesting), to open up the discussion. While git is good and powerful in many ways, git frankly has many deficiencies, yet everybody treats it as the holy grail of version control. Just because Linux uses it, GitHub exists or something else, I don’t know. The author lists many valid points that are not all sci-fi and that would multiply the usefulness of the vcs sevenfold. Someone has to point out the elephant in the room. It could spark the idea for someone to invest in something new and better or for someone to contribute improvements into git.