| 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). |
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.