Quote:
Originally Posted by Monochron
I wouldn't imagine the new control system would prompt teams to switch, unless something comes out indicating an issue with one of the main three languages.
|
I would expect that support for the 'big three' languages would remain the same as it has been.
Quote:
Our team did Python the first two years and are now switching to Java mainly for ease of use and the ability to compile in a nice IDE. Disclaimer, I didn't actually work on programming this past year, I'm just relaying what I remember hearing from them. So take this with a grain of salt.
We ran into a lot of annoying syntax errors that would have been caught instantly by Eclipse and would have prevented us from loading obviously bad code onto the robot.
|
This is one of the problems with using python -- since it's dynamically typed, you have to actually test/run your code to find the syntax errors, as opposed to depending on a compiler. To help with this, one thing we introduced in the middle of the season was a
robot simulator that allowed you to run your code on your laptop, which my students found quite useful for quick iterative development. Python development for 2015 is pretty active, so hopefully the community will grow more this year.
