News for hackers. Stuff that matters.
Re:A Git catastrophe cleaned up by jack9 on Wednesday December 21, 2016 @01:32PM (#13231428)
> DVCS is fundamentally a simple concept

It is, if you're going to simplify it so far as to avoid the problemspace by nomenclature. It's just transforming nonlinear events into a linear sequence! I guess multithreading is also a fundamentally simple concept, in that vein.

Re:A Git catastrophe cleaned up by ap22213 on Wednesday December 21, 2016 @06:24PM (#13233541)
I don't mean to minimize the effort that went into Git. But, have you ever looked at the source code? It's like someone dropped the kitchen sink into the global namespace. The whole code base is full of premature optimizations. And, there's a lot of low-level infrastructure code coupled in with the core logic.

I know abstraction is out of fashion these days, but it may have helped a little in organizing things. Abstraction, when used properly, can almost always make complicated things more simple.

Basically, if a regular person had created Git, and not a demigod, would it even have become what it is?

Re:A Git catastrophe cleaned up by Hello71 on Wednesday December 21, 2016 @06:42PM (#13233619)
we would have hg.

as a user, I'll take premature optimizations over slow as balls any day.

Re:A Git catastrophe cleaned up by ap22213 on Wednesday December 21, 2016 @06:51PM (#13233666)
The problem with premature optimization is that most of it has little effect on overall performance. Software performance almost always follows a Pareto distribution.

But, wtf do I know, I'm just some regular person.

Re:A Git catastrophe cleaned up by SOLAR_FIELDS on Wednesday December 21, 2016 @08:25PM (#13234067)
It's hard to tell - did the premature optimizations allow Git to extend way beyond the initial release with little worries of performance? It's not something that's easily quantifiable.