The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Unity EventSystem -- develop with or avoid?
As a traditional .NET dev, my gut says that if there is an adapter pattern like the Unity EventSystem available, one should make every effort to use it. But I've gotten lots of advice from people I respect building apps and frameworks for MR that it should be avoided. It seems like the main benefit of using it is it makes supporting multiple platforms much easier (desktop, mobile, VR, MR). What are the problems with it that make avoiding it a good idea?
VS 2017 v5.3.3, Unity 2017.3.0f3, MRTK 2017.1.2, W10 17063
Microsoft MVP, Freelance HoloLens/MR Developer