3 ms·
Sorry to go off topic but one of my pet peeves is things self-described as "simple". What does that even mean? Is it simple to use? Is the implementation simple
by choward 7y ago
Sorry to go off topic but one of my pet peeves is things self-described as "simple". What does that even mean? Is it simple to use? Is the implementation simple? Is it lacking features that I'm going to need and regret it later? I think it's most people's goal to make their software user friendly, but let us users decide that.
Also, when coming across a project where other solutions exist, it's nice seeing an explanation of why you created your solution instead using prior art. What inspired that project? That really helps me when trying to decide on something. Some comparisons would also be nice.
I have been considering using a shell testing framework for a while (at the moment I just write tests that shell out). But when I see project this new when others have existed for a while I'm curious to know why it was created. However I get that because it's new, documentation probably isn't the main concern right now. I don't know if you care about adoption or just wrote this for yourself.
Anyway, looks good. I like the output.
- Karupan 7y agoFair points. “Simple” to me means a familiar API, and the fact that I don’t have to install any dependencies. I either add it as a git sub module or just copy the file into my project. > Also, when coming across a project where other solutions exist, it's nice seeing an explanation of why you created your solution instead using prior art. > However I get that because it's new, documentation probably isn't the main concern right now I’ll be working on both very soon (life gets in the way during weekends!)