I know there already is strong agreement, but my $0.02:
I'm not convinced about AGJS and connection with server-side libraries.
I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs,
I agree with you, but i think AGJS has might be evolving from just a client side lib. This is whole topic could be and should be a whole other thread. I think the original goal of the JS lib has changed and doesn't have as clear of a "story" as the other libraries anymore.
AGPUSH, AGSYNC, are trackes for server-side technologies,
I think for AGSync we have related JIRA's pointing to JIRA's in AG-JS. I thought about doing something like that for the node-sender stuff
consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land.
On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf <[hidden email]> wrote:
On Thu, Jul 16, 2015 at 5:01 AM, Matthias Wessendorf <[hidden email]> wrote:
well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS
i think for the JS library, we would only version components that lived in there own repo. the node sender makes sense here. but store(and other components of the main lib) probably wouldn't get this type of granularity, and at this point, i don't think it makes sense to split them apart