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

31–40 of 132 posts

Re: Bit – A modernized Git CLI written in Go

#31

Post by bbbobbb »

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…

It does depend on the context but I mostly use the '2 hours ago notation'.

Sure, if you're looking for a specific timestamp or something that happened 2 months ago, it's not useful and then I switch to the timestamp format.

Majority of the time I care about stuff like what happened today, yesterday just to get the rough idea.

Re: Bit – A modernized Git CLI written in Go

#32

Post by formerly_proven »

pjmlp wrote: post #22
chriswalz wrote: post #2

Git is an awesome tool – so awesome that it has a vast plethora of options and commands to do just about anything. Bit attempts to alleviate some of that pain.

- rant mode on Having used most SCM since RCS days, I get to differ, but since I am left without another option, so just like with C and JavaScript, I suck it up and get the job done by whatever means. - rant mode off Thanks for bringing a bit more of security into the IT world with a Go version though.

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;

Re: Bit – A modernized Git CLI written in Go

#33

Post by nxpnsv »

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…

It's timezone independent... I think it makes sense when hour time scales make sense. For days/week dates work just fine

Re: Bit – A modernized Git CLI written in Go

#34

Post by saurik »

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 infuriating. This is the kind of thing that should just always be a setting.

Re: Bit – A modernized Git CLI written in Go

#35

Post by bamboozled »

formerly_proven wrote: post #32
pjmlp wrote: post #22

Earlier quoted context omitted.

- rant mode on Having used most SCM since RCS days, I get to differ, but since I am left without another option, so just like with C and JavaScript, I suck it up and get the job done by whatever means. - rant mode off Thanks for bringing a bit more of security into the IT world with a Go version though.

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;

Memory safety?

Re: Bit – A modernized Git CLI written in Go

#36

Post by domlebo70 »

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.

Re: Bit – A modernized Git CLI written in Go

#37

Post by grandchild »

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…

It depends whether you want to see age or point in time, a.k.a do you want to compare it to now or to some other specific time.

I personally take longer to parse an ISO formatted timestamp when all I want to know is age (i.e. difference from now). An "x [unit] ago" is much faster for me.

The absolute timestamp is probably more handy when I have other dates to compare it to, because I could line them up vertically and visually diff the digits.

I think it boils down to the fact that I don't have enough working memory to precisely memorize all numbers in a complete timestamp.

Re: Bit – A modernized Git CLI written in Go

#38

Post by oakmad »

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.

Re: Bit – A modernized Git CLI written in Go

#39

Post by justincormack »

formerly_proven wrote: post #32
pjmlp wrote: post #22

Earlier quoted context omitted.

- rant mode on Having used most SCM since RCS days, I get to differ, but since I am left without another option, so just like with C and JavaScript, I suck it up and get the job done by whatever means. - rant mode off Thanks for bringing a bit more of security into the IT world with a Go version though.

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.

Re: Bit – A modernized Git CLI written in Go

#40

Post by szszrk »

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…

It's pain in the ass when you troubleshoot CI problems as well. Was the issue before or after this particular commit? Can't tell, have to check in some other tool.
Post reply on HN