ChapterZero

In a word, yuck! I can usually tell, just by looking at an example of code written in the language, whether I will like or even find it possible to learn a programming language. Take VC/VC++ (I *know*, it’s not really a programming language, but still, it might as well be)– I bought a book on it two years ago, knowing I would never read it, but hoping against hope. Still haven’t read it; I’m looking for some Microsoft worshipper to give it away to. Take Perl also, as an example of the opposite situation: I read so many disparaging comments about how Perl has an abominably intricate and intractable syntax. I prefer the syntax of Perl to C– call me strange, but I would think anyone would! The things you can do with one line of code and 5 minutes in Perl would take multiple screenfuls of code and 3 days in C. At least for me.

So that is why I know graphical programming isn’t for me. I think in text now– in regards to programming and anything else. Plus, I have CTS, and I can’t see myself dragging wires between components. Admittedly, for a lazy person like myself, I can see the attraction of using a modular system like all visual programming tools have to be, but only for very specific tasks. When it comes to general purpose text processing or interface building, I say standard text-based programming would make much more sense.

More can be read on this topic at the kuro5hin.org site; search for an article on LabView. The discussion after the article, as is true for most K5 articles, is very interesting, and provides many links.

Possibly relevant posts:

• Redesign Ideas (9/5/2002)
• R6RS ratified (9/16/2007)
• Due South (3/26/2002)