Making Monobehaviour as a Component type in ECS

After learning ECS for some time, I think the biggest usability problem of ECS is actually not so much with the ECS itself, but its interoperability with the current GameObject/Mono structure.
Have Unity devs considered of making Mono-derived component as some sort of ILegacyComponentData? Put some pointer in it so it runs Awake Start Update FixedUpdate etc on the data. Exclude ILegacyComponentData from all the native containers so it can not be used with the job system.
Provide some API like GetEntityComponentData in MonoBehaviour and GetMonoBehaviourComponent in EntityManager;
Deprecate the concept of GameObject and everything references each other with Entity, so everything is unified.
If game devs wish to optimize their existing projects with ECS, they can gradually take data fields from MB scripts to component data and make systems on them.
Just some thoughts throwing out there.

 

See the "Companion Game Object" section of this article: https://gametorrahod.com/game-object-conversion-and-subscene/

Also this: https://github.com/Unity-Technologi...ECSSamples/Assets/StressTests/HybridComponent

Side note: Companion GameObject mechanism has seen several improvements since the README was written.

 

This is entityManager.Add/GetComponentObject which you can use mono types (Add doubles as set). Also see entityQuery.ToComponentArray (not ToComponentDataArray). Component object types are all compatible with ComponentType.__ so you can use them in making EntityQuery/Desc.