The GUI rendering model would not work for game objects since GUI nodes are replaced in screen-space and laid out. For game objects you almost always want exact placement against other elements and automatic rescaling and layout on a GO level would alter the relation between objects.
The idea with the render script is that you can indeed choose. You can render your game in any way you want. It is possible to alter scaling of draw passes individually, have multiple views into the game (split screen), post effects, advanced lighting and pretty much anything you want. However, accessing all this power requires that you do some work. So if you want something simple it might feel daunting that you have to setup and modify the render script.
There are at least two things I think we at Defold can do here:
- Look at the camera component. We are aware that it is not adequate, it needs to be properly redesigned and implemented. Doing that would probably make it much easier to solve a couple of common use-cases. This is in our backlog and will happen some time in the future.
- Improve on documentation and examples. We are continuously working on this. Perhaps it would be a good idea to give a few examples with common setups that you could just cut and paste into a custom script?
If you have other ideas, please let us know.