Echo JS 0.11.0

Kind of a meh article.  There's very little point to the Angular example, and the rest doesn't provide much.

IMHO, for the most part, just use fetch, and write your own abstraction for your API access over that.

Decent article... should probably include generators and for await while at it though.

Other than I'm not sure about the need for trolley, the service the blog is oriented around.  There's a 2% fee on top of Stripe's relatively high fees.

I love JS, love node... but "fast" is relative.  There is also scale, and environment cost to consider.  You need a runtime, you may need a convoluted build environment.  It varies.

For me, it's a language that almost everyone has to know/use as so many applications have a web front end.  It's a scripted language that runs almost everywhere you'd want it (Linux, Windows, Mac).  You don't generally need a build step for orchestration scripts.  package.json tasks with npm make it easy to have your dependencies and the task definitions in one convenient spot.

A couple technical issues, and not a clear comparison of why one would use JWT over or in addition to cookies.

While very cool, I'd really rather see a blog article for how it all came together, tools used, etc.

Middleware is one of the options that is mentioned.

It's pretty much the exception to the rule.  The main application I'm working on now isn't using SSR, so it doesn't hurt me to have a global __BASE__ state, this is where I inject configuration variables/options as well as a lot of the localization/strings.  There's also localStorage and sessionStorage.  Not *EVERYTHING* belongs in redux and there's no shame in putting a couple details like this outside that scope.

I tend to do my UI/node dev locally, but have been working on stack deployments to docker, as well as running the tiers I'm not actively in within containers locally.  It's been really nice.

Gotcha worth note, do *NOT* use volumes for live database files in windows or mac... docker desktop runs in a vm and uses a file cloning service between the container and the desktop for volume mounts, unlike actual Linux.  database backup/restore path or other volumes are generally okay, but scenarios with lots of read-write operations are bad in mac/windows.

Even beyond the link shortener, there are a few domains apparently in a spam filter for the submission, so the authors now submit a blurb with the url in the blurb.  I don't know what the honestly expect, there's rel=nofollow on all the links here, it's not like they gain SSO from this site.