I would say that C/C++ would be better, if you’re willing to spend some time learning both languages. Simply put, a scripting language may be as fast, or nearly as fast as the same application written with a language so that it runs nativly. The native application will almost always, if not always use less processor time to do the same task.
C/C++ at least in my own mind is no more complicated than using javascript ( node.js / bonescript ). It all boils down to which libraries you can find / use for the given language of choice. Then of course, your ability to read, and understand how the code ( library ) are meant to be used. Bonescript for instance, is very similar ( in usage ) to some Arduino libraries I have seen. Which are written mostly ( all ? ) in C/C++. To be sure, there is always a lot of reading / understanding to do when using new software libraries. As such I still feel that it would be good to start off with a low level language such as C/C++. After that, something like javascript will be very easy to use / understand. At the end of the day however, context means a lot too. Do you need to slap together a demonstration of hardware abilities for a presentation, or are you a hobbyist who just wants to do “stuff”. Also, it can be argued that there is a “right language” for every job.
As for which IDE, or compiler / toolchain . . . there are several options. Personally I have only used Linaro’s gcc with code::blocks on Windows( so far ), but this option is also available on at least Linux too( the code::blocks IDE is crossplatform ). It may also run on OSX, but I am not sure. If you’re not too keen on JVM this may be a decent options. Code::Blocks is relatively customize-able, so it can work with many different gcc toolchains ( and possibly more ).
Eclipse also seem to be very popular, and it is also very feature full. Probably even more customize-able than code::blocks, but is based on java ( requiring a JVM to run ). If not for this last fact, I would probably be using it myself, but I am adverse to using anything that requires a JVM to run. If not a problem for you, then Eclipse could possibly be the IDE to use.
There are other possibilities as well, but probably too much for a new player to worry about. Meaning, technically with a bit of “magic” You can technically use different toolchains with Visual studio. But setting something like this up is not for the timid, and quite possibly can take a good bit of your free time initially to get working. In this given case it all boils down to what you want / need. Usually something like this is too much hassle to even bother with, despite Visual studio being a top notch IDE. And there are many other possible similar scenarios . . .