Echo JS 0.11.0

Gotta love a post that starts with "You won't believe what some developer who used to work here did!"

What this doesn't mention is that unless cross-browser support isn't really important to you, you can't really use localStorage without some sort of fallback, because 

a) it's not available in certain browsers under certain conditions (ie, safari private mode)
b) it's prone to failure under certain conditions (workstation security policies seem to affect IE11, there's also a limit on how much storage can be allocated)


we do a few things in our web app with localStorage and eventually the failure rate was high enough that we had to implement a fallback that actually uses cookies under the hood. sadly it's one of those neat browser APIs that not everybody decided to implement properly and as a result can't be relied on :/

Biggest issue with snyk is that when you run snyk protect as part of your post install scripts, it can slow things down a bit. Their servers often seem to go offline or fail to respond, and it can take a while for the script to actually report a failure. 

Apart from that it's a pretty useful tool. They often pick up vulnerabilities that aren't found by github (which also offers dependency vulnerability scanning now), and the ability to automatically open a Pull Request with a remediation is super handy. 

The part I find a little strange is their pricing. There's a free tier and then after that it instantly becomes very expensive. We're able to make do on the free tier but honestly I'd prefer to be able to contribute at an affordable rate, it's a useful service they're offering! Worth noting that it's completely free for OSS too.

I worked on a project with Hapi a few years ago where we built out a huge REST API, and it was _really_ nice. Once we had our basic scaffolding set up, implementing new endpoints with request/response validation, error handling, etc, was really quick. It's got a really nice ecosystem of tools around it but they're all pluggable so by default you don't get the kitchen sink.

Definitely worth a look if you've never strayed far from Express...

Great write up! You've really clearly articulated some very useful points about when/where to use lenses. Thanks.

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.

this is cool, thanks for sharing :)

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.

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.

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?