You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The word “block”, as used in the JS client code, actually means “remote object”, or more precisely “object composed mostly of Cells in a particular fashion”, corresponding to ExportedState on the server side. This is left over from very early design where such objects were almost all also GNU Radio blocks on the server side.
Find better vocabulary and use it.
The text was updated successfully, but these errors were encountered:
Today I thought of referring to this category of objects as Cellular. Pros: Short and descriptive. Cons: Possibly confused with cellular radio; is more an adjective than a noun.
If I did use this name I would rename both “block” and “ExportedState”.
Another piece of the puzzle is ReferenceT which is the server-side value type referring to ExportedStates. This is arguably a different concept, because it is named what it is because it refers to a value that should be proxied rather than copied to the client — but that's more of a statement about what the type is guaranteed to contain than what it is…
The word “block”, as used in the JS client code, actually means “remote object”, or more precisely “object composed mostly of
Cell
s in a particular fashion”, corresponding toExportedState
on the server side. This is left over from very early design where such objects were almost all also GNU Radio blocks on the server side.Find better vocabulary and use it.
The text was updated successfully, but these errors were encountered: