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

91–100 of 132 posts

Re: Bit – A modernized Git CLI written in Go

#91

Post by ljm »

user5994461 wrote: post #88
bitdivision wrote: post #86

Earlier quoted context omitted.

I don't understand why his statement was wrong. GMT does not change according to daylight savings time as far as I know?

GMT = Greenwich Meridian Time The time at the greenwich meridian = not GMT See the problem here? I know it sounds like a bad pun but it's a real problem that every developer in the UK struggled with. To make thing worse, Greenwich the location is right next to the financial district of London where thousands of developers make financial software that are one hour wrong.

I have to say that the level of confidence you have while being so misinformed is rather comical.

I lived in Greenwich, I don't remember entering a new space-time continuum when getting off the DLR at Cutty Sark. You know, compasses spinning eratically, GPS going haywire, cuckoo clocks spinning out of control, because the bubble around the Greenwich Meridian transcends the mortal plane.

GMT is the timezone we have between the end of October and the end of March. Between the end of March and the end of October, it shifts an hour ahead and becomes BST, or GMT/UTC+1.

Greenwich is also South East London, not East London, as it is south of the Thames.

Re: Bit – A modernized Git CLI written in Go

#92

Post by the_greyd »

Cool project! Love the autocomplete feature. Just my 2 cents about the custom commands, hiding the complexity of git commands is not something I'd like personally (not accounting for alias, aliases are cool). In most cases you'd much rather know which exact git command did/does what to debug/fix, so it's better to invest that time learning early on..

Re: Bit – A modernized Git CLI written in Go

#93

Post by user5994461 »

ljm wrote: post #91
user5994461 wrote: post #88

Earlier quoted context omitted.

GMT = Greenwich Meridian Time The time at the greenwich meridian = not GMT See the problem here? I know it sounds like a bad pun but it's a real problem that every developer in the UK struggled with. To make thing worse, Greenwich the location is right next to the financial district of London where thousands of developers make financial software that are one hour wrong.

I have to say that the level of confidence you have while being so misinformed is rather comical. I lived in Greenwich, I don't remember entering a new space-time continuum when getting off the DLR at Cutty Sark. You know, compasses spinning eratically, GPS going haywire, cuckoo clocks spinning out of control, because the bubble around the Greenwich Meridian transcends the mortal plane. GMT is the timezone we have be…

See, you agree that Greenwich is not under GMT time half of the year.

That's all I am saying. You don't have to resort to name calling.

Re: Bit – A modernized Git CLI written in Go

#95

Post by johnisgood »

imhoguy wrote: post #51
bartread wrote: post #43

Earlier quoted context omitted.

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…

Just hover over "...ago" to get a full date.

HN for one does not support that. :/

Re: Bit – A modernized Git CLI written in Go

#96

Post by johnisgood »

pjmlp wrote: post #45
justincormack wrote: post #39

Earlier quoted context omitted.

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.

I do not care about memory safety only, I would be pissed if it removed my files, for example. :D Security is too broad a term anyways, hence this thread.

Re: Bit – A modernized Git CLI written in Go

#97

Post by IggleSniggle »

imhoguy wrote: post #51
bartread wrote: post #43

Earlier quoted context omitted.

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…

Just hover over "...ago" to get a full date.

I hovered my finger over my tablet screen but nothing happened...

Re: Bit – A modernized Git CLI written in Go

#98

Post by IggleSniggle »

qw wrote: post #50
oakmad wrote: post #38

Earlier quoted context omitted.

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?

This is always such a ball of yarn, but working in a UI where both “absolute” and “relative to the locale of where it happened” are important contextual information, I’ve come to the conclusion that it is actually quite sensible to show both UTC and “local to where the event occurred” time at the same time, every time.

Re: Bit – A modernized Git CLI written in Go

#99

Post by YesThatTom2 »

zaro wrote: post #52
OJFord wrote: post #48

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…

I didn't even get to sync, stopped reading on 'save'.

Thank god you did! I’ve seen too many “make it easier for normal people” projects ruined by trying to appease people that have muscle memory for the old way.

Luckily bit doesn’t do anything that would prevent someone from using git on the same repo. You can co-exist.

I’ll make this prediction based on decades of observations:

1. There will be many projects like this.

2. Eventually one will win out and the others will fade.

3. The winner will be the one that focused on a particular audience AND successfully ignored so-called experts that didn’t see the need for such a project.

4. After one tool wins out, the nay-sayers start to adopt it. Forums like HN get flooded with posts about how “I wish I had tried it sooner”.

But seriously... if you don’t need this kind of tool do the other 98% of the world develop it in peace.

Re: Bit – A modernized Git CLI written in Go

#100

Post by pwinnski »

user5994461 wrote: post #93
ljm wrote: post #91

Earlier quoted context omitted.

I have to say that the level of confidence you have while being so misinformed is rather comical. I lived in Greenwich, I don't remember entering a new space-time continuum when getting off the DLR at Cutty Sark. You know, compasses spinning eratically, GPS going haywire, cuckoo clocks spinning out of control, because the bubble around the Greenwich Meridian transcends the mortal plane. GMT is the timezone we have be…

See, you agree that Greenwich is not under GMT time half of the year. That's all I am saying. You don't have to resort to name calling.

People use GMT because it's an unchanging timezone that's good for world-wide coordination. That it differs by fractional seconds from UTC is irrelevant in most cases.

Nobody but you seems to care about what time it is in Greenwich, including, it seems, other people who've lived in Greenwich. So GMT is fine.

Post reply on HN