Well, there's tons of reasons that have been listed over the years.
If you're not scripting it, then there's no reason for there not to be a scripted editor. It won't steal any of your time away, order your slaves to get it done. I don't have a problem with it, just like the RC. I don't have a problem with the fact RC is scripted, it has its uses.
BUT, if you're not scripting these tools, so you no longer spend time on tools for Graal, why is it so hard to ask for the external tools to be updated? Its not like you'll be working double time scripting the internal tools and coding the external ones.
From my experiences with client-RC, I don't think internal tools will ever match the performance of external tools. They're sluggish, they carry the faults of the GUI interface, they reflect the performance of the client. Take for example... hmm, a gani editor(I assume this will be scripted as well?). Right now I can open up my gani editor and edit some gani's. It works full speed, no slow-down... its a simple application. But, I suspect, just like with RC, if I were to be using this as a tool in Graal, its performance would drop because Graal itself isn't that fast on my computer.
Also the fact that internal tools will never have the flexibility of external. It's programming vs interpreted. The tools will be as limited as the security and flexibility of GS2.
I mean, I do see the benefits of scripted tools... but personally for me they end up just being fail-safes. Like... "hmm, I'm not home so I won't bother installing the editor to edit this level, I'll just use the scripted one!" And that's about it. Scripted RC is a great accomplishment, and really pushes the limits of GS2... but as far as using it goes, I'll just stick to my external RC.
If you're not doing the scripting(and therefor, not dividing your time between scripting AND coding) why are you so determined to abandon tools that are basically there and just need to be updated? |