Re:It Isn’t Your Father’s Realtime Anymore: The Misuse of a ...
by derefr on Sunday August 23, 2015 @03:20PM
(#10106449)
"ROM" is, these days, short for "ROM image"—the type of binary you'd typically write to a ROM that gets memory-mapped and jumped into, e.g. firmware, a BIOS, or a previous-generation console game unikernel.
"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.
"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.