<story><title>I quit my job to work full time on my open source project</title><url>https://ellie.wtf/posts/i-quit-my-job-to-work-full-time-on-my-open-source-project</url></story><parent_chain><item><author>Brian_K_White</author><text>You don&amp;#x27;t need any of it.&lt;p&gt;History is useful enough to exist as a feature, I up-arrow routinely, but it doesn&amp;#x27;t actually matter when it doesn&amp;#x27;t exist.&lt;p&gt;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:&lt;p&gt;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 water and so you decide that your normal towels aren&amp;#x27;t good enough and so you get more &amp;amp; better towels, or even put a sump pump in the corner to keep pumping all this water away.&lt;p&gt;I&amp;#x27;ve written a lot of complicated pipelines and awk and sed etc, but they were either one-offs that are of hardly any value later, or I made a script, and the few things that are neither of those, are so few they automatically don&amp;#x27;t matter because they are few.&lt;p&gt;It&amp;#x27;s not illegal or immoral, just goofy.</text></item><item><author>lanza</author><text>I love the idea of Atuin but it&amp;#x27;s just way too slow with large history files. I&amp;#x27;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.&lt;p&gt;I don&amp;#x27;t need most of the history, but there&amp;#x27;s 0 chance in hell I&amp;#x27;m auditing that many lines to decide what I need and what I don&amp;#x27;t need.</text></item></parent_chain><comment><author>lanza</author><text>&amp;gt; You don&amp;#x27;t need any of it.
&amp;gt; History is useful enough to exist as a feature, I up-arrow routinely, but it doesn&amp;#x27;t actually matter when it doesn&amp;#x27;t exist.&lt;p&gt;That&amp;#x27;s absurdly naive to think the simplistic constraints of your own workflow is a general rule.</text></comment>
<story><title>I quit my job to work full time on my open source project</title><url>https://ellie.wtf/posts/i-quit-my-job-to-work-full-time-on-my-open-source-project</url></story><parent_chain><item><author>Brian_K_White</author><text>You don&amp;#x27;t need any of it.&lt;p&gt;History is useful enough to exist as a feature, I up-arrow routinely, but it doesn&amp;#x27;t actually matter when it doesn&amp;#x27;t exist.&lt;p&gt;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:&lt;p&gt;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 water and so you decide that your normal towels aren&amp;#x27;t good enough and so you get more &amp;amp; better towels, or even put a sump pump in the corner to keep pumping all this water away.&lt;p&gt;I&amp;#x27;ve written a lot of complicated pipelines and awk and sed etc, but they were either one-offs that are of hardly any value later, or I made a script, and the few things that are neither of those, are so few they automatically don&amp;#x27;t matter because they are few.&lt;p&gt;It&amp;#x27;s not illegal or immoral, just goofy.</text></item><item><author>lanza</author><text>I love the idea of Atuin but it&amp;#x27;s just way too slow with large history files. I&amp;#x27;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.&lt;p&gt;I don&amp;#x27;t need most of the history, but there&amp;#x27;s 0 chance in hell I&amp;#x27;m auditing that many lines to decide what I need and what I don&amp;#x27;t need.</text></item></parent_chain><comment><author>euos</author><text>I use those ! Bash history features all the time. I.e. !?some_test to just rerun a test case I ran several months ago. I don’t need to sync histories between PCs (they are different enough) but history is important.</text></comment>