Live data from Hacker News

What is in that .git directory?

blog.meain.io

41–47 of 47 posts

Re: What is in that .git directory?

#41

I really don't like the "f" in that font. Very jarring.

Yup. As far as modern letterform conventions go, it's just plain wrong.

It's incredibly distracting and I can't imagine why anyone would ever choose to use it for code.

If you're doing some kind of cool alternative graphic design poster, then by all means go nuts! That's precisely where it's fun to play with different forms and be as "wrong" as you want.

But for something like code where legibility is the primary concern, it's a very unfortunate choice.

Our brain recognizes words not just by individual letters but by the shape of the entire word, and inserting a descender where we're not accustomed to one, breaks our word-level recognition. It's not a neutral, aesthetic choice -- it literally makes it objectively harder to read, in a modern context.

Re: What is in that .git directory?

#42

By random chance I ended up in the git internals doc^1 today, also lovely refered to as plumbing and porcelain. It's a fantastic read, very well explained. I wish all doc was written with such explicit care to be understood. It reads like a good friend is trying to explain you something. What got me into that was a 51Gb ".pack" file that I wanted to understand. If you wonder about that, they're pack files, and what t…

Do you have large image files, videos or other file formats that aren't plain text only that might cause git to store weird diffs/duplicates when you change them?

Re: What is in that .git directory?

#43

There is a trend to all these hidden dot folders and files from apps. VS code is another example. Personally I do not like this. Couldn't there be another way for this config files?

If you don't like .git directories you can create a bare repo. That puts all of git's internal stuff at top level and makes it visible. But then you have to set up your working directory somewhere else.

https://stackoverflow.com/questions/7632454/how-do-you-use-g...

Re: What is in that .git directory?

#44

Earlier quoted context omitted.

Nice! I didnt know about this. Feel like its in an odd place. This is the first ive ever heard of this, so must be that not many use it (or admit to using it)

A more suggestive name like “private-ignore” would help.

While I always hate the cluttering of "top" directories, id think something more like `.gitignore.local` at the top level would be much better than where its hidden

Re: What is in that .git directory?

#45

By random chance I ended up in the git internals doc^1 today, also lovely refered to as plumbing and porcelain. It's a fantastic read, very well explained. I wish all doc was written with such explicit care to be understood. It reads like a good friend is trying to explain you something. What got me into that was a 51Gb ".pack" file that I wanted to understand. If you wonder about that, they're pack files, and what t…

> It reads like a good friend is trying to explain you something.

As the author of this document, I wanted to let you know that it made me happy to read this. Thank you for the kind words. :)

Re: What is in that .git directory?

#46

Earlier quoted context omitted.

A more suggestive name like “private-ignore” would help.

While I always hate the cluttering of "top" directories, id think something more like `.gitignore.local` at the top level would be much better than where its hidden

Yeah absolutely. When it is buried inside the repository itself most people won't find out about it, even with a good name.

Re: What is in that .git directory?

#47

By random chance I ended up in the git internals doc^1 today, also lovely refered to as plumbing and porcelain. It's a fantastic read, very well explained. I wish all doc was written with such explicit care to be understood. It reads like a good friend is trying to explain you something. What got me into that was a 51Gb ".pack" file that I wanted to understand. If you wonder about that, they're pack files, and what t…

> I wish all doc was written with such explicit care to be understood. It reads like a good friend is trying to explain you something.

I think this is due to git's early history and the reputation it had for being incomprehensible and difficult to use. Lots and lots of work has been done by many people to make it more developer/user friendly. It really helped that its feature-set made all of this work appealing. e.g. learning git-blame and git-bisect made me want to use git for all of my projects, even if it takes time to explain how to use it.

Post reply on HN