Echo JS 0.11.0

I apologize for the comment, I just happen to notice a lot of entries, and looking back at your blog, most articles are much more flushed out.  I try to read pretty much all articles on EchoJS, and most of the top 100 on hackernews every day and don't always keep all the sites correct in my mind.

I also tend to be much more critical of blog sites/entries that have relatively large portions of marketing blurbs attached; such as a lot of the Auth0 blogs that where at least half seemed like thin examples of using their service.  I'm also very critical when there's an opportunity to dive deeper into a more complex topic such as not only why we need workers, but also how we use workers.  Understanding that it's a work in progress feature.  The specific article in addition to an example for the new feature would have been to cover the browser version and how they compare and possibly an abstraction for using the same worker code for both.

Contrast this with the recent CSS Houdini article which was much more flushed out and included a simple example of how to use the new APIs.  Only critique there might have been to embed a working example (with a note of which browser(s) are supported).

Doesn't show combining babel with typescript (target: es2017).  There are quite a few things in babel that are not in the browsers and not in typescript itself.  Especially if you consider in progress specs.

No code sample for actually using the suggested (behind a flag) feature, but one for a higher overhead approach?

Frankly, I'm getting sick of the constant low value posts from logrocket.

I didn't vote this down, and while I agree that React, Vue and Angular are the 3 main frameworks to consider and have some understanding of today, I disagree that Angular is best, and some of the opinions in general are highly subjective.

The pros/cons are all biased and it shows.  I don't think the author has even a good understanding of each of the libraries/frameworks compared.

Angular is a framework, it's very hard to isolate parts and/or replace them in practice.  React is almost purely a rendering library, though some of the recent hooks and the new Context interfaces close the gap.  Vue is closer to React on this, mostly a rendering library with what feels like tighter integration into the browser.

I have my own bias towards Vue for bog-simple stuff you might have used jQuery for.  React for anything bigger than that, and dislike Angular entirely.  That said, pick your poison here.  It's worth understanding and reviewing all three.

The React ecosystem is probably larger than the other two combined at this point.  Vue will probably catch up a lot this next year.  Angular will continue to be used by corporate drone developers who generally don't know better.

That's my $.02, and I wouldn't even recommend reading TFA.

Shell section should probably reference using shelljs module with node scripts directly.  If you're already using node, this normalizes very well across platforms.

Other than that, pretty much every gotcha I've come across is there.

Does this support use of the Cluster module?  IIRC, when I looked at gRPC in node a couple years ago that was a major limitation in practical use for me.

See also: https://github.com/ReactiveX/IxJS

Missing use of `break labelName`, which is more advanced use of break.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/label

Meh... while I do think that using array methods map/reduce/filter etc are generally a better idea from being able to understand code over for loops... there are many cases where the for loop options are better.  Serializing requests or other queue handling in async functions as an example.  Async generators (ES6 Streams with for-async) being another.

I do like the interface overall... I do think the isStale resolver should be passed the key and datetime for when the item was placed in cache.

https://github.com/DominicTobias/keshi/issues/1