Name of CLI

[Scimonster]

For v2.1, i added a small CLI script to print data. It's really not compatible with the regular Hebcal, so i don't want to call it hebcal. What should i call it? Right now i have hebcaljs, but does that make it sound like it's for doing something with JavaScript?

[mjradwin]

hebcal-cli?

-michael

On Tue, Mar 11, 2014 at 10:33 AM, Scimonster notifications@github.comwrote:

For v2.1, i added a small CLI script to print data. It's really not compatible with the regular Hebcal, so i don't want to call it hebcal. What should i call it? Right now i have hebcaljs, but does that make it sound like it's for doing something with JavaScript?

Reply to this email directly or view it on GitHubhttps://github.com/hebcal/hebcal-js/issues/3 .

[Scimonster]

I hadn't even considered using a hyphen. :P Hmm, hebcaljs is a drop shorter.

How strongly do you feel about it?

~Sci

On Thu, Mar 13, 2014 at 7:23 PM, Michael J. Radwin <notifications@github.com

wrote:

hebcal-cli?

-michael

On Tue, Mar 11, 2014 at 10:33 AM, Scimonster <notifications@github.com

wrote:

For v2.1, i added a small CLI script to print data. It's really not compatible with the regular Hebcal, so i don't want to call it hebcal. What should i call it? Right now i have hebcaljs, but does that make it sound like it's for doing something with JavaScript?

Reply to this email directly or view it on GitHub< https://github.com/hebcal/hebcal-js/issues/3> .

— Reply to this email directly or view it on GitHubhttps://github.com/hebcal/hebcal-js/issues/3#issuecomment-37560610 .

[mjradwin]

I don't feel strongly at all.

If you have a vision of completely replacing the legacy C application with js, then one option would be to make the CLI app offer a strict superset (e.g. by default 100% compatible with the existing binary). I don't know if it's worth the effort, though - the value in your JS port isn't so much the command-line apps, but more in the JS API itself which can be used in a browser or Node.js...

[Scimonster]

At first i was thinking i might want to replace the C with JS, and hence have it be completely compatible, but then i decided, what's the point? The CLI should basically just be for quickly seeing a date. So, i guess i don't need it completely compatible with the original CLI. It does look for the same HEBCAL_CITY environment variable though.

I'm planning to release v2.1.0 on Purim.

~Sci

On Thu, Mar 13, 2014 at 11:32 PM, Michael J. Radwin < notifications@github.com> wrote:

I don't feel strongly at all.

If you have a vision of completely replacing the legacy C application with js, then one option would be to make the CLI app offer a strict superset (e.g. by default 100% compatible with the existing binary). I don't know if it's worth the effort, though - the value in your JS port isn't so much the command-line apps, but more in the JS API itself which can be used in a browser or Node.js...

— Reply to this email directly or view it on GitHubhttps://github.com/hebcal/hebcal-js/issues/3#issuecomment-37589524 .