Use code HN-1223 at checkout for 90% off ($40 -> $4) a license key through the end of the year. (... Which is a lot closer than it used to be, sigh. Time marches on.)
Show HN: Hucksh – A shell with a very good memory
41–50 of 73 posts
Re: Show HN: Hucksh – A shell with a very good memory
#42Earlier quoted context omitted.
anon25783 seems to be even using BSD for their own projects. Even weirder. Maybe the constant GPL bashing going on is making people misunderstand the crucial difference between "permissive" and free software licenses?
It must be, because I misunderstood that difference myself. I've edited my original comment to reflect this.
Very stand-up of you, kudos!
Re: Show HN: Hucksh – A shell with a very good memory
#43Earlier quoted context omitted.
Thanks! Yeah, I've looked at warp.dev. Funny story: I heard about them from Daniel Martí, aka mvdan, the author of the shell library I'm using. It looks really neat, though I confess I haven't explored it much; dogfooding, don't'cha know. :) I felt a little threatened by them but also weirdly encouraged, since they got $50M in funding. It made me think that hey, somebody thinks a new experimental shell/terminal is a…
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 transition or make people more willing to try it.
#3 - A Windows version is possible. Hucksh has worked there in the past. I think my hurdle there is a build error on Windows in one of the libraries I use. It's probably one of those things that when I actually look closely at it, it'll take an hour to fix, but so far I haven't. More fool I, perhaps.
I also shy away from Windows a tiny bit because it's not my primary platform (macOS), or even my secondary platform (Linux), and the Windows file system structure (with drive letters and so on) requires different code.
On the other hand, a Windows client talking to a Linux server would cover a big use-case.
#4 - If enough people buy it, I could hire other people! ;) I realize that doesn't make it any easier to be an early adopter.
#5 - Would you care to speculate on what you think is a fair price?
Also, based on your other comment, I've added a discount code for 90% off (HN-1223).
Re: Show HN: Hucksh – A shell with a very good memory
#44I highly recommend buying a domain and putting together a professional-looking website, if you intend to sell this software.
Thanks, that's valuable feedback. I do have huckridge.com (a Wordpress site), and some others like huck.sh (which mirrors huckridge.com), but I've been using Notion and Dropbox so as to focus on my product and outsource stuff that wasn't in my core competency, if that's the right word.
You can put a domain in front of a notion workspace. You can either pay something like https://super.so (I've used them) or a few others, also there's a way to front it with your own proxy and maybe a cloudflare method but I forget. I set it up a year ago for my go wiki but I can't even remember the url to show you right now..
It works very well but IIRC there are some quirks but nothing that was game ending. It's still notion and not a website in the end.
Re: Show HN: Hucksh – A shell with a very good memory
#45Earlier quoted context omitted.
anon25783 seems to be even using BSD for their own projects. Even weirder. Maybe the constant GPL bashing going on is making people misunderstand the crucial difference between "permissive" and free software licenses?
It must be, because I misunderstood that difference myself. I've edited my original comment to reflect this.
Thanks!
Re: Show HN: Hucksh – A shell with a very good memory
#46Seems like resh ( https://github.com/curusarn/resh ) plus a directory tab and unlike resh it isn't free. I like the directory history, but that isn't a $40/yr value add over resh for me. There are so many free players in that space (e.g., https://news.ycombinator.com/item?id=31402095 ), $40/yr is probably a hard sell.
Neat tool. Thanks for pointing it out.
Re: Show HN: Hucksh – A shell with a very good memory
#47Here's my 2c. It's unlikely that many users, here or elsewhere, would be comfortable downloading and executing this Hacksh binary from your Dropbox, regardless of its benefits.
Agreed. I would not consider running a closed source shell because it's not auditable.
Re: Show HN: Hucksh – A shell with a very good memory
#48Earlier 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…
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 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.
Re: Show HN: Hucksh – A shell with a very good memory
#49[flagged]
Re: Show HN: Hucksh – A shell with a very good memory
#50Small world : - ) Great work, Larry!