31 ms·

Thanks for the clarification :) As far as I know all current Sphere hardware is based on an ad-hoc Mediatek chip[0], which is really underpowered[1], I think t

Thanks for the clarification :) As far as I know all current Sphere hardware is based on an ad-hoc Mediatek chip[0], which is really underpowered[1], I think this might be a factor. Or maybe I suppose they're bringing up C first and then build the toolchain for other languages on top of that? [0]: https://www.mediatek.com/products/AIoT/mt3620 https://www.mediatek.com/products/AIoT/mt3620 [1]: https://docs.microsoft.com/it-it/azure-sphere/app-development/mt3620-memory-available https://docs.microsoft.com/it-it/azure-sphere/app-developmen...

pjmlp 6y ago
So far the only times that the discussion has come up, they state that their target market won't buy something else and there are sanitizers anyway. Quite strange for a device whose sales pitch is security above anything else. Yet notice how the "The Seven Properties of Highly Secure Devices" story doesn't mention anywhere the safety of the programming languages. Meanwhile on another side of the computer campus we have Microsoft Security Response Center writing such blog posts https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-systems-programming-language/ https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-s... If you dig into developer requests, there are several posts regarding this, for example https://feedback.azure.com/forums/915433-azure-sphere/suggestions/38747848-support-c https://feedback.azure.com/forums/915433-azure-sphere/sugges... Note that I am not advocating that C# would be viable option on Sphere's case, just the absence to acknowledge C as being the platform Achilles' heel in the security story that the team selling. At very least also do hardware memory tagging like Solaris SPARC, iOS and Android (as of 11) are doing.