toold == tools On Sat, May 7, 2016 at 9:59 PM, William Hermans <[email protected]> wrote:
> *Someday, someone will probably come up with visual system that's general, >> open source and amenable to maintaining in git---but that day hasn't >> arrived yet.* >> > > I think that right now, probably the toold that are closest are the better > UML apps out there. Rational Rose, and Microsoft Visio. Where you diagram > your program flow, and the app builds your app skeleton for you. Functions, > classes, and all it can based on the data you've given it. For me > personally though, this is not my own style of coding. I prefer to write > small bits at a time and test as I go. This way, I do not spend large > amounts of time debugging code . . . > > On Sat, May 7, 2016 at 8:27 PM, Przemek Klosowski < > [email protected]> wrote: > >> These graphical or visual programming languages you denigrate really do >>>> help scientists, engineers, and other "domain experts" who aren't, and >>>> don't want to become, "programmers" implement an idea for which there is >>>> not, and will never be until the idea is proven sound, a budget for "hiring >>>> real programmers". >>>> >>> >> In principle, yes, they are useful and enabling. In practice, however, >> they have been underwhelming, and I can think of several reasons: >> >> - fragmentation: they usually are designed for some domain-specific >> programming (e.g. LabView for data acquisition, GNUradio for signal >> processing, Simulink for control systems, SGI AVS/Explorer for data >> flow/processing, etc). This, however, means that their audience is limited >> to that particular domain. >> - closeness: most of graphical programming systems are commercial and >> closely held by their owners >> - lack of scaling: easy tasks are very easy, but as the program size >> grows, they become unmanageable. It's difficult to determine whether two >> visualized data flow graphs are equivalent: the program representation and >> semantics are mixed up. My favorite dis of graphical programming: >> >> >> - Finally, we can have spaghetti code that looks like spaghetti! >> >> Someday, someone will probably come up with visual system that's general, >> open source and amenable to maintaining in git---but that day hasn't >> arrived yet. >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgGyRF185jpBpgf%2BugqTRsfd5S6QdV9oHXc_W55%2Bs%3D5Ygw%40mail.gmail.com >> <https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgGyRF185jpBpgf%2BugqTRsfd5S6QdV9oHXc_W55%2Bs%3D5Ygw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORomM3Ry9T6SVEYo-7NcXt25isSsMEYoD0ZwK7_Ej69-4w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
