Quote:
Originally Posted by DevOrc
May I ask why your team jumped from C++ from what I assume is Java?
|
Not the same person, but my team went from C++ to Java last year (so other way around if they started on Java). We did this for a few reasons: (1) There seemed to be more material online for people to learn from, (2) I personally feel it's easier to teach to a complete beginner, and (3) it aligns with AP CS curriculum, which is just sorta a bonus because students don't have to bounce around between the two every day in class then in the lab.
However, I think it's more likely they moved from LabView to C++. A lot of teams are originally on LabView because their programmers can't totally program prior to the season and decide there's not enough time to learn a language which has a much larger learning curve for a beginner (not to say that's why all LabView teams are on LabView though). I know of a lot of teams that decide during an offseason or when they gain a programming mentor they might not have had to move to a more "conventional" programming language, which I personally think is awesome. I view LabView the same way I view GRIP, where it's an amazing tool if you just want to get things done quickly or don't have the proper tools for the alternative, but personally feel the learning experience of using Java/C++/Python is a lot greater.
Hope that wasn't coming across as a diss of LabView or teams that use it, I think it's great if you use it and hold nothing against it. Just feel it's awesome when teams move to languages that are more widely used in industry that present their own issues which you have to figure out.