|
|
|
|
|
by ericHosick
4453 days ago
|
|
> building systems that ran off of workflows (as in flowcharts)
> but as input they are just flawed The flaw is to assume there is only one mental model that Visual Programming Languages should operate under: say only workflows for example (a mistake all VPLs I've seen have done). This is like assuming that there should only be object-oriented programming when there are other methodologies we use as programmers to form mental models such as declarative programming, functional programming, structured programming, etc. It doesn't make much sense to code out mathematical equations using flow charts. A VPL which supports multiple mental models is able to best represent behavior based on specific business domains. The right tool for the right job. |
|