Quote:
Originally Posted by timytamy
- Pretty much this. If you are a team that is picking a language out of the dark, then the biggest factor should be what is already known. The less time you have to spend on the basics, the better.
- If all things in 1. are equal, you can look onto ease of use/complexity. Personally, I rate the ease of install and setup of Java highly, I prefer to spend time with students writing code, not installing toolchains. Others can speak on behalf of LabView's ease of use/complexity
- Finally, if 1. and 2. haven't made the decision for you, you can think about where the students will go with their programing skills. Others have already spoken about Java being more CS and LabView being more engineery.
|
#4 One that I am struggling with.... Is your decision, only for next year, or path for the team moving forward.
We are a labview team, we were a C++ beta team two years ago, as we contemplating the switch to C++, as some programmers had that experience. This was the year the roborio came out, and the beta documentation was tough, it did not make us want to swtich to C++ as we had a history of good Labview features in our back pocket, that would take sometime to get an equivalent built in C++.
But now, (as I understand it) labview is no longer an option at the FTC level, which means for the future, you will be feeding programmers at the FRC level, with primarily JAVA based programming, from FTC.