Hi Ruben, On Fri, 2019-03-29 at 10:17 -0700, Ruben Reusser wrote: > Robert, > > On 3/29/2019 8:59 AM, Robert Munteanu wrote: > > Hi Ruben, > > > > On Fri, 2019-03-29 at 08:13 -0700, Ruben Reusser wrote: > > > Robert, > > > > > > I think as long as the 'maybe help with other stuff' part of your > > > email > > > is true I'd suggest not to use sling.cli > > Suggestions welcome, I'm not terribly good at naming :-) > > maybe sling.dc (sling developer companion) for things that are > relevant > to the work a sling developer does?
You make a good point - we should definitely delimit the 'developer' tooling from the 'user' tooling. I would go as far as to follow Julian's lead and use the term 'committer' since the term 'developer' is overloaded. Our users are developers using Sling, even though not developers of Sling. > > > On a separate note, for the sling based peregrine-cms we chose to > > > use > > > nodejs for the cli [1] to lower the entry barrier a bit > > That's interesting. I briefly considered using something like go > > which > > seems better suited for CLI tools ... but ended up deciding for > > something familiar. How did you find node for writing CLI tools? > > writing cli tools with node is in fact very simple and straight > forward > as most nodejs based frameworks provide a cli tool. There is also a > cli > tool for front end developers working on AEM (aemfed) at [1] it > relies > on aemsync [2] That's good to know, thank you. For the time being I'll stick with that I know and I supposed that everyone else does. I'm open to experimenting with other langauges, of course, I just think that at the moment this is where our strength is. Thanks, Robert
