Still hatin' on git: now with added Actual Reasons

Re:Still hatin' on git: now with added Actual Reasons by pyre on Thursday May 13, 2010 @04:56PM (#1345644)

When you 'checkout' something from the library, you are not 'having a peek at it' in the 'Hey! Come check this out!' usage of the word. Words can have multiple meanings depending on context. 'git checkout' has no context, so you can't just assume what the author meant when the command was named as such.

[ Parent | on HN ]

Re:Still hatin' on git: now with added Actual Reasons by phaylon on Friday May 14, 2010 @08:53AM (#1347194)

I know, and having multiple meanings for a single word that's used as a technical command without visible content is not a good idea. That's what I'm saying

[ Parent | on HN ]

Re:Still hatin' on git: now with added Actual Reasons by pyre on Friday May 14, 2010 @03:07PM (#1348246)

> without visible content

There is a manual... You don't blame a drill press company just because someone thought it was a good idea to use their drill press to pierce their nose, do you? What's the point of providing people with documentation, if you are going to rail on the product for not being 'so easy' that people don't need to read the documentation?

[ Parent | on HN ]

Re:Still hatin' on git: now with added Actual Reasons by phaylon on Sunday May 16, 2010 @06:20PM (#1352915)

This is about catching mistakes. No manual will help you there. Documentation doesn't even come into the mix.

[ Parent | on HN ]