I recently tweeted about how adding seemingly minor features can unexpectedly snowball in to a significant amount of work. I thought it was worth writing up in...
I think you have to draw the line for backwards compatibility in some cases. In my opinion, with the addition of a proper scenegraph/prefabs feature, it could be redundant for something like containers to continue to be supported down the line as most projects start to use it.
One of the great thing about how C3 is built is that a lot of features are built-in addons/behaviors and can be phased out over a long period of time. But being a long-term service model, it's going to be quite a lot of compatibility to maintain.. Unless you guys intend to just drop the C3 branding and do a C4 (boom) update that kills compatibility with old projects, it seems like a necessary move!
It can be very unpopular to withdraw support for features people are still using. People interpret an update that removes support for an old feature that breaks their project, as a broken update.
I understand why. It’s always better to be on the latest version of the engine, so it also means for Long projects, constantly reworking my game to use the current features. It took me awhile, but I finally worked out all the old function plugin usage from my games. It took quite a bit of work, because the new functions doesn’t replace certain use cases. Instead, I used a combination of other plugins to substitute for it.
Got to upset some people sometimes, else you’ll end up pleasing no one! Something I feel is already being done well is the slow depreciation method, where for a Long period of time the support is only just support on old projects. That way people don’t fall into the trap of using the “wrong” feature.
Now that you made a pun, I really want this C4.
Hahahah, Glad you liked it.
I'll second this. As a C# dev there's a lot of legacy code running .net 4.0 because clients use Windows XP machines. I mean XP lost support, now win7, if Microsoft can pull the plug, we are succesfully pulling the plug on .net 4.0 and going straight to 4.8, then you can cut the ties with C2.