[Agentlien]

I have worked full time for five years with a combination of Unreal and Unity. I've also worked for five years with Frostbite and another five in various custom engines.

I absolutely love both Unreal and Unity. Unreal is amazing from a technical perspective and having worked with a talented team in Unreal the stuff we were able to make were mind-blowing given the resources we had.

Unity is way easier to work with if you aren't focused on high fidelity graphics. In fact, I've never tried any engine that felt as easy to work with as Unity. I would absolutely not call it a monster. Even with a fairly green team you can hit the ground running and get really productive with Unity.

[moron4hire]

The problem with Unity for green developers is that a lot of the defaults are bad and there isn't a lot of guidance to fixing it unless you just Git Gud at Unity, which is not something I've observed a lot of green developers do. There's a reason why "Unity Asset Store Dump" is a meme and it's largely because of content farm companies churning projects off the backs of perpetually underpaid junior developers (with no seniors around to mentor them). I saw too many of my friends in the local VR scene 10 years ago see absolutely zero economic progress and very little technical progress because of it.

So yeah, Unity is an easy on-ramp. But unfortunately, I think it puts people in a bad market that doesn't serve them well.

[Agentlien]

I do agree that some of the defaults are quite bad. A great example of this is how even Unity themselves recommend an object workflow very different from what their engine naturally seems to suggest: You really shouldn't use tons of objects with update methods called directly by the engine. You need managers with update functions which iterate over all their subjects. Doing it the intuitive way easily becomes unsustainable and is horrendous for performance.