Echo JS 0.11.0

Forgive my ignorance, but can you cherry pick single methods out of Ramda?

Cool... if you're publishing a static site in multiple languages, this could definitely be useful... didn't read thoroughly, but what if an italian user *wants* the english version?  It seems that walking people through changing their browser settings to access a single site in a preferred language is a bit overkill.  Would probably add a cookie override/setting...

What's funny, is when I first heard the term `jQuery` as a JavaScript library, this is what I thought it was until I learned about it.

That said, nice little library, minimal size impact, well outlined on the readme.  Haven't tested against it as of yet.

Cool.. I do wish more libraries would put the rough build/payload sizes in the readme though.

Does anyone know of a similar component that is an isolated web component?  Or React?  would be nice to see some comparison examples.

My only concern here might be the size of the script(s) involved.  But it's very cool, and if the payload is under 20-30k probably worth it. :-)

Sigh: how many of these does *ANYONE* need?

Should this really be on this site?  I'm half tempted to delete the post.

That said:

Regarding Dockerization early... I'm not entirely sure I agree... while down time is bad, lifting/shifting the database to a bigger server isn't too hard... same goes for the website.

You can get to be incredibly huge on a single database server, and a single application server if the code is well written to support that model...  Stack Overflow grew vertically a *LOT* before they needed more than 2 servers.

Personally, I'd say Dockerize early for a more streamlined development CI/CD process.  Depending on the database and application chosen, closer to bare metal may be a wiser choice.  If you really want to invest in multiple DB servers up front determine what your needs are.  Is it absolute scaling, or is it read-redundancy?  These things should shape decisions.

Can't wait for the Private member bits to make it in.  Though still have to have it in SpiderMonkey and a few months beyond that.  Right now, I'm targeting ES2017 support for internal applications (babel for newer features), will be nice when ES2020 is the standard that I can ignore what came before.

Not really a rundown of how to document your code so much as a list of tooling options for creating documentation from your code.

Seems a bit convoluted... would be nice if this were isolated into a set of NPM modules, one for abstracting the baseline google library and another for the React UI/UX integration.

First, should probably use a ref when wiring the initialization controls.

Second, I'm not sure how the onSuccess actually gets wired or fired from the child component into the UI itself here...