Backend performance tests about angular-seed

[dancancro]

Hi Bill

I'm curious about documentation and support for this project generally. It seems to have more functionality than all the others, but if you can't figure out how to use it, then it won't matter that much.

Are github Issues the recommended mechanism for handling questions and discussions?

This Google group doesn't appear to be active.
This chatroom is hit or miss and only good for synchronous help. It seems to be there more for announcing github commits.

[Goochie]

Hi Dan,

i feel the same way, the documentation does not seem to cover the depth of the project and i added this as an issue as there seems to be quite a few questions as issues.

For the life of me i could not work out how to add the label though.

B

[pilsy]

Hi @Goochie & @dancancro,

The performance tests that exist in the node-seed are old, they are the same ones that exist in clever-controller - if you want to run tests please use the ones there until i get some time to make some better tests. (These ones do however show that the node-seed is slightly faster than base express)

I agree that the documentation is lacking, i am basically the sole maintainer of this project and could really use some help with this stuff - i did dedicate 45 days to development of cleverstack recently but i am currently working on an exciting project so i only have a couple of hours a day free to work on this stuff.

The google groups are not really used that much at the moment, the best place would be in github issues using the question tag if you can find it (it doesn't matter, the main point is it gives a place to reply... if you don't have a hipchat account you don't get history in hipchat and i cannot contact you back at a later date if you have left the room)

Alternatively im always happy to help, add me on gchat ([email protected]) or skype (richard_gustin)

[dancancro]

As far as I know, labelling is something only contributors can do. But if, @pilsy you don't mind doing that, I'll put my questions there. I never can tell how groups feel about that, so I assume they'd rather not have them there.

Thanks for the very generous contact info. I'll use the issues first for the sake of posterity and searching, but if I get into an emergency situation I might send you a message.

The inherent trade-off between developing functionality and describing how to use it is a big reason why these separate projects need to merge. The whole burden shouldn't ever fall on one set of shoulders. More hands make light work.

[pilsy]

Ah ok, yeah no problems i'm quite happy to tag the issues as questions for you (or anyone else).

I agree totally, we should be striving to create a better framework/seed/tool - if mean wasn't so far gone i would have helped with that project but it feels like there is no architecture or thought put into it, duct tape everywhere.