171–180 of 190 posts
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.
This person has gone from having a solid business model (having a job) to having at best a very vague one (“I hope I can focus on adding new premium hosted features for advanced users, and begin to support business usage.”). You know how this sounds like, to me? “I quit my job to play with and walk my dog full time. I am hoping this will give me time to develop skills to eventually earn some money by maybe walking ot…
I'm going to quit my job to relax. And my relax is to build some open source things.
I have some local setup replicating what Atuin does, but I'm realizing I don't use it at all even though I thought it'd be useful, and I don't use my shell history much overall. I have an alias "aled" to edit my aliases quickly, so it's easy for me to add new ones, and that's where I put the commands I want to use regularly, or even the ones I'd like to be able to find if I ever need them again in years. It's easier…
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.
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.
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…
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.
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…
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 history is a substitution for documentation or an audit trail or anything else, but it is a useful tool if it works. Consider a case where you're exploring a new dataset you find online. You download it into a directory, run some commands to transform it, load it into a database etc. You don't know if this will ever be useful. But if it does turn out to be useful, you now have a log of everything you did to get there. Trying to document everything up front would be insane and you'd never get any exploratory work done.
This person has gone from having a solid business model (having a job) to having at best a very vague one (“I hope I can focus on adding new premium hosted features for advanced users, and begin to support business usage.”). You know how this sounds like, to me? “I quit my job to play with and walk my dog full time. I am hoping this will give me time to develop skills to eventually earn some money by maybe walking ot…
Work must always revolve around a pecuniary interest at all times?
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.
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…
While I agree it may not work with everyone's workflow, maybe it could be a powerful change to folks workflow. I'm going to try it out and see for myself!
Earlier quoted context omitted.
How to pay for the open source commons is far from a solved problem, but I'm glad individuals are trying to make it work for themselves anyway. I wish we wouldn't act like producing software and making gobs of money are inextricably linked. Yes, we absolutely need to find a way to fund people who are building critical infrastructure. But sometimes, "I quit my job to work on open source" can be more akin to "I quit my…
>I wish we wouldn't act like producing software and making gobs of money are inextricably linked. Yes, we absolutely need to find a way to fund people who are building critical infrastructure Don't you see the contradiction? Critical infrastructure costs gobs of money. The software has to pay for itself, or it has to survive on crumbs; that's just reality. Software is really, really expensive to create and maintain,…
This is why I like Open Source instead of Free Software. There's no practical difference between the two in terms of licences that are compatible with the two definitions. However, Free Software is an ideology that considers proprietary software to be immoral. Whereas Open Source is a perspective that only cares about the economics of producing software, and is perfectly compatible with capitalism.
https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
Note, there are many scenarios for which I find Amazon getting rich off OSS work is perfectly OK, even advantageous for the contributors, since that kind of freedom and control is the whole point of OSS. It's just that being paid for your OSS contributions is probably not one of those scenarios, and people need to be aware of it, indeed.