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

I quit my job to work full time on my open source project

ellie.wtf

Post reply on HN
Print view View original

181–190 of 190 posts

Re: I quit my job to work full time on my open source project

#181

Post by lanza »

ellieh wrote: post #73
lanza wrote: post #17

I love the idea of Atuin but it's just way too slow with large history files. I've synced my history on my own for the past decade and have like 170k lines and the history search the ctrl-r search just crawls. I don't need most of the history, but there's 0 chance in hell I'm auditing that many lines to decide what I need and what I don't need.

> but it's just way too slow with large history files hey! what issues were you having here? slow to open or slow to search? we have a whole bunch of people with way more than 170k lines, so that shouldn't be happening :/

The delay between the physical keystroke and rendered text insertion + search filtering is uncomfortably high. Compared to FZF's instantaneous rendering of the same this is a UX downgrade.

Re: I quit my job to work full time on my open source project

#182

Post by thedragonline »

teddyh wrote: post #178
thedragonline wrote: post #172

Earlier quoted context omitted.

Work must always revolve around a pecuniary interest at all times?

That’s pretty much the definition, yeah. Otherwise it wouldn’t be “work”.

There is work to do in this world that offers no remuneration or very difficult paths to said remuneration.

Re: I quit my job to work full time on my open source project

#183

Post by ukd1 »

kazinator wrote: post #143
ukd1 wrote: post #142

Eventually I suspect someone will abuse this for the free (and encrypted) storage, and then they'll have to fight that battle, which won't be fun, and likely end up charging. Probably should start charging for storage sooner rather than later, and just allow self hosting free.

> which won't be fun Says who?

I mean, obviously it's my opinion - from experience, fighting a that kinda thing is a race, and a pain

Re: I quit my job to work full time on my open source project

#184

Post by tripleo1 »

globular-toast wrote: post #177
Brian_K_White wrote: post #36

Earlier quoted context omitted.

You don't need any of it. History is useful enough to exist as a feature, I up-arrow routinely, but it doesn't actually matter when it doesn't exist. I find the idea of going out of your way to preserve and migrate years of shell history and make it searchable in a db about like: You have a problem that water is flooding your kitchen floor. Normally you deal with a spill with a mop or towels. There is now too much wa…

Good tools change the way you work. Imagine if version control systems were notoriously unreliable and difficult to get working. You'd be saying "nobody needs their entire commit history, if you need a version create a source archive and back it up". But version control systems do work, so we use them, we keep history and we tag releases and don't really need to bother with source archives any more. Nobody is saying…

You remind me of "hey, i just wrote a terminal emulator in JS".

Re: I quit my job to work full time on my open source project

#185

Post by euos »

the_arun wrote: post #71
euos wrote: post #45

Earlier quoted context omitted.

What do you have in the history that’s sensitive? Keys, passwords should not be in shell history anyways (e.g. I delete them from bash history if I enter by mistake)

Shell history is wiped out after user logged out for a reason. More details are here - https://www.securityhq.com/blog/security-101-dont-bash-your-... .

It is not. I definitely use months-old bash history through !? shortcuts.

Re: I quit my job to work full time on my open source project

#186

Post by kazinator »

ukd1 wrote: post #183
kazinator wrote: post #143

Earlier quoted context omitted.

> which won't be fun Says who?

I mean, obviously it's my opinion - from experience, fighting a that kinda thing is a race, and a pain

I'd give users several megabytes of command storage, which features LRU forgetting: least recently used command is erased when a new command is remembered, and the storage is full.

Store shit in that, if that floats your boat.

Rate limiting is obviously applicable here; a normal user doesn't generate large numbers of commands in a short period.

Re: I quit my job to work full time on my open source project

#187

Post by lovestaco »

todd3834 wrote: post #47
motoxpro wrote: post #43

What should I be using shell history for? I've never wanted to go back in my history but obviously people are getting a lot of value from it.

Here are some of my often use cases: Long kunernetes commands, or ssh into an ip you don’t have remembered, curl commands when testing an api. Anything on the CLI that is long and either hard to remember or just annoying to type.

True I use mcfly[1] works pretty smoothly for me

[1] https://github.com/cantino/mcfly

Re: I quit my job to work full time on my open source project

#188

Post by da39a3ee »

latchkey wrote: post #154
da39a3ee wrote: post #6

I use this and it's been fantastic and rock solid; (I've been using Unix shells intensively for 15 years, started using it 1 year ago and never looked back).

The real question here is whether you'd pay for it.

Hm, I just use it on my personal machine. I would pay, but it doesn't look like I'll need to:

> Atuin will continue to be open source and available for free in its current form as a self-hosted tool. By going full-time I hope I can focus on adding new premium hosted features for advanced users, and begin to support business usage.

Re: I quit my job to work full time on my open source project

#189

Post by latchkey »

da39a3ee wrote: post #188
latchkey wrote: post #154

Earlier quoted context omitted.

The real question here is whether you'd pay for it.

Hm, I just use it on my personal machine. I would pay, but it doesn't look like I'll need to: > Atuin will continue to be open source and available for free in its current form as a self-hosted tool. By going full-time I hope I can focus on adding new premium hosted features for advanced users, and begin to support business usage.

That is the rub, for the developer who just quit their job to work on it full time.

The way I see it, they have made the carnal mistake of a lot of entrepreneurs (including myself!) and developed a product, not a company.

Re: I quit my job to work full time on my open source project

#190

Post by Brian_K_White »

lanza wrote: post #60
Brian_K_White wrote: post #36

Earlier quoted context omitted.

You don't need any of it. History is useful enough to exist as a feature, I up-arrow routinely, but it doesn't actually matter when it doesn't exist. I find the idea of going out of your way to preserve and migrate years of shell history and make it searchable in a db about like: You have a problem that water is flooding your kitchen floor. Normally you deal with a spill with a mop or towels. There is now too much wa…

> You don't need any of it. > History is useful enough to exist as a feature, I up-arrow routinely, but it doesn't actually matter when it doesn't exist. That's absurdly naive to think the simplistic constraints of your own workflow is a general rule.

One can only speak meaningfully about their own experience and actual reasoning.

Anything else is bs imagination.

Had I not already allowed that "it's not illegal or immoral" or suggested the feature shouldn't even exist, you might have a point.

Post reply on HN