"Jose Armando Garcia" <jsan...@gmail.com> wrote in message news:mailman.635.1320260049.24802.digitalmar...@puremagic.com... > On Wed, Nov 2, 2011 at 8:19 AM, Nick Sabalausky <a@a.a> wrote: >> "Martin Nowak" <d...@dawgfoto.de> wrote in message >> news:mailman.631.1320245247.24802.digitalmar...@puremagic.com... >>> >>>The main point is that git offers a lean mental model. >>> >>>http://book.git-scm.com/1_the_git_object_model.html >>>http://book.git-scm.com/7_the_packfile.html >>> >>>IMHO a complete understanding/control of what is happening scales much >>>better >>>than a fleshed out abstraction that hangs in the air. >> >> OTOH, Git pretty much expects you to understand that under-the-hood stuff >> for any of it to even make sense in the first place ("hard, soft, hard >> and >> soft, index, blah, blah, blah, WTF just undo the gorram commit, >> damnnit!"). >> Hg you can pretty much just pick up and go. > > Thats like trying to successfully write an application that uses an > SQL database application without knowing SQL, database theory, etc. > > Thats like trying to successfully write a networked application > without knowing how IP, TCP, UDP, etc work. > > Thats like trying to successfully write a D program without knowing > how the language works. > > Thats like trying to successfully write a computer software without > knowing how a computer works.
Bad analogies: You shouldn't have to know how IP, TCP, UDP, etc work to successfully *USE* a networked application. Etc... I'm not talking about contributing to the Git/Hg projects themselves, I'm talking about just simply *using* them.