> How about being able to write extensions in Python? It's a far simpler language than C++, which would make it easier for amateur developers to write extensions for Construct. Python has great interoperability with C++, so the Python SDK could be entirely based off the C++ SDK.
>
I don't think writing extensions in Python is a good idea. That would effectively nullify the one of the major benefits of extensions in C++: C++ is fast. It's a compiled language. Python is interpreted language, so it doesn't perform any faster than Construct's events, which are, too, an interpreted language. Actually, I think that events might perform faster than Python, because they are very simple. But I don't know, it's about the optimisation of the interpreter, after all.
Only for close loops; for many things you can bind to C++ for any function you'd want to impliment that's available in the C++ world to python but not available to Scirra by finding the python bindings and attaching it to the scirra plugin SDK wrapper for python. This is useful for people who don't like C++ but will tolerate easier-to-use languages like python and would only want limited extension creatibility... I guess it all depends on what sort of extensions you could create with inline python rather than importing it...
As for Ruby and Lua, please god no. Beauty in language? Are you guys smoking your CS majors? The whole idea about easy tools like Construct is that form follows function -- it does what it does and it does it good, effective, and easy. I should disclose my personal bias by saying that I'm a BASIC programmer and I don't give a crap about "beauty" in the classic programmer's sense -- verbosity makes it much easier for ANYONE to get into programming vs. something that looks like a math problem.
Edit: To not sound like a hypocrite I also request that Scirra's inline python editor provide auto-tabs