Our first and foremost goal at this time is still to create a highly robust, open, and “industrial strength” hardware/software base platform that stays as close as possible to the Microsoft standard for .NET and NETMF. As the saying goes: “soon ripe, soon rotten”. To make the platform as bomb-proof as possible just takes a lot of (very unspectacular and barely visible) work. As our manpower resources are constrained, we will therefore usually lean towards “less is more”. In practice, this means a subset of the standard NETMF feature set, suitable for headless Internet gateways.
Steve Jobs often said that even Apple, now the world’s most valuable company, can only do a few things at a time really well. This is true even today, and so much more so for a smaller company.
Yet sometimes a customer “forces” us to go even beyond the existing NETMF feature set, by paying money This happened recently when a long-time customer needed analog output, which is not a standard feature of NETMF. So we submitted an API proposal to the .NET Micro Framework Core Tech Team for review. As a result, starting with NETMF 4.2 QFE2, analog output will be a standard feature of NETMF and we are again happily within the standard feature set.
I am glad, however, that it should also be possible to use GHI’s more extensive libraries on our hardware. Together with the community contributions it can add a lot of value to a project for which additional capabilities are needed, e.g., RLPLite.