Quote:
Originally Posted by jkoritzinsky
Additionally, one of my personal goals for a C# WPILib (slightly different from Thad House's goals and possibly the goals of FR-C#) is to be able to use C# to create a simpler and more expressive WPILib that utilizes the language and the framework to create a more streamlined development for programming teams instead of just cloning the official library (which does not utilize many of the features of languages it exists in).
|
I would encourage the C# project to keep to the spirit of the original WPILib, and at least *allow* mostly cloned code to continue working. This what we try to do on RobotPy, to ensure that teams can easily port code between languages (after all, there are a lot more Java WPILib code examples than Python or C#) and allows work on any one of the languages to possibly benefit the others.
I feel like building streamlined / more native extensions/frameworks/etc are better suited as libraries that can be used on top of / alongside WPILib, to allow more advanced teams to use those if desired, but let the new teams stick to the FRC documentation AND use a cool language.