Re:Go 1.8 Performance Improvements on ARM (RasPi)
by rosbrith on Friday January 20, 2017 @09:43AM
(#13444084)
Oh, this takes me back to my university days where I spent time with Lejos [0] on an RCX brick (32 kilobytes of usable space).
I recall using Eclipse for development and I am sure the build process involved uploading the JVM and program code via a USB infrared interface.
Have to say that I preferred using "Not Quite C" [1] due to it having a simpler syntax and intuitive support for cooperative multitasking.
[0] http://www.lejos.org/ [1] http://bricxcc.sourceforge.net/nqc/
Re:Go 1.8 Performance Improvements on ARM (RasPi)
by khedoros1 on Friday January 20, 2017 @03:26PM
(#13446721)
I had a lab partner, and Java was our shared language. I don't remember the decision process that went into choosing our language, but I'm sure that was a big part of it.
Actually, looking at NQC's page, they don't support the NXT, just the RCX. That certainly would've been the killer for us, there.
For reference, the NXT v1 brick has an ARM-based Atmel microcontroller with a clock of ~55MHz, 256KB of flash, and 64KB of RAM, along with a smaller ATMega4 microcontroller.