Interesting read... really applicable to very large organizations that would want to distribute portions of visibility to different development organizations and teams.
For example, a large financial institution may want a consistent interface for header, footer and navigation, where each subsite will need to reuse/register their place in the larger application.
This is a very deep well in practice and there are infinite combinations and no perfect solution, only combinations of good enough in this space (imho).
This article is just wrong... it seems to be confusing `async function` and the `async` module in npm. Do *NOT* follow this article's advice...
Should I just delete the link?
While JS is my favorite language... and it's more broadly available than pretty much anything else. It's also probably the most widely used (by nature of web dev). All of these things said, it's a poor language for a beginner to learn programming concepts with.
IMHO, if you are visually oriented and/or starting from a designer or front end perspective, JS might be the best choice to start with (this assumes you have some HTML and CSS knowledge to leverage). If you are coming from ground zero and want to learn programming, Python is probably the best language to start with.
Python was created as a learning language and has expanded into many areas. The learning content for Python is very broad without diving into hardware/cs concepts to get your feet wet.
I say this as someone that loves JS, and doesn't really know any significant Python at all.
I really appreciate github's actions, and it's imho better, if similar, than Azure's new pipeline .yaml format. Will probably migrate some of my npm packages from travis.
In case anyone is doing a publish to npm proper…
https://gist.github.com/tracker1/fdd5ceab8f532afc3a05ab9c0bddebc1
Interesting simple approach, should probably check and see how big the import gets. Seems to depend on amonad that has a tslib dependency (not dev dependency).