Echo JS 0.11.0

The bigger issue is that if you have more than around 6 connections to a single resource they will be delayed.  It's not so mucha matter of grouping the requests to deliver at the same time as it is about limiting server requests and resource contention.

Websockets would be another solution.

Didn't see this when it was first published, and google didn't show it on echojs.

While on the one hand, I completely understand, on the other, I'd like to see babel have a single document/page listing all the stage-X proposals and links to pages for each of the appropriate plugin for the latest version of Babel.

I switched to individual plugins when all the deprecated warnings started.  thinking of publishing @tracker1/babel-preset-running-with-scissors for an equivalent to stage-0

Definitely cool, but at 35GBP ($45 USD), it's definitely a bit overpriced imho... at $15-20 USD, it would be something you'd get a few just to play with.  I'm not sure I even have a great use case for something like this without spending even more on a surrogate device to work with/against.  For around $60-80 USD I can do an RPi3B+ with case etc and a btle adapter.  It's not as small, but as I said, the puck is really limited without a surrogate device anyway.

This could be a really cool effect for a chat application.

A few points to mention:

1. I feel that redux-thunk with async functions are good enough for 98% of async needs... saga and others are just so much overhead and boilerplate to work with.

2. Look at mterial-ui (which uses React-JSS for styles), it's a pretty nice set of tools to work with on that side.

3. I find Redux easier to work with when things get more complicated, you can break things up and combine them as you need.

4. connected-react-router will tie into redux a bit better... you can also write your own redux plugin to deconstruct querystring parameters and append the data in response to your connected router.

5. Writing middleware for redux can fill a lot of gaps, ymmv of course.

It's an idea I had a couple years ago and finally took the time to do... saves around 200kb on a bundle payload if zxcvbn isn't actually used on a screen.  Loads asynchronously if/when needed.

Finally... might start doing more typescript.

Interesting idea... would be cool to have something like this as a mountable koa module for API access integration.

-1 for me... extremely simplistic example using request and cheerio modules seen time and again.  What would be better would perhaps be an accompanying article surrounding what this project is trying to accomplish and why it was put together.  As is, another throwaway repository on github.

I prefer angular-redux, as it feels like the effects are just a lot more overhead as opposed to say async action creators in a service with redux.  I know the reasons why, but I absolutely prefer a more unidirectional event/data flow that I get with Redux, even in Angular.