Echo JS 0.11.0

The reasons to fork from a release standpoint provides a variant that is appealing for certain types of development. The numbers that it appeals will dictate, at least partially, its success/popularity.

The same applies from a maintenance perspective with the semver approach.

There's room for both or N forks really, as long as the users don't get burned out on too many options, which was the topic of a recent JavaScript MVC framework article (can't find it now).

Good to know. I first heard about plato from: 
http://ariya.ofilabs.com/2013/01/javascript-code-complexity-visualization.html

His article references the standalone plato (https://npmjs.org/package/plato).  Nice to see you can do it all from your existing Grunt config.

Definitely keep up the good work!

This is definitely a useful resource, but not really a newsworthy topic unless their guide was recently updated.

Impressive.  Someone with that much time to critique moot datapoints must be a master of the universe.  

I love how he suggests you increase your comment character limit at the end. 

You better remove those links to "Stalk me all over the Internet"!

The first article I read was: http://www.echojs.com/news/3468

That was on April 3rd, 2013.

I'm not sure how I was referred to the article though. Can't seem to track that info down.

Dual purposing UI actions leads to confusion in my experience. Even though well intentioned, the idea that voting also saves to a list is an unexpected result.  Even for our savvy group, I would recommend using common user interface hints, like a star or a save for later element.

For me, I didn't even realize there was a discussion component until looking closely as the small typography near the articles.  Maybe the design could be modified, but I don't know if discussion is the main focus of this site.

For a while I thought that the up/down voting was the focus aside from getting JS news that I really enjoy.