Echo JS 0.11.0

Looks as non-trivial as lenses, but doesn’t seem to be them =(

You mean system time only.
My idea is that shadow depends not only on time, but also on time of the year and geo position (latitude) in general.
When it’s spring in Europe, it’s autumn in Australia.

If one ever thought about how to create efficient search, many ideas there are obvious. Nonetheless it’s still better than 100th article: angular vs react vs vuejs.

Very cool idea, I like attention to subtle details like these. Does it take into account user’s geo position?

Whilst I in general agree, when writing into an object, you cannot emulate that easily. But that’s also unpredictable.
One slight typo and you are writing into wrong place. It’s just dangerous in these cases.

It might seem a little verbose, but having a convention to distinguish container and presentational components is a good idea in general.

No “provider vs service vs factory” =(
Is it really out of trend?

I prefer using Function.prototype.call.bind

The context of the situation is described very poorly.
Currently the guide seems like a twist of chaotic steps rather than migration guide.

So the main reason to introduce this is to reduce boilerplate. But there are other ways to do so w/o going against redux philosophy.