Skip to content

Instantly share code, notes, and snippets.

@lupincn
Last active August 29, 2015 14:08
Show Gist options
  • Save lupincn/8db4a24880ae3ee2ecf6 to your computer and use it in GitHub Desktop.
Save lupincn/8db4a24880ae3ee2ecf6 to your computer and use it in GitHub Desktop.
TroopJS Comments

Good Parts

  1. Publish/Subscription patten make widget communication more easier and more accessible.
  2. Promise way make asynchronous more clear and could be controlled.
  3. Query cache is very useful and make performance really good.
  4. Use pure EMCAScript standard and new feature also let our code more easily to adapt modern browser.

Bad Parts

  1. Template Engine is too obsolete as current view, should change to more modern language.
  2. Each version upgrade is so painful for developer. Too much thing can't be compatible.
  3. Sometime, memory type subscription is used carefully to avoid UI mistakes.
  4. We have a lot of data change for sigle widget, but we haven't data binging...
@KaresQin
Copy link

Inconvenient Parts:

  1. Hubs are always transfer common messages. But instances from a same widget can not easy to separate the privacy message.
  2. Can not get the latest message from a hub easily.
  3. Troop depend on when and general fix on a version, this may conflict with product code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment