ob

8 ms·

31.
by ob 15y ago
If you never merge, but only use "git pull --rebase", you will have a straight line history and thus lose all of the "distributed" nature of the history. That's fine, but limiting. Any system that allows distributed development has to dea
32.
by ob 15y ago
Matt's point is that they've chosen a system that makes it really hard to get that last 10%. "We have tried to draw spirals using cartesian coordinates, what we have gets us 90% there, but there are infinities and edge cases involved in get
33.
by ob 15y ago
There are two things most commenters in this thread have missed: 1) The article talks about auto-merges. If the code is "too close" by some definition of close, you get a conflict that needs to be manually merged. The article does NOT talk
34.
by ob 15y ago
Then you're no better off using a DVCS than you are using diff and patch. Not even git (which is as dumb as it gets) is _that_ dumb.
35.
by ob 15y ago
Of course Git uses history. It doesn't _have_ to, but it does. As a matter of fact, as soon as you use diff3, you are using history (that's where the GCA comes from).
36.
by ob 15y ago
No, you are totally wrong. Did you even try this in Git? Any sensible VC system will give you a conflict here. The article discusses auto-merge behaviour. You ABSOLUTELY can get auto-merge to work 100% of the time. When it doesn't you get a
37.
by ob 15y ago
I've tried a technique like this, it works wonders if you are near a computer and can copy/paste. As soon as you have some flash login box where you can't paste or you try to log in from your iPhone it becomes extremely painful. Better to u
38.
by ob 16y ago
Note however that the "unusual toolkit" and "being super-smart" are not mutually exclusive. He probably had both.
39.
by ob 16y ago
I've had similar stuff happen to me. One trick that has helped to get me out of the rut is to go back to the basics. When I'm stuck I would find a textbook problem, from the very simple (reverse this array, etc) to the more complex (impleme
40.
by ob 16y ago
Gruber regularly deals with critics that will write basically anything, even criticizing products that have not been announce yet. Hank Williams' statement: Essentially, anyone who has criticized the iPhone, or presumably Apple is j
41.
by ob 17y ago
That doesn't make any sense. You're assuming that they have 10 times the content, need 10 times the processing power, and that they derive no advantages to caching (from 48 GB RAM to 480 GB RAM). That is not how capacity planning works at a
42.
by ob 17y ago
I've heard it told the other way around. That Larry had worked on Teamware at Sun and he showed Linus how distributed SCM worked. Linus said "if you build that, I will use it" and Larry built it.
43.
by ob 17y ago
I think it goes very well with this article about how to get big projects done: http://www.spring.org.uk/2008/11/getting-big-projects-done-b...