News for hackers. Stuff that matters.
Re:Update to the .NET Language Strategy by viraptor on Wednesday February 08, 2023 @06:15PM (#34717050)
* for serverside
Re:Update to the .NET Language Strategy by kcb on Wednesday February 08, 2023 @06:27PM (#34717218)
Yea I'm guessing there's not a ton of fresh WPF or forms desktop apps being created. We've mostly moved to ASP.Net backends with React frontends wherever possible.
Re:Update to the .NET Language Strategy by viraptor on Wednesday February 08, 2023 @08:09PM (#34718319)
Oh, there's definitely a huge amount of wpf and winforms created every day. That's what I meant. Those people just don't visit HN that often. (Then again, I created 4 windows specific wpf apps last year...)
Re:Update to the .NET Language Strategy by jameshart on Wednesday February 08, 2023 @07:03PM (#34717652)
Unity3D is probably one of the most widely used cross platform native app development platforms, and it’s taking c# .net code to Linux, macOS, android, iOS and browsers via wasm.
Re:Update to the .NET Language Strategy by mythz on Wednesday February 08, 2023 @07:14PM (#34717757)
This doesn't speak to the cross-platform .NET Core runtime as Unity3D is built with C++ and still uses their modified fork of Mono to run C# code whilst their WASM uses their IL2CPP tool to convert .NET byte code to C++ before using Emscripten to convert to WASM.
Re:Update to the .NET Language Strategy by mastax on Wednesday February 08, 2023 @07:56PM (#34718197)
Unity is moving to .NET 5+ and, if I remember their documentation correctly, the hold up is entirely on their side and not due to the .NET runtime not being cross platform enough.
Re:Update to the .NET Language Strategy by HyperSane on Thursday February 09, 2023 @12:51AM (#34720228)
So C# -> bytecode -> C++ -> Javascript? Wow.