Present the various options to the kids and let _them_ decide what's easy/hard/powerful/wimpy/etc., based on their personal experiences and preferences for doing things. Some will prefer command lines, others will need a GUI, and a few could probably even adapt/develop their own IDE, given open-source examples! No matter how they get there, the end result should be code that executes properly, is self-documented with well-though-out data structure naming and comments, and, after they've gotten the basics down, has improving efficiency in terms of performance, memory/processor/file resource consumption, etc. I think they should at least be exposed to working on the command line just so they can appreciate how hard software development was and still can be, in environments still stuck in the Stone Age.
Try writing software for the ancient cable TV set-top boxes with 4 MB of RAM that are still out there, "supported" by manufacturer-controlled toolchains that haven't been updated in decades, bugs and all. In some ways, the limited resources of the R-Pi will be a good lesson to kids that you can't always rely on there being the latest-and-greatest tools available on resource-limited platforms. Today's mobile and embedded devices are perfect examples of things where development is still challenging due to the laws of physics. Sometimes, the only editor available is a line editor and, if you're really lucky, vi - you can't just bring in whatever high-falutin' modern technology to which you've become overly dependent (e.g., in truly secure environments, where no connection to the outside world can be allowed, such as installing your favorite IDE/editor/etc.). Not every environment is supported by cross-compilers, etc., either, especially in the embedded world.
The best things in life aren't things ... but, a Pi comes pretty darned close!
"Education is not the filling of a pail, but the lighting of a fire." -- W.B. Yeats
In theory, theory & practice are the same - in practice, they aren't!!!