Zkuq said:
I'm not sure how much experience you have with these things of course (you were a bit vague), so if I'm wrong, I'd certainly like to hear about it. |
the issue with number 1 seems to be resolve now with more stable update cycle. But I remember once that I updated it for much needed improvements only to find out that hitbox collision with concave object was now broke and I used it extensively (it was about 5 year ago). So I guess you could choose not to update but you may be loosing on improvements for stability concern. In the end you'd probably branch the project, update Unity, test extensively, decide if you keep the update or not, and workaround issue if you choose to update. All this process is time consuming and more difficult with larger teams. It certainly had an impact on decision to switch to unity back then.
For number 3, you'r right, it's way easier to switch from C++ to C# than the other way. I used to work for a company that made video games for casino machine in C and C++ 10 years ago and switched to work as a software engineers when the company had difficulties and had to let go 1/3 of its staff. Now I work mainly in C#/javascript. The switch was fairly easy for me to do, but it was not the case for many others (mind you some were working purely in C which is not even object oriented).
Funnily enough this company have now got back on it's feet and started using Unity with a specific Dev team. I know that many, mainly older senior employee, are much stubborn and reluctant to the change thought.
But even without the employee/skills factor. this company had to be ready to let go what was probably $millions in investment over many years in tooling/code base shared with many project to start anew.