- Firstly it's a native .Net library, so no more wrapping the old style MvxSock dll whenever we need to use it in a .Net application;
- Secondly it's open source, so with some work this could be used as the basis for building (for example) applications in Windows Mobile, Android or IOS;
- Thirdly it's open source. I know I already mentioned that one but it's worth reiterating. There is an ecosystem of 3rd party consultants and software solutions that interact with M3. Wouldn't it be nice to be able to do so without being beholden to Infor for access to the underlying library that allows this?
For my next project I'm certainly going to look at this as an option. And and when I do (or someone else does and lets me know about it) I'll post my conclusions on its suitability as a MvxSock replacement.