Hi,
I’m not the strongest coder and it has literally taken me ten months to to create the first level of a game I’ve been writing a book version of for years. The game’s functionality relies on MonoBehaviour functions like OnTriggerEnter, and coroutines and finite state machines and things I’ve become used to using. The game only has about two or three NPCs in it at a time and the player.
Is Unity not going to allow Object Orientated Programming in the future? Is it going to only allow this Data Orientated approach. What I’ve seen of DOTS doesn’t seem to offer anything helpful for the story based 3D game I’m creating.
No, they’ll live together forever. Data-orientated will always be there to compliment the existing stuff, never replace it. Don’t worry about this.
1 Like
Thank you. i’ll still try to learn some DOTS and ECS I’m just a bit scared lol. 
Well I would suggest simply looking at the Job system first as I find this a really nice primer on the first part of the whole DOTS ecosystem. Being able to set-up data for a job, scheduling it, having it automatically run across cores and then get the results is something that is useful even if you never ever use things like ECS which is a different paradigm altogether.
You can then look at the Burst stuff and see how you can get automatic vectorisation of work done for you. All this without even touching ECS.
Many system including internal Unity systems use the job system and have done so for years, well before any ECS stuff.
At some point, you might encounter some code which is just taking too much time and would be a nice candidate for running off the main-thread on lots of cores.
2 Likes