[dickswan]

Here's a few other "Pros" for ROBOTC.

The elapsed time from when you move a joystick or push a button on the PC Game controller until a motor speed or servo position is changed is much faster. ROBOTC has an optimized Bluetooth messaging mode that is about 50% faster than NXT-G. And ROBOTC messaging to the HiTechnic motor controller is about twice as fast. The cumulative effect is tens of milliseconds faster. Your robot will be more responsive to game controller movements.

Many sample programs specifically focussed on FTC robotcs and game operation.

A PC "dashboard" that gives you continuously refreshed views of all the motor speeds and encoder positions, the servo positions and sensor values. You can even change motor speeds and servo positions via dashboard controls. The dashboard display operates simultaneous with your program running and the built-in Controller Station (i.e. Game Controller testing) function.

A Controller Station (CS) "application" built-in to the ROBOTC development environment (IDE) for easy testing of user control game mode. You can use the single ROBOTC IDE for you edit code, compile, download, test cycles; there's no need to switch between mutually exclusive IDE environment and standalone CS environment.

NOTE: I may be a little biased. I'm involved in ROBOTC development.