@gts Sounds like normal growth there, PR’s welcome of course, with benchmarks and explanations and such. 
OvermindDL1
2
gts
Maybe is better to brainstorming about the Drab future, discuss the current limitations and then agree on the roadmap before starting to PR, trying to involve in the discussion many of the existing users, what do you think?
3
OvermindDL1
Yeah, probably should start a list of what should be done and why, then work out how they can be accomplished. Feel free to start? ^.^
2
gts
I’ve started to write a shared doc on google docs where we can more easily elaborate and share our wishes on Drab future roadmap, anyone interested can contribute
And I’ve just submitted a PR for supporting PubSub in Drab applications (allows page updates on data changes). I think this is a killer feature that LV has and that Drab cannot afford not to have.
3
OvermindDL1
Located where? ^.^
Adds support for allowing PubSub subscription and events handling by guidotripaldi · Pull Request #189 · grych/drab · GitHub for anyone curious.
2
gts
Located where? ^.^
what do you think it is better, leave the document write-open to anyone, or include as editors, for now, only those guys that express the aim to collaborate?
1