I understand the logic behind the thoughts and respect your stand. And I don't want to derail this thread. But still: Isn't that against the core system of C2? The extendability by plugins is a feature, isn't it? Even C2 itself is based on plugins (I understand that you think they are always safe, while 3rd party may not). Wouldn't it make your life much easier on a long term project, when instead of constantly updating C2 with the risk of breaking something (yes, that can very well happen with C2's own elements, too), you'd stick to one version of C2, with one version of all 3rd party plugins?
Again, this isn't quite the right place to discuss it. So maybe just take it as an suggestion for an easier development process - or just ignore it
I agree, but I think there should be also a fallback method, as I've said, the canvas is more adapted to this use, but knowing another way around (or at least that it can be done) is good to know in case of plugin discontinuity for long term project. I'm more a "use plugins when they can simplify your life, but also know if you could do it without and how just in case".
Again, the only plugin I actually used for myself were the clay.io plugin (I don't use it anymore though), the Paster plugin (I prefer it to the canvas plugin, for better compatibility with WebGL, and it is easier to use IMO), and the FGL plugin (only when I want to use FGL), everything else is done vanilla C2 (I've not seen any plugin that could make my life easier other than those ones)