Live data from Hacker News

Visual Programming – Why It’s a Bad Idea

mikehadlow.blogspot.com

121–122 of 122 posts

Re: Visual Programming – Why It’s a Bad Idea

#121

source control is the biggest problem with visual programming. i remember doing something we eclipse modelling tools which actually supported merging of models but you just lose so much going from languages that are supported by the existing text based eco-system to languages that are not.

Is this an inherent difference, though, or "just" due to current source control systems being built with text in mind?

It's also an issue with the final output of these tools being text, instead of reified computer models.

Re: Visual Programming – Why It’s a Bad Idea

#122
post #119
post #114

Earlier quoted context omitted.

To begin with, the labview run time is riddled with bugs. Every application I've ever seen written under labview is expected by its creators and its users to crash randomly and continually for no explainable reason. Yes, drawing out some things in a visual IDE and having it work is nice. The problem is that eventually LabVIEW is going to update their runtime and it won't work anymore. Now what? Take the time and do i…

do it right up front, Ok, but again what do you suggest is 'right' then, any example? Because as laid out, for me, it is right, since we have zero problems. Every application I've ever seen written under labview is expected by its creators and its users to crash randomly and continually for no explainable reason. Hmm, strange. Sounds to me like those creators must be doing something wrong. I mean, we've been running…

Or the labview runtime is absymal and broken and you simply haven't tripped over any of its thousands of broken cases in the minimal use of it you've done.
Post reply on HN