I've actually started to use it to teach Javascript to 10 year olds in my local primary school (through a CodeClub I run). It has been a great experience and a lot of kids are moving quickly through the campaign levels.
I even have a few kids who moved on to the multiplayer levels.
Quick remark: the computers in the school are Core 2 Duo machines with 1.75GB of RAM. They are running the latest version of Chrome on XP but often crash on CodeCombat (lack of RAM?). It's a shame but reloading usually solves the problem. Also, getting coordinates on the map is usually quite tedious (it doesn't seam to work all the time).
I am really excited about the future of CodeCombat.
We'll keep working on the RAM needs, but yeah, that is just about the lower limit that I would expect to be able to play the game at all currently. We have a lot of work to do, but don't worry, we'll get it running on older and older hardware as we optimize. Thanks for your patience (and your students').
Interestingly, we have a 10-year-old who hangs out in our dev chat and helps us playtest and simulate. He actually came up with a strategy that did pretty well on the ladders for this latest one, and we'd challenge our other (existing developer) playtesters to c'mon, surely you can beat the 10-year-old!
Looking to the future, we have some ideas to push that younger and younger, too.
I've actually started to use it to teach Javascript to 10 year olds in my local primary school (through a CodeClub I run). It has been a great experience and a lot of kids are moving quickly through the campaign levels. I even have a few kids who moved on to the multiplayer levels.
Quick remark: the computers in the school are Core 2 Duo machines with 1.75GB of RAM. They are running the latest version of Chrome on XP but often crash on CodeCombat (lack of RAM?). It's a shame but reloading usually solves the problem. Also, getting coordinates on the map is usually quite tedious (it doesn't seam to work all the time).
I am really excited about the future of CodeCombat.