code-2018
Team 846's code base for their 2018 robot (by Team846)
kapuchin
Type-safe, cross-platform robotics framework for real-time control and the orchestration of high-level autonomous behavior. (by Team846)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
code-2018
Posts with mentions or reviews of code-2018.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-20.
-
Trying to decide on Scala or Kotlin
Whoa! Never expected a discussion about FIRST here! My team in high-school was actually the first (and only afaik) to use Scala to program their robots. We developed a functional framework for writing robot code (https://github.com/Team846/potassium) and even contributed support for 32-bit / ARM targets to Scala Native so we could compile our code to native binaries ahead of time. Our 2018 robot ran Scala Native the entire competition season https://github.com/Team846/code-2018.
kapuchin
Posts with mentions or reviews of kapuchin.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-20.
-
Trying to decide on Scala or Kotlin
Yeah, the team spent their focus on maintaining a Kotlin framework (https://github.com/Team846/kapuchin) after the switch. But Potassium was designed to be very FRC-agnostic (only ~10% of the code depends on WPILIB) so most components still work out of the box.