Re:G# – A modern .NET language with Go, Kotlin, and Swift er...
by mapcars on Thursday July 16, 2026 @05:35AM
(#48932288)
Go, C# and .Net? And here I am wishing for typescript-like language for backend systems.
[ Parent
| on HN ]
Re:G# – A modern .NET language with Go, Kotlin, and Swift er...
by psd1 on Thursday July 16, 2026 @06:06AM
(#48932492)
F# is nice, i like it.
Re:G# – A modern .NET language with Go, Kotlin, and Swift er...
by mapcars on Thursday July 16, 2026 @07:02AM
(#48932878)
Interesting, I have been skeptical about .net as a platform, is it really open and doesn't lock you with microsoft in any way?
Re:G# – A modern .NET language with Go, Kotlin, and Swift er...
by orphea on Thursday July 16, 2026 @10:53AM
(#48935428)
.NET is Open Source (MIT) but Microsoft is a major - it's probably safe to say the largest - contributor.
Maybe similar to OpenJDK and Oracle?
Re:G# – A modern .NET language with Go, Kotlin, and Swift er...
by WorldMaker on Thursday July 16, 2026 @12:04PM
(#48936397)
Potentially viewable as better than OpenJDK and Oracle (and OracleJDK) from what I've seen. A lot of .NET governance moved to the Dotnet Foundation which is built along the lines of things like the Linux Foundation. Microsoft is the major contributor to .NET and a major sponsor of the Dotnet Foundation, but most of their contributions are still flow through the Foundation legal/governance structure and subject to the same governance as anyone else today. .NET is almost entirely planned and developed openly on GitHub including things like meeting minutes for all in person meetings.
Re:G# – A modern .NET language with Go, Kotlin, and Swift er...
by psd1 on Friday July 17, 2026 @06:42AM
(#48945654)
You can infer direction from observable actions, and Microsoft is visibly going for dev mindshare with e.g. Typescript and VS Code. They recognise that they lost the battle for the dev desktop and the server OS, hence the pivot to xplat.
You can code in strictly vim or JetBrains with no friction, and run on mono with no friction in the happy case. It is possible for the SDK to be the only Microsoft product in your stack.
I don't see a way for Microsoft to return to funnelling users to their own ecosystem via dev-ex, and they seem to recognise that.