Quote:
Originally Posted by Phoenix Spud
C++ was ok, but there were quite a few bugs and the documentation was really bad.
|
I would counter. (at least now) almost everything is documented using Doxygen, and you can easily generate the documentation yourself from the source code.
As far as with bugs, the Java and C++ implementations of WPILib track rather closely now so bugs should be similar.
If you mean as to build toolchain, I can't speak to that as my team has used ucpp for the past two years.
If anything, my anecdotal experience is that LabVIEW broke more often - though the debugger was awesome when it worked, halfway through competition (logomotion). It also bricked without explanation once - we had to do a full reformat in order to get everything back up and running. The technical staff at the regional couldn't figure out why in either case also. The whole affair was rather strange.
That's just my anecdotal experience though, and I must admit to be fair that I am not unbiased in my opinions
As far as I'm concerned, the single greatest factor in favor of Java or C++ is that version control is *much* easier than with LV. That's saved my team on a number of occasions. I also contend that distributed systems are nicer because they let you have full access to history and make commits at the competition without an internet connection to your host.