Re:How Flow-Based Programming Could Save The Sanity Of Web D...
by drcode on Friday August 23, 2013 @05:12PM
(#6266273)
The crude/simple explanation I think is to imagine your program like an Excel spreadsheet: Some cells on the spreadsheet contain your client-side data (i.e. your "model"). Other cells are used by a javascript library to decide what's in the DOM (i.e. your "view")
The "flow-based programming" model involves creating all the formulas that shuffle the data from the model to the view.
At least that's what I can gather from what I've read (and I agree it's always been a big fail in the past, though there may be some merit to this idea eventually in limited roles.)
Re:How Flow-Based Programming Could Save The Sanity Of Web D...
by enraged_camel on Friday August 23, 2013 @02:34PM
(#6265436)
>>I have two questions. First, what exactly is Flow-Based Programming? Emphasis on exactly.
Let the confusion flow through you!
Second, we know from the history of these things that it's easy to sell managers and journalists on boxes-and-lines visual programming. The pictures look a lot easier to understand than reams of source code do, but that's always because the examples are trivial—invariably some variant of a box with 2 in it, another box with two in it, arrows leading from those to a box with + in it, and then an arrow leading to a box with 4 in it. These always turn out to be a siren song because they don't scale to application complexity. How exactly is FBP different? Emphasis on exactly.