(I hope I was not the only one who read that entire post in bender’s voice)
I’d like to take a stab at addressing some of your concerns Quinten.
- We need more and more real-time features.
GHI has always maintained the ability to do real-time with their RLP offering. Now with TinyClr it gets even easier. One person (who’s name evades me at this moment) was even able to do ADC sampling and conversion at audio frequency rates while .NETMF was running on the same processor. He calculated that the ADC functions took up about 30% of the CPU’s time. All it made NETMF do was run a little slower.
The option of real time is one of the foundations of TinyClr.
- The growth of Linux embeeded systems, with a lot of hardware I/O is really appealing, we can find a lot of help as well on these plateforms, and also when it’s time to hire engineers, it’s easier to find linux embeeded specialists than C#/Netmf specialists
Lolz. I assure you, that is is more difficult to find help for linux than .NETMF. Case in point. When GHI released “The Module”, which runs debian, myself and another were trying to get it to connect to the network persistently using WIFI. It was a nightmare to find consistent information on how to do it. Given that things can change in the linux world unexpectedly, an without documentation, I’ve found it harder to troll through thousands of pages of documentation to find even a simple answer, than just @Gus, a question.
You don’t need NETMF specialists!!! Anyone who knows C# and Visual Studio can learn netmf quickly, and they are typically easy to find.
- Even if GHI is very responsive, and seems to grow, it is difficult to have only one provider.
TinyClr to the rescue. You can at any time, get suitable arm device and port TinyClr to that platform yourself. E.g. IngeunityMicro
- And as mentionned on the original post, the low activity on this forum does not seem to indicate that a lot of people uses the plateform (or nobody has any issues ;-p)
It’s the lack of issues. TinyClr is totally open source. Not sure why you’re getting that weird exception? Read the code; fork the code; fix the code; problem solved. Also, most of the people still participating on the forum have been here 5+ years. Forums like that tend not to have 19 posts with the same issue posted over and over by different people. That’s the relm of a stack exchange site, not here.
With the release of the AM3358 Sitara Processor into GHI’s line up, it now means that they now have an offering that can relate to any level of embedded system’s development.
(NB We were also able to do C# development on the AM3358 Sitara Processor using the mono framework).