This is a compilation of other people's work, but not a business. No one is going to pay for it. Because honesty is more useful and kinder than false praise, sorry and good luck.
Show HN: Hucksh – A shell with a very good memory
61–70 of 73 posts
Re: Show HN: Hucksh – A shell with a very good memory
#62Earlier quoted context omitted.
All of that is fair and I appreciate the comment. Hmm. #1 - I could fork an instance of bash for every command instead of using an internal interpreter. I've shied away from that because it adds an extra layer of complexity, and also on the theory that if you're trying something that hucksh can't run by itself, then you should probably write a stand-alone script anyway. But perhaps as an option it'd help ease the tra…
I don't think there's anything 'unfair' about your price, it's just something I don't want to have to think about yearly for a shell/terminal. One possible workaround is longer term licenses (especially promotionally to early adopters) or a different paid upgrade cadence. I think the fundamental problem to me is similar to that expressed by some of the other commenters - a vague sense of unease with using a closed so…
> a vague sense of unease with using a closed source shell/terminal combo. That's much harder to overcome than paying for a shell/terminal combo. Of course, getting reasonably compensated for open source work is an even trickier problem.
I actually see them compounding... either one alone isn't great, but combine them and you're left with a tool that can be rug-pulled out from under you at any time for any reason. OSS with some monetization gives you a fallback of maintaining it yourself, while commercial non-OSS with a perpetual license at least means you can keep using an old version as long as you can manage. Commercial subscription software is at best ephemeral, and not something I'd invest (time, money, transition effort, etc...) in without a strong fallback option, and even then the benefit offered has to be pretty impressive to overcome those switching costs.
Re: Show HN: Hucksh – A shell with a very good memory
#63This is a compilation of other people's work, but not a business. No one is going to pay for it. Because honesty is more useful and kinder than false praise, sorry and good luck.
It's really not. But if it were, that seems strangely apropos for something calling itself a shell.
mvdan/sh | gio | darktile
Re: Show HN: Hucksh – A shell with a very good memory
#64Earlier quoted context omitted.
somebody thinks a new experimental shell/terminal is a viable commercial product; why not mine? I'm glad people are working on these although as you say yourself, commercial viability is tricky. I like the non-SaaSyness of this but then I'm still left with having to: 1. change my shell 2. change my terminal 3. but not on Windows 4. rely on a single person for bugfixes, security issues, features 5. pay $40/yr for the…
All of that is fair and I appreciate the comment. Hmm. #1 - I could fork an instance of bash for every command instead of using an internal interpreter. I've shied away from that because it adds an extra layer of complexity, and also on the theory that if you're trying something that hucksh can't run by itself, then you should probably write a stand-alone script anyway. But perhaps as an option it'd help ease the tra…
UNC paths are pretty universally supported on modern windows and make things more similar to other platforms. (essentially there are symlinks that make the drive letter look like just an element of the larger path)
Re: Show HN: Hucksh – A shell with a very good memory
#65Earlier quoted context omitted.
somebody thinks a new experimental shell/terminal is a viable commercial product; why not mine? I'm glad people are working on these although as you say yourself, commercial viability is tricky. I like the non-SaaSyness of this but then I'm still left with having to: 1. change my shell 2. change my terminal 3. but not on Windows 4. rely on a single person for bugfixes, security issues, features 5. pay $40/yr for the…
All of that is fair and I appreciate the comment. Hmm. #1 - I could fork an instance of bash for every command instead of using an internal interpreter. I've shied away from that because it adds an extra layer of complexity, and also on the theory that if you're trying something that hucksh can't run by itself, then you should probably write a stand-alone script anyway. But perhaps as an option it'd help ease the tra…
Wait, is it a perpetual license with 1 year of upgrades or is it a license that expires after a year? The latter would make this a no-go for me even if I really like everything else that I'm seeing.
Re: Show HN: Hucksh – A shell with a very good memory
#66Earlier quoted context omitted.
All of that is fair and I appreciate the comment. Hmm. #1 - I could fork an instance of bash for every command instead of using an internal interpreter. I've shied away from that because it adds an extra layer of complexity, and also on the theory that if you're trying something that hucksh can't run by itself, then you should probably write a stand-alone script anyway. But perhaps as an option it'd help ease the tra…
Wait, is it a perpetual license with 1 year of upgrades or is it a license that expires after a year? The latter would make this a no-go for me even if I really like everything else that I'm seeing.
It's the former. A license today will work with today's code forever.
I am not a fan of subscription software, and as much as I would love a recurring income, I don't want to inflict that on my users, if I can avoid it. At the same time, I think it's fair to try to have some way to fund ongoing improvements. It's a delicate balancing act.
Re: Show HN: Hucksh – A shell with a very good memory
#67Earlier quoted context omitted.
Wait, is it a perpetual license with 1 year of upgrades or is it a license that expires after a year? The latter would make this a no-go for me even if I really like everything else that I'm seeing.
It's the former. A license today will work with today's code forever. I am not a fan of subscription software, and as much as I would love a recurring income, I don't want to inflict that on my users, if I can avoid it. At the same time, I think it's fair to try to have some way to fund ongoing improvements. It's a delicate balancing act.
Thanks, I've bought a license now.
Another question: Is there a publicly accessible changelog anywhere? All I see is a Discord link and a newsletter, neither of which I'm interested in using just to see what's changed in a new version. This is the kind of thing that should have its own page on your Notion and be available as a separate text file in the downloaded zip/tgz.
Re: Show HN: Hucksh – A shell with a very good memory
#68Earlier quoted context omitted.
It's the former. A license today will work with today's code forever. I am not a fan of subscription software, and as much as I would love a recurring income, I don't want to inflict that on my users, if I can avoid it. At the same time, I think it's fair to try to have some way to fund ongoing improvements. It's a delicate balancing act.
Thanks, I've bought a license now. Another question: Is there a publicly accessible changelog anywhere? All I see is a Discord link and a newsletter, neither of which I'm interested in using just to see what's changed in a new version. This is the kind of thing that should have its own page on your Notion and be available as a separate text file in the downloaded zip/tgz.
> Thanks, I've bought a license now.
Thanks, that's awesome!
> Is there a publicly accessible changelog anywhere?
Not at present. I'll definitely do one for future releases. I added a reminder in my Makefile, too :) . Thanks for pointing that out.
Re: Show HN: Hucksh – A shell with a very good memory
#69Earlier quoted context omitted.
I don't think there's anything 'unfair' about your price, it's just something I don't want to have to think about yearly for a shell/terminal. One possible workaround is longer term licenses (especially promotionally to early adopters) or a different paid upgrade cadence. I think the fundamental problem to me is similar to that expressed by some of the other commenters - a vague sense of unease with using a closed so…
> a vague sense of unease with using a closed source shell/terminal combo. That's much harder to overcome than paying for a shell/terminal combo. Of course, getting reasonably compensated for open source work is an even trickier problem. I actually see them compounding... either one alone isn't great, but combine them and you're left with a tool that can be rug-pulled out from under you at any time for any reason. OS…
> commercial non-OSS with a perpetual license at least means you can keep using an old version as long as you can manage
That's what hucksh has. Today's license will work with today's code (and code released in the next year) forever. Sorry if that was unclear.
Re: Show HN: Hucksh – A shell with a very good memory
#70This will come in handy in CTF competitions and studies. I often find it difficult to keep track of my work.
Please give the trial version a shot before using it (literally? :) in anger.
It's as good and stable as I can make it at the moment, but I'm not going to pretend it's, you know, absolutely rock solid against anything you can throw at it, and I'd hate for it to crash out from under you in the middle of a competition.
On the plus side, of course, if it does you should be able to just restart it and be on your merry way; that's what I do. :) So maybe it'd be fine.