Put information into tables

Author: BaronClaps

src/misc/pedro_vs_roadrunner.md

@@ -1,60 +1,22 @@
 # Pedro Pathing vs Road Runner
 
-**Pedro Pathing** is a path-following library that utilizes a reactive vector follower
-that implements translational, heading, and centripetal force correction
-to dynamically converge to the target position. 
+| Feature | Pedro Pathing | Road Runner |
+|--------|--------|--------|
+| **Path Following** | Path Follower | Trajectory follower using motion profiling | **Visualizer** | Web-based using a nonstandard (0 - 144) coordinate scheme | Code-based using the standard FTC coordinate scheme |
+| **Tuning** | Half manual and half automatic | Nearly all automatic |
+| **Motor Write Caching** | Used by default | Able to be implemented manually |
+| **Paths** | Cubic Bezier curves | Quintic Hermite splines |
+| **Bulk Reads** | Able to be implemented manually | Used by default |
+| **Logs** | Not built in | Automatic logging of every run |
+| **Priority** | Speed | Time consistency |
+
+| Information | Pedro Pathing | Roadrunner |
+|--------|--------|--------|
+| **Docs** | <https://pedropathing.com> | <https://rr.brott.dev/docs/v1-0/installation/> |
+| **Quickstart** | <https://github.com/Pedro-Pathing/Quickstart> | <https://github.com/acmerobotics/road-runner-quickstart/tree/master/> |
+| **Visualizer** | <https://visualizer.pedropathing.com> |  <https://github.com/acmerobotics/meepmeep> |
+| **Library** | <https://github.com/Pedro-Pathing/PedroPathing> | <https://github.com/acmerobotics/road-runner/> |
 
-**Links:**
-- Docs: <https://pedropathing.com>
-- Quickstart: <https://github.com/Pedro-Pathing/Quickstart>
-- Library: <https://github.com/Pedro-Pathing/PedroPathing>
-- Visualizer: <https://visualizer.pedropathing.com>
-
-**Pros of Pedro:** 
-- Makes your bot drive faster.  
-- Excellent correction for unexpected disturbances.
-- Has a no-code, browser-based path visualizer.
-- Caches motor writes by default.
-- Corrects for centripetal force to hold the robot onto curved paths.
-- Path curves can be manually set using control points.
-- Speed is prioritized
-
-**Cons of Pedro:**
-- Visualizer uses a nonstandard (0 - 144) coordinate scheme.
-- Quickstart code is not under the standard TeamCode package name, 
-making using SlothLoad and integrating existing projects more difficult.
-- No logs, so no replays of each run and much more difficult debugging.
-- No AdvantageScope support.
-
----
-
-**Road Runner** is a motion-profiling-based follower library
-that includes a command-based action system and geometry. 
-
-It prioritizes time consistency above all else.
-
-- Docs: <https://rr.brott.dev/docs/v1-0/installation/>
-- Quickstart: <https://github.com/acmerobotics/road-runner-quickstart/tree/master/>
-- Library: <https://github.com/acmerobotics/road-runner/>
-- Visualizer: <https://github.com/acmerobotics/meepmeep>
-
-**Pros of Road Runner:**
-- Stable, minimal bugs if any. (Recently, this has not been true)
-- Time consistent by default.
-- Tuning is almost fully automated, making it difficult to screw up. <!-- 5 automatically tuned constants, 3 manually tuned constants ... PEOPLE still do? -->
-- Extensively tested and used by thousands of teams; almost all possible problems have been solved before.
-- Uses the FIRST-recommended standard coordinate system consistently.
-<!-- - Works with SlothLoad immediately. || this is a quickstart thing, not a library thing itself? -->
-- Built-in custom logs, for easier debugging and full replays of every run.
-
-**Cons of Roadrunner:**
-- Prioritizes time consistency above all else, meaning worse correction.
-- Slower speed by default.
-- Path curves are less flexible then Pedro. 
-- Path visualizer is code based.
-- Does not cache motor writes by default.
-- No built-in centripetal force correction.
-- Bulk reads by default.
 
 <!--
 
@@ -63,8 +25,6 @@ Guidelines for editing this page:
 Differences must be objective issues from a neutral point of view, not one sided.
 Ideally, people with biases in both directions should agree about these differences.
 
-Each difference will be listed twice, as a pro of one library and as a con of another. // Just because something is a pro of smth doesnt mean its a con of the other...
-
 Actively avoid being reductive or summarizing into an overall recommendation;
 the idea of the page is that both libraries are good for different needs,
 and the reader should decide for themself which library aligns with their priorities.
@@ -76,7 +36,6 @@ If you feel that a library has too many cons, consider fixing the underlying iss
 and improving the experience for all users. Let us know (in an issue, PR, or in the Cookbook Discord)
 after this happens and we will be happy to remove it from the list.
 
-
 -->
 
-*Last Updated: 2025-7-7*   
+*Last Updated: 2025-07-07*