youngbatcat, like a lot of your other posts, that’s untrue and very wrong. Don’t post misinformation.
That approach is never going to happen for Blender due to it’s wildly different development methods. Cinema4D is developed by a company, which means to a large extent they have the ability to assign programmer resources where they see fit, in order to satisfy market demands.
Let me explain a little about how open source development works here.
Blender doesn’t work the same way as c4d, it’s developed largely by volunteers in their free time, and if these volunteers a) don’t have the skills or b) don’t have the time or c) don’t find it interesting to implement such a feature, then no amount of petitioning is going to change that. Yes, most Blender coders would like to satisfy users, but there are a lot of other factors and opportunity costs involved. Adding N-gons to Blender, while very nice, would be a big, big job and would probably mean rewriting most of Blender’s many mesh editing tools, along with other deep structural changes. It’s not easy.
If you want N-gons that badly, you have to find a way to change a) b) or c).
a) is hard to change, there are a small proportion of the blender coders who would actually be able to do the coding required. So you’d have to identify those people, or hire an external programmer (who would have to be very, very good to be able to come in and understand the complexities of the current system and come up with a solution, in a short time).
b) can possibly be changed by paying one of the current Blender coders who have the abilities, if they have other commitments (like a job) that they’d be able to put aside if they were financed.
And c) can be changed by having a positive attitude, posting incentives and finding ways to reward volunteer coders for implementing this, rather than just complaining and criticising them and Blender.