Echo JS 0.11.0

Pretty nice... if you're using Mongo/Mongoose for your application's models, this is definitely the fast path to an administrative UI/UX for data management.

Very thorough UI styling library.  A bit more and less than say Bootstrap, but pretty full-featured in terms of examples for most use cases in a typical website.  It isn't a reusable component structure, mostly CSS based.

Definitely interesting, and if you're developing mostly web content and not applications this is particularly useful.  If you're developing web applications, this may not be the best approach.

No idea... tbh, I find a lot of the politicizing in the dev community, more so around npm than any other I've worked in/with, I kind of hope that GH gains a lot of ground.  The last thing I really want from a package repo is a bunch of grief over things I cannot change (when/how/who I was born).

Almost none of the companie mentioned are using Angular (more about 2mc pushing their sales).  Many are using Node on the backend, which is fine.  It seems like 2mc only writes very poor articles to push their tech stack (Angular and Node), not about actually being informative.

I usually just delete the 2mc articles that are spamvertorials, but wanted to comment here...  Going back to my reading/vacation now.

Didn't dig into streams... also the new async generators with for-await syntax looks really cool... though wouldn't mind seeing a synchronous generator interface as well...

Of course it will take a while before a lot of the libraries around I/O with streams are updated to the newer model.

http://2ality.com/2018/04/async-iter-nodejs.html

I really do like the frameworks that take Bootstrap's CSS library and re-wraps component libraries around it.  It's been done a couple times with React, Angular, etc, and a valuable approach.  It's a very nice approach as a baseline.

About my only criticism, is the SCSS is separated from the components.  I also tend to favor Material Design libraries these days, but will often use Bootstrap when under a time crunch.

There are also a few wrappers around cluster to make orchestration and mgt easier[1].

It's also worth looking at the new Worker Threads API[2] for node.  If you're spinning off for compute intensive things, wrapping worker threads in a pool is a pretty good option.

NOTE: If you are using Kubernetes, do *NOT* use clustering in node.  You're better off using the external management of k8s and launching multiple instances that way.  It'll simplify your management and communications interfaces.

[1] https://www.npmjs.com/package/cluster-service
[2] https://nodejs.org/api/worker_threads.html

There's really not enough in the article to recreate the solution... It discusses a potential client api for a queue, and that it can be backed by redis.

This is kind of a solved problem repeatedly...  There are also dedicated queue servers and services and libraries available.

If you want a Message Queue style interface, backed by redis, I'd suggest you look at Kue[1], which is widely used and has a pretty rich ecosystem around it.

If you need more complex queuing, then I'd look at RabbitMQ specifically as an AMQP compatible queue server, or if you're already using a cloud provider, there's usually the option of a simple queue system and a more complex workflow system as other options.

Also, as an adjacent issue, there are RPC systems you can look at behind MQ systems (like kue or rabbit), or orchestration options behind Function as a Service (FaaS) hosting such as AWS Lambda or Azure Functions.  This area is really interesting for micro-service orchestration behind compute heavy operations.

[1] - https://www.npmjs.com/package/kue

Definitely interesting... also nice to see some tests, but I tend to prefer my test files next to my implementation.

Frankly, you should have looked at the source code for the material-ui project and the components there.  They're using the theme system and reusing or inheriting from there... It's actually really easy to create your own components from the base components outlined.  There are also tools for creating customized themes and colors, etc.

It's really in a similar vein to when I talk about Bootstrap, as it's also really easy to look at and use/modify the styling from the source scss files.  Likewise you can definitely use the primitives, themes, cards, etc in material-ui's library to create more customized components with the events you need for your own reuse.