Tod Liebeck dropped some tantalizing hints on the future direction of Echo2. First, it won’t be Echo2, but Echo3! Sounds like the development of custom components will be a touch easier too.
The next version isn’t 2.2, it’s worth of a full version number change. We’re almost ready to do the initial announcement on this one.
The Echo 2.x method of rendering component state to the client is all gone, component state is automatically serialized to the client for you (and changed properties on the client are automatically serialized back).
Another result of the Echo2/Cooee fork? You decide.
