News for hackers. Stuff that matters.
Re:Ask HN: Why has visual programming not caught on? by nostrademons on Tuesday June 28, 2011 @11:52PM (#2708342)
It already has succeeded in one very limited area: GUI component layout. People use XCode/Netbeans Matisse/DreamWeaver all the time to build their UIs.

It fails in other areas because code is remarkably info-dense, and if you split that out into individual components, it takes a huge amount of screen space and visual manipulation for even simple subroutines. I encourage you to take a simple function and draw out the parse tree for it. It's surprisingly large, with lots of different node types all strung together in unusual ways. Think about how much people complain about the parentheses in Lisp; now imagine that each set of parentheses is a box on screen.

Re:Ask HN: Why has visual programming not caught on? by jshharlow on Wednesday June 29, 2011 @12:02AM (#2708352)
Agreed, for GUI component areas it seems it has been pretty successful (I'm assuming anything complex in a GUI would also not be manageable though?). Just from some limited experience it seems a lot of "enterprise" products try to go this route. It seems like the amount of time to program the same logic, vs the complexity in the GUI would actually not be worth the benefit. But I guess the initial 5 minute demo that is shown makes it look really shiny, until u start adding complexity, and then it falls apart.
Re:Ask HN: Why has visual programming not caught on? by david927 on Wednesday June 29, 2011 @03:36AM (#2708707)
GUI layout is not programming; it's GUI layout. (Or, more concretely: it's specifying a dataset.)

When software construction is finally "solved", visual representations and interfaces will be common. Our current mechanisms are simply too crude, lacking sufficient methods of abstraction, to work well. In fact, they do the opposite and point out what deep flaws exist in the current state of the art.

Re:Ask HN: Why has visual programming not caught on? by nostrademons on Wednesday June 29, 2011 @04:54AM (#2708811)
HTML, CSS, XML, SQL, JSON, YAML, and other configuration languages are also not programming; they're specifying a dataset. I can basically guarantee that any large project will have large quantities of them, though, and that code will have bugs.

For that matter, Lisp is not programming; it's specifying a dataset. Except, well, it actually is programming, because you can execute that dataset. When you push it far enough, the distinction between code and data disappears.

This is probably an indication that software construction will never be "solved": once an acceptable representation has been found for one level of complexity, someone will quickly build on that and take it to the next level of complexity, and then the abstractions will once again prove inadequate.

Re:Ask HN: Why has visual programming not caught on? by david927 on Wednesday June 29, 2011 @07:07AM (#2709042)
If I draw a picture, did I program? Are artists programmers? What if I try to execute that binary of a digital image? I would say: no to the first, yes to the last. I think it's a big difference: the aesthetic and basic syntax qualities of markup, the completeness of a list of invitations to a party, and executable code.

To me, HTML, CSS, XML, etc. are not code and do not have real bugs; they have design flaws and syntax flaws, just as a picture may need more red or blue. (But note that I'm not sure there's a right answer here, and I certainly respect you and your opinion.)

I also think that it's not about abstractions but better abstraction mechanisms which work to reduce complexity at any level. It may get more complex, but you can manage that complexity much more skillfully. I am absolutely confident that we can find better abstraction mechanisms.

Re:Ask HN: Why has visual programming not caught on? by bartonfink on Wednesday June 29, 2011 @10:44AM (#2709636)
GUI layout in the sense of moving around graphical elements to produce a larger, desired image is not programming.

GUI layout in the sense of creating a series of instructions for a computer to automatically create and display the same image is much closer to programming than you're making it out to be. In fact, I would say that it is programming at a higher level, as you're not producing an image - you're producing code that tells the computer how to produce that image. If that's not programming, I don't know what is.