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

Dura is a background process that watches your Git repositories

github.com

Post reply on HN
Print view View original

131–140 of 207 posts

Re: Dura is a background process that watches your Git repositories

#131

Post by bobuk »

tkellogg wrote: post #93
abcd_f wrote: post #53

As a sidenote - “dura” is a common and fairly rude Russian word for “fool” or “imbecile” as applied to women. Perhaps it was intended, but I can’t quite make a connection.

LOL — author here — I definitely didn't intend it that way, but it does kind of jive with "Git's" other meaning. I should have known that all 4-letter words are an insult in some language. I had originally named it "duralumin" after a magical metal in [a novel that I'm reading]( https://www.amazon.com/Well-Ascension-Mistborn-Book/dp/07653... ). I shortened it to "dura" after realizing that I can't even remember the n…

Perhaps you will find it interesting: in Russian, the abbreviated word “dural” is often used for duralumin.

Re: Dura is a background process that watches your Git repositories

#132

Post by avgcorrection »

I don’t understand these backup tools which masquerade as VCS extensions.

I want my VCS commits to be intentional. If they’re not then I’m just using a fancy VCS tool[1] for backup—just set up a _dumb_ backup routine that backs up every X interval and doesn’t have to care about the intentionality behind any changes made (the domain of version control).

And if you get into a situation where you haven’t committed for such a time while that you risk losing “days of work” then… seriously? You might want to get a better Git client where committing isn’t such a pain (IMO the CLI is too much typing for git(1). Magit is great).

And as already mentioned there is the reflog. Which is difficult enough for me to navigate sometimes without some pseudo-backup tool making a mess (on top of _my_ mess…).

[1] Git might be “stupid” but it’s also quite fancy.

Re: Dura is a background process that watches your Git repositories

#133

Post by grishka »

abcd_f wrote: post #53

As a sidenote - “dura” is a common and fairly rude Russian word for “fool” or “imbecile” as applied to women. Perhaps it was intended, but I can’t quite make a connection.

I thought most every Russian was over it after laughing for a bit about the last name of the VKontakte founder, Pavel Durov. At least I didn't make this association immediately when I saw the name of this project.

Re: Dura is a background process that watches your Git repositories

#134

Post by admax88qqq »

encryptluks2 wrote: post #64
admax88qqq wrote: post #21

Cool tool! It's kind of insane to that in 2022 were still dealing with "save early, save often." Our tools are so antiquated. Storage is cheap and computers are fast, every keystroke should be persisted somewhere I can recover from rather than having to manually save and commit works in progress.

You mean like a keylogger that saves everything to some third party?

Yes clearly that's exactly what I meant...

Re: Dura is a background process that watches your Git repositories

#135

Post by stavros »

avgcorrection wrote: post #132

I don’t understand these backup tools which masquerade as VCS extensions. I want my VCS commits to be intentional. If they’re not then I’m just using a fancy VCS tool[1] for backup—just set up a _dumb_ backup routine that backs up every X interval and doesn’t have to care about the intentionality behind any changes made (the domain of version control). And if you get into a situation where you haven’t committed for s…

> If they’re not then I’m just using a fancy VCS tool[1] for backup

Yes you are; what's wrong with that?

Re: Dura is a background process that watches your Git repositories

#136

Post by avgcorrection »

stavros wrote: post #135
avgcorrection wrote: post #132

I don’t understand these backup tools which masquerade as VCS extensions. I want my VCS commits to be intentional. If they’re not then I’m just using a fancy VCS tool[1] for backup—just set up a _dumb_ backup routine that backs up every X interval and doesn’t have to care about the intentionality behind any changes made (the domain of version control). And if you get into a situation where you haven’t committed for s…

> If they’re not then I’m just using a fancy VCS tool[1] for backup Yes you are; what's wrong with that?

Don’t use a fancy tool to implement a simple tool? I’m sure that’s a rule somewhere.

Re: Dura is a background process that watches your Git repositories

#137

Post by gen220 »

mlyle wrote: post #121
gen220 wrote: post #118

Earlier quoted context omitted.

Have you considered using `git commit --amend --no-edit` after making your first commit? It simplifies the unwinding step. This is pretty much my workflow, too. I’ll make some changes, `git commit -m wip`, and then `g can`. When you’re ready to prepare the PR/diff, `reset HEAD^`. Then, a few cycles of `add -p`, `commit -v`. `commit --amend` and `add --patch` are super powers!

If you do this, and find you want to go back to 3-4 commits ago, you need to dig around in the reflog for it.

Ah yeah, that's a totally fair critique. Everything in moderation, I suppose. :)

I must avoid those situations by making a new commit when I anticipate wanting to keep the reference to that point in work accessible.

I do dive into `reflog` maybe once or twice a quarter, but as far as I can remember, I only go there as an immediate reaction to tired-brain mistakes.

Re: Dura is a background process that watches your Git repositories

#138

Post by stavros »

avgcorrection wrote: post #136
stavros wrote: post #135

Earlier quoted context omitted.

> If they’re not then I’m just using a fancy VCS tool[1] for backup Yes you are; what's wrong with that?

Don’t use a fancy tool to implement a simple tool? I’m sure that’s a rule somewhere.

Ah, I'm of the "whatever gets the job done with the least amount of effort" school.

Re: Dura is a background process that watches your Git repositories

#140

Post by xcambar »

encryptluks2 wrote: post #64
admax88qqq wrote: post #21

Cool tool! It's kind of insane to that in 2022 were still dealing with "save early, save often." Our tools are so antiquated. Storage is cheap and computers are fast, every keystroke should be persisted somewhere I can recover from rather than having to manually save and commit works in progress.

You mean like a keylogger that saves everything to some third party?

Stupid business idea: KaaS, keylogger as a service.

"When Ctrl-Z is not enough"

As a french, I can only call this service Patricia. Because Patricia Kaas of course.

Post reply on HN