This is fair. I've been working on my current project for nearly 2 years (although I haven't been working on it full time, and I've been working as a single dev).
I think a policy like this changes the types of projects you undertake.
With my current game, I would have built a custom engine for it anyway, since the design of the game kind of requires me to have a lot of control over low-level details. So it wasn't a huge stretch for me to go from that decision to, "well, if I'm building my own engine, I sure as heck want to actually own it."
There are tradeoffs in both directions. I'm definitely conscious of the fact that there are things I want to take advantage of that I can't, and I already know console ports are probably going to be horrible to work on.
I think a policy like this changes the types of projects you undertake.
With my current game, I would have built a custom engine for it anyway, since the design of the game kind of requires me to have a lot of control over low-level details. So it wasn't a huge stretch for me to go from that decision to, "well, if I'm building my own engine, I sure as heck want to actually own it."
There are tradeoffs in both directions. I'm definitely conscious of the fact that there are things I want to take advantage of that I can't, and I already know console ports are probably going to be horrible to work on.