In the last post, I’ve written a little rant on how awful MonoBehaviour initialization is and teased little more advanced frameworks that can help with that. Specifically - I’m talking about dependency injection.

Here, I said it. It mixes serialization, magic methods, callbacks to pretty much everything and undefined access level of all that in a single, messy soup. MonoBehaviour with two unimplemented methods (which is something Unity itself recommends against), two unnecessary using directives and no namespace is the first thing an aspiring dev sees when he starts to code in Unity. It’s just sloppy.

My name is Piotr and I've been a Unity developer since 2013. It does sound a lot like an alcoholic's anonymous introduction, doesn’t it? Truth be told, sometimes it feels this way. Unity annoys with its instability between versions, teaches bad programming practices, does not help one bit when introducing its inner workings… And yet I keep coming. Surely, it must be an addiction.