"Fork", meanwhile, has simply transitioned from having a discrete to having a continuous meaning. All Github "code forks" of a project have the potential to become "organizational forks", and whether they do is mostly a question of to what degree the changes introduced in one "code fork" are incompatible with merging into the upstream. I would argue that this transition in meaning is necessary—when every piece of code is owned by some organization, "code forking" is "organizational forking"—but when there is no organization, it can happen that some random stranger's "code fork" becomes the de-facto accepted fork, just because it is being maintained while the upstream isn't.
* isomorphic
* functional
* reactive
* responsive
In other words, embrace, extend, extinguish.
Some examples:
* ROM: something you download and install on your Android phone (as opposed to socketing a new chip)
* Machine Learning: any change in program behavior based on feedback input (we used to call this programming)
* Disruptive: doing business at least slightly different than someone else (as opposed to a new paradigm that sends shockwaves through a whole industry)
* Fork: make a copy of a project (as opposed to starting a rival project based on the codebase of another project)