3 ms·
They’re not out of the woods yet: > However, it is worth noting that while the high level control flow logic is written in Swift, some of the parsing steps sti
by saagarjha 6y ago
They’re not out of the woods yet:
> However, it is worth noting that while the high level control flow logic is written in Swift, some of the parsing steps still involve the existing ObjectiveC or C implementations. For example, XML is being parsed by libxml, and the NSKeyedArchiver payloads by the ObjectiveC implementation of NSKeyedUnarchiver.
- pjmlp 6y agoAgreed, it is still a first step. rantmode=on While I complain about how constrained NDK happens to be, I imagine that is exactly Google's goal, to force everyone to write as little C and C++ code as possible. Microsoft seems to be the worst case in this regard, despite the whole security talk, WinDev is pretty much doubling down on C and C++. I find ironic that Azure Sphere sells security, yet only supports C on their SDK. rantmode=off My experience with security advocacy, is that only works with seeing is believing. So the initial Swift rewrite might also be to prove a point to the team, while libxml and NSKeyedArchiver will eventually come down the roadmap.
- mikevm 6y ago> Microsoft seems to be the worst case in this regard, despite the whole security talk, WinDev is pretty much doubling down on C and C++. From what I understand, MS is gradually moving away from C/C++: https://thenewstack.io/microsoft-rust-is-the-industrys-best-chance-at-safe-systems-programming/ https://thenewstack.io/microsoft-rust-is-the-industrys-best-...
- pjmlp 6y agoVery very gradually, Check the praise for C and C++ over here, https://microsoft.github.io/microsoft-ui-xaml/ https://microsoft.github.io/microsoft-ui-xaml/ https://techcommunity.microsoft.com/t5/internet-of-things/developing-secure-coding-in-azure-sphere/ba-p/1796510 https://techcommunity.microsoft.com/t5/internet-of-things/de... Or how XNA was killed in name of DirectXTK. Meanwhile the MonoGame, Unity, WaveEngine, and for IoT, Meadow (what Sphere should have been) efforts are all driven by third parties. Joe Duffy mentions on his RustConf talk that even with Midori proving it was capable to handle production loads (it even powered parts of Bing for a while), it was a no go for Windows team. Apparently the culture change in WindowsDev will take a couple of generations.
- Rhedox 6y agoXNA was written in C++, just like you could expose DirectXTK to C#.
- nindalf 6y ago> Microsoft doubling down on C/C++ I’m getting the opposite feeling. Just last week they released a way to expose all Windows APIs past and present to C# and Rust, with theoretically any language supported on that same framework. I can’t speak to the Azure API you mentioned but clearly Microsoft sees the value in non-C languages.
- pjmlp 6y agoIt is not an API, it is an IoT device sold as being the ultimate achievement in IoT security. Microsoft does see a value, the WinDev unit not so much. "Porting the Clipboard sample to C++/WinRT from C#—a case study" https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/clipboard-to-winrt-from-csharp https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-a... > Unmatched Native Performance > >WinUI is powered by a highly optimized C++ core that delivers blistering performance, long battery life, and responsive interactivity that professional developers demand. Its lower system utilization allows it to run on a wider range of hardware, ensuring your sophisticated workloads run with ease. https://microsoft.github.io/microsoft-ui-xaml/ https://microsoft.github.io/microsoft-ui-xaml/ It is like the left hand undoes what the righ one is trying to do regarding security improvements.
- xiphias2 6y agoThey should add Rust as a .NET language to be able to optimize between languages. Somebody did an experiment of translating LLVM output to CLR IR, and it looked like it had potential.