After 1 year of tremendous investment, my research over Meteor Framework shall be over now as I have just reached its bottleneck.
a. Meteor has no reactive aggregation support and is not going to happen this year. It does not support MongoDB 3.2 well enough to create a Relational Database. A Relational Database is almost mandatory when our projects just start to get larger in scope, and we start to look for data joins. We are not able to sort / search relational data in Aldeed:Tabular. That renders it being a plain Datatables plugin which really does nothing significant. I would not be dumb enough to roll out our own Join Indexes by using collection-hooks plugins. It is a very big disappointment and a time consumer.
In addition to (a): even the author of Aldeed:Tabular has given up supporting collection sorting / searching and has omitted the sorting button from their column headers (and then closed all relevant issues).
b. ACL management is a mess. We have Roles and Security and Allow/Deny , that is good. But as long as we rely too much on pub-sub mechanisms, we could not do anything more dynamic. Every sin relates to the relational database requirements when we used Publish-composite as the last resort for it.
c. Most importantly, Problem (1) is literally unsolvable. I tried so many plugins and even rolled out my own autoform fields, plugins, branching my own copy of Aldeed:Tabular and trying to fix…, nope. I see no hope.
I announce you today Meteor is my dead framework, considering it already running out its 2nd round investments. I’ve had enough.