3 ms·

I feel bad for autonomous participants, Java is almost a uniquely poor choice for the size of project FIRST teams would be creating. Java has its domains, but

I feel bad for autonomous participants, Java is almost a uniquely poor choice for the size of project FIRST teams would be creating. Java has its domains, but small, algorithm driven code worked on by a small, inexperienced group isn't one.

bvisness 3y ago
Especially when people try to impose Enterprise Quality Java on the students, and your project gets bloated with interfaces and dependency injection and config files…all for a single platform with fixed hardware :( When we were still using Java, I had the students just make everything static. We don’t need more than one instance of our IntakeSubsystem. We only have one intake. But the OOP boilerplate persists.