There is even a software "law" related to this: https://www.hyrumslaw.com/

" With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody. "

> I came across the theories of B. F. Skinner, which I thought were terrible, because they were an attempt to fit curves to behavior without any internal ideas.

Anyone guess what he would think about the current generation of popular tools?

Great story. He’s an excellent speaker and very charismatic.

For those interested he has a non profit focused on teaching reading and writing: https://www.johncorcoranfoundation.org/

Related work by the AMP team is their worker dom project: https://github.com/ampproject/worker-dom

The gist is to mirror a subset of DOM apis in workers and project changes back out to the main page.

As far as I know a few companies have tried similar methods, but most write proprietary APIs, rather than using the DOM.

Still in development but the examples are promising.

For those interested in moving apps (or parts) into a web worker, this project by the AMP team has some fascinating ideas (via DOM API replication in a worker): https://github.com/ampproject/worker-dom

Skip the require vs browserify debate and use https://github.com/webpack/webpack.

Allows for amd commonjs and almost any other format around. With gulp and grunt plugins!

I've been messing around with require.js and browserify all day, but I don't really LOVE either solution for a large angular app. I'm going to give webpack a try. Thanks

Our team is using Brunch on an Angular app and the proper module system on top of Angular's "module" system does indeed feel wrong.