Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bit – A modernized Git CLI written in Go

github.com

Post reply on HN
Print view View original

41–50 of 132 posts

Re: Bit – A modernized Git CLI written in Go

#41

Post by [deleted] »

saurik wrote: post #34
stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

I agree: to me this is like a car giving you driving directions by saying "turn north" instead of "turn left"; there are people who legitimately find either way to be easier, and if you give them the wrong way they are just going to have to convert it... I find absolutely dates and times to be super intuitive, and I have most of my life laid out in my head with absolute dates, and find relative dates and times to be…

[deleted]

Re: Bit – A modernized Git CLI written in Go

#42

Post by imhoguy »

stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

Honestly, when I enter a project page I glance these to quickly evaluate how active the development is. E.g. for Ruby library when I see "9 years ago" everywhere then likely the code needs some work to get it working with the latest Ruby version. But when there is just one "2 months ago" on `lib` directory it tells me somebody came back here to maintain the things. I am not sure if list of accurately formated timestamps would be quicker to scan.

Regarding unmaintained projects, usually my next step is to check recent PRs list or Network Graph page to see if there is some more active fork.

Re: Bit – A modernized Git CLI written in Go

#43

Post by bartread »

stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

Agree. Timezone issues aside (which this does simplify), I'd like to see both "N hours ago", plus the actual date and time it happened (in my local timezone).

With hours it's not so bad, but gets worse with longer time periods. I find it incredibly aggravating when services say "N days ago", or "N weeks ago", because this simply serves to obscure when an event actually occurred. Just give me the damn date and time in my local timezone!

Re: Bit – A modernized Git CLI written in Go

#44

Post by mschrage »

domlebo70 wrote: post #36

The autocomplete popups are really cool. Does anyone know if there's a generic way to provide this for all tools with CLI's with help text? What about being able to parse a Programmable Completion file. I don't know much about this stuff, but the thought popped into my mind.

This is something I’ve been working on!

Autocomplete popovers / CLUIs seem like a really natural way to enhance discoverability in the terminal.

https://github.com/withfig/completion-specs

Re: Bit – A modernized Git CLI written in Go

#45

Post by pjmlp »

justincormack wrote: post #39
formerly_proven wrote: post #32

Earlier quoted context omitted.

Why would a different CLI (presumably still using libgit2) improve security? Especially if it's installed like this: curl -sf https://gobinaries.com/chriswalz/bit | sh;

It doesn’t use libgit2 it shells out to git. So it doesn’t improve security.

It still does, by adding yet another layer, written in a memory safe language.

Just like a castle with a water pit can still be conquered, but it takes a bit more effort for achieving it.

Re: Bit – A modernized Git CLI written in Go

#46

Post by remolueoend »

domlebo70 wrote: post #36

The autocomplete popups are really cool. Does anyone know if there's a generic way to provide this for all tools with CLI's with help text? What about being able to parse a Programmable Completion file. I don't know much about this stuff, but the thought popped into my mind.

There are some default completion replacements out there, such as fzf-tab for zsh: https://github.com/Aloxaf/fzf-tab

Re: Bit – A modernized Git CLI written in Go

#47

Post by stinos »

oakmad wrote: post #38
stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

You’ve never worked across time zones have you? I find it’s a lot easier to say “that commit from 2 hours ago” than do the mental math during a code review or debug session. However I do think it should be opt in as I understand your POV and in my experience it’s never an issue until it’s a big one. In our ui we show ago, local and point of origin for all time zones we deal with in a popover.

You’ve never worked across time zones have you?

Actually I have, and then we all use GMT when communicating timestamps. But it's like another commenter mentions: yes, 'that commit from 2 hours ago' is still doable (though if it matters we communicate SHAs), but when it goes to 'a day ago' it doesn't really work out anymore.

Re: Bit – A modernized Git CLI written in Go

#48

Post by OJFord »

I really liked the look of this, until I got to `save`/`sync` in the readme...

That's not how I want to work, and it's not how I want other people to work in a repository I'm using. I know 'I don't have to use them then I can just use the git subcommands', but that's not the point, it's a big signal ('90% of the time the above commands will have you covered.') about the motivation/angle/philosophy of the project that doesn't match my attitude towards git at all.

Which is a shame, because the autocomplete stuff looks really nice.

Re: Bit – A modernized Git CLI written in Go

#49

Post by brigandish »

paulsmal wrote: post #24
brigandish wrote: post #12

The autocomplete/help popups didn't happen for me, is there something I need to do? I'm using zsh on a Mac, perhaps it assumes bash. Aside from that, I'm going to persist with this for a little while and see how it goes, the git interface does bother me.

try using bash, maybe zsh autocompletion interfering with it?

Same outcome, but using enter works. It's possible I've done something to both bash and zsh, I like to tinker :)

Re: Bit – A modernized Git CLI written in Go

#50

Post by qw »

oakmad wrote: post #38
stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

You’ve never worked across time zones have you? I find it’s a lot easier to say “that commit from 2 hours ago” than do the mental math during a code review or debug session. However I do think it should be opt in as I understand your POV and in my experience it’s never an issue until it’s a big one. In our ui we show ago, local and point of origin for all time zones we deal with in a popover.

The time displayed by git or other programs could simply be converted to the timezone you feel comfortable with?
Post reply on HN