<rant>
The fundamental problem is that when LVOOP was introduced people said, "Oh classes! I've programmed in C++ or Java, I know how to use those!" So they went off trying to write C++ or Java code in LV. Nobody took the time to consider how to use classes correctly given LV's unique attributes. The result is that I have seen lots of LVOOP programs and none of them really worked from the standpoint of maintainability.
You can't say use "LVOOP" for everything anymore than you can say use "state machines" for everything. We keep looking for silver bullets hoping that if we enforce enough rules (which is really all OOP is about) we can force people who don't have the required discipline into being a good programmer. Rules don't work that way - in any area of human endeavor.
</rant>
I hear what you are saying, about the devil you know, but I would rather be working in an environment that if broken has a chance of getting fixed. Yes NI "supports" 2011, but don't be expecting any bug fixes.
Mike...
