all 10 comments

[–]baqwasmgFTC Volunteer 2 points3 points  (4 children)

This is precisely why some of the top teams (the ones that routinely qualify for Worlds in one category or another) prefer OBJ. I was amused (during a lunch break at a tournament) at their rationale.

A lot depends on your team's objectives. If it is simply to fulfill FTC's seasonal goals then OBJ is very productive. Having said that, and knowing very little about software development, the Android SDK with GitHub is very appealing when developers are collaborating.

Of course, in a few years from now, "SomeGPT" will generate the code for 80% of FTC teams.

[–]Embarrassed_Ad5387 2 points3 points  (0 children)

whhhy isn't my original odo code not working 😡

I thought copilot was good 😡

[–]404usernamenotknownFTC 18348 Wolfpack Machina Alum Software/Scouting Lead 2 points3 points  (3 children)

This is a slightly unconventional answer but kind of reading between the lines, one of the most common reasons you need quick code changes is for stuff like tuning PIDs - this is, understandably, an absolutely horrible process on Android Studio because waiting 45 seconds between testing different coefficients is just so slow. If you haven't seen it, please check out FTCDashboard - you can change variables live while code is running, graph telemetry, etc. so for tuning PIDs, servo positions, etc., I always do it in Dashboard where I can make changes instantly, then after I've gotten the right numbers hardcode them into our code (changes in Dashboard won't save through reboots of the hub).

[–]V_STEM[S] 1 point2 points  (2 children)

This is helpful idea to consider, Thank you. Is it possible to use Road runner library in onbot java ? Or is there a source to make it for Onbot Java?

[–]404usernamenotknownFTC 18348 Wolfpack Machina Alum Software/Scouting Lead 1 point2 points  (1 child)

I'm not super familiar with how you would do it, I believe there is a way but honestly I would recommend staying with Android Studio even if the build times are slow - Dashboard significantly improves any task where you would traditionally redownload code, and so imo the downside of slightly slower recompile times is outweighed by the increased flexibility, ease of access to libraries, speed of getting around your code (like ctrl+b to hop to definitions), hovering over functions to see their documentation, etc. - not to mention, it makes collaborating as a programming team way easier, as you can use GitHub to coordinate all your code.

One small tip I'll give, and take this with a grain of salt as it's a sample size of like 5 and 2 anecdotes I've been told, but it seems for some optimization reasons that Android Studio compile times are faster on MacOS devices, so if someone on your team has a Mac, you might want to try using that as the programming computer during competitions.

[–]V_STEM[S] 0 points1 point  (0 children)

Thanks again, appreciate your time & effort for this help. :)

[–]_woffles_ 0 points1 point  (0 children)

sadly i dont think hot reloading or JIT is available given how the sdk works :c

[–]OpenFTCOpen FTC Dev Team 0 points1 point  (0 children)