Echo JS 0.11.0

<~>

mxxx comments

mxxx 38 days ago. link 1 point
Funny that this should get re-posted, I ran into a bunch of problems with localStorage in a production app just recently; a certain group of our users were unable to use localStorage (seems like some sort of content policy issue) and as a result some of our functionality was failing. 

The odd thing about that particular article though is he recommends falling back to in-memory storage, which isn't really the same thing at all, since it doesn't persist across sessions (which is generally the point of localStorage, no?)

Potentially you'd be better off using something like localForage which attempts to use other APIs, or even a cookie-based fallback.
mxxx 74 days ago. link 1 point
this is cool, thanks for sharing :)
mxxx 85 days ago. link 1 point
Hey this looks cool but you should put some screenshots up on your github README. It feels a bit strange looking at an app with a GUI that you can't see.
mxxx 208 days ago. link 1 point
Thanks for sharing! I might get some of the guys on the team who are newer to React to have a read of this, looks like quite a comprehensive overview.
mxxx 304 days ago. link 2 points
I've never been 100% clear on why you'd want dependency injection in a situation like this... Can anyone elaborate on what the real benefits would be?
mxxx 331 days ago. link 2 points
interesting concept! 
can't get the demo to run in chrome though because it's requesting jquery and the google fonts over http from an https source.
mxxx 678 days ago. link 1 point
finally! this is what echojs has been missing all these years.
mxxx 737 days ago. link 2 points
yeah, maybe a more useful title would be "µWebSockets significantly more performant than socket.io". this one's a bit alarmist, isn't it?

edit - interesting benchmarks though.
[more]