RobotC vs EasyC

My school uses RobotC exclusively, but I’ve been seeing a lot of posts about EasyC recently. Can anyone describe the differences? Which do you prefer?

I prefer to use EasyC since I am not a hardcore programmer, in other words I don’t enjoy programming as much as the other aspects of vex robotics. Easy is mostly pictorial, using flowcharts and drag and drop blocks instead of line code. Everything is sorted and categorized for user friendly purposes.

I use EasyC in order to simply get my programing done as in my club I’ve seen people take a whole meeting to get operator control done, while I can do it in easyc in about 5 minutes. Those that prefer robotC usually enjoy programming and get a Bit more complicated with things.

Easy c is all drag and drop functions for your motor commands and other functions and is geared towards those who don’t like programing, don’t have time for it, or don’t have the experience to use robotc correctly.

Also remember PROS and ConVex too

Here’s how to put it simply: ConVEX, PROS, and RobotC are for real programmers. EasyC is for fake ones. :stuck_out_tongue:

Jkjkjk but honestly, RobotC gives you much more freedom. If you’re already comfortable using RobotC, don’t use EasyC. It’s really difficult to do something like Rerun on EasyC and pretty easy on RobotC.

As someone who has spent the past three years programming EasyC and now this year switched over to RobotC I’ll give you my review.
NOTE: I do not do as advance functions like iAndroidOs, but I do use PID on both sides of drive and the arm which is semi-advance :smiley:

They are both C style programming. The main difference is the formatting. EasyC will insert brackets and other formatting items for you, and RobotC won’t. In a way some people find this easier, yet some find it more difficult because things have to be drag ‘n’ dropped. Another key difference is that having to drag ‘n’ drop blocks can also be more time consuming which isn’t that nice. The last difference that I can think of is the download reliability and time in RobotC. It is very good!

In the beginning of the year I didn’t want to switch to RobotC because it was pretty foreign to me, but I am glad I made the switch.

EasyC can still do amazing things. I don’t mean to be cliché, but look at 1103 :stuck_out_tongue:

Goodluck with your decision!

Thanks! Yeah I definitely think I’ll be sticking with Robot C, as I’ve already got a basic proficiency with it and the software for it.

This. I have switched over exclusively to PROS and there is no reason for me to go back. Also learning PROS is actually easy with the good documentation.

I would choose EasyC preferably over RobotC because of the easy interface. In EasyC you basically just drag and drop versus writing code in RobotC. I personally think EasyC is better for those new to programming, cause RobotC is not a easy interface to deal with. EasyC is straight forward and RobotC is more complex :stuck_out_tongue:

They both are good for programming and both are good in their own ways! :slight_smile:

Our club has always used RobotC because it is more practical to apply to real programing. Also the more advanced C programing allows more advanced tasks. However, I have not used EasyC, PROS, or conVEX, so I am biased.

For tournaments, 15 or 20 secs of auton followed by complete driver control, i don’t see how easy c cannot handle that. Hey, it is only 15 seconds, and i believe nobody needs to jump in and out an infinite while loop for infinite times. Easy c is just simple and effective. But when it comes to programming skills of course go with robot c. Easy c can be as easy as possible while robot c can get as intricate as possible.

I greatly prefer RobotC. While I’ve never programmed with EasyC, the drag-and-drop interface seems like a big hindrance to programming. I like to be able to type my programs directly, and dragging and dropping would greatly decrease my programming speed. I’ve also heard that EasyC does not have native multi-tasking support, which is a vital part of my RobotC autonomous programs (RobotC does have native multi-tasking support). All in all, I like RobotC’s implementation of C for robots a lot better :slight_smile:

Wait, what?

What the heck are you trying to say?