Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Update to the .NET language strategy

devblogs.microsoft.com

Post reply on HN
Print view View original

31–40 of 151 posts

Re: Update to the .NET language strategy

#31

Post by xupybd »

BenGosub wrote: post #11

How well are F# and C# supported on the Linux platform?

We are running NopCommerce (https://nopcommerce.com/) on Linux with no problems. This is ASP on .Net Core and everything works well.

I have a handful of smaller programs built on the SAFE stack. They're all F# and run very well on Linux. We use a lot of Excel interop so that is a no go on Linux but that is the only limitation I've found. It's not hard to have a server with an Office 365 license to run all of our Excel processing.

Re: Update to the .NET language strategy

#33

Post by lolinder »

starik36 wrote: post #29
ricksmith1962 wrote: post #6

Earlier quoted context omitted.

Absolutely. Saying this as someone who codes 100% in VB supporting applications that are 25+ years old. Honestly, I couldn't be happier with the language strategy as I was wholly expecting VB to be discontinued.

.NET itself is about 20 years old. How are you supporting VB apps that are 25+?

They probably migrated some VB6 apps to VB.NET.

Re: Update to the .NET language strategy

#34

Post by xupybd »

eyegor wrote: post #28
jjtheblunt wrote: post #13

Earlier quoted context omitted.

Huh? F# has Microsoft Research building it and its libraries and optimizing compilers, no?

Last time I talked to them, the entire f# team at Microsoft was still fewer than 10 people. Language features, lsp modules, visual studio support, etc. They do technically exist but it's far from a focus at ms.

I hope that changes. F# is a very nice language to use. I hope that it survives and grows. It's my favorite functional first language.

Re: Update to the .NET language strategy

#35

Post by paranoidrobot »

rqtwteye wrote: post #26
clouddrover wrote: post #2

Sounds like Visual Basic will be a second-class citizen going forward.

VB.NET should never have happened. It has only superficial similarity with VB6. It was sold as upgrade path from VB6 but that never worked.

Perhaps, but I think it offered people who didn't have exposure to C-like language syntax, an easier upgrade path for their own skills.

I was writing stuff in VBA and a little VB6. The move to VB.NET was made easier because of the synax similarities.

My move from VB.NET to C# was made easier because by then I understood the framework, and it was just a matter of learning the syntax differences.

Maybe that's not such a big deal with a lot more people having exposure to C-like syntax languages like Javascript.

Re: Update to the .NET language strategy

#36

Post by JonathonW »

jimbob45 wrote: post #30

Don’t they offer C++ on .NET to some degree? I know it’s not supported on the same level as C# but it’s still there, is it not?

That's C++/CLI; it's still around but isn't really a priority nor is it considered a "core" .NET language these days (it's an optional install in VS2022): https://learn.microsoft.com/en-us/cpp/dotnet/dotnet-programm...

Re: Update to the .NET language strategy

#37

Post by SquareWheel »

starik36 wrote: post #29
ricksmith1962 wrote: post #6

Earlier quoted context omitted.

Absolutely. Saying this as someone who codes 100% in VB supporting applications that are 25+ years old. Honestly, I couldn't be happier with the language strategy as I was wholly expecting VB to be discontinued.

.NET itself is about 20 years old. How are you supporting VB apps that are 25+?

I don't see the contradiction. Visual Basic existed before .NET did.

Re: Update to the .NET language strategy

#38

Post by zengid »

Hot take but I wish they’d start a new lang in the spirit of what’s happening in swift/Kotlin instead of evolving C#. I use it everyday. I love the new pattern matching, it simplifies a lot of gnarly reflective type checks and feels good. Records are nice too. I see discriminant unions are coming soon. But they’re painting themselves into the corner in terms of syntax and overcoming OOP defaults. A fresh start would be incredibly expensive and risky, but it would bring in a lot of excitement and fresh faces. /rant

Re: Update to the .NET language strategy

#39

Post by zamalek »

BenGosub wrote: post #11

How well are F# and C# supported on the Linux platform?

At work our C# codebase never touches Windows (all developers except me use MacOS, I am testing Linux). Production is Linux. We all use Rider, which pretty good (but extremely crashy when debugging). Probably in the region of 500Kloc.

Re: Update to the .NET language strategy

#40

Post by madeofpalk »

Kwpolska wrote: post #12
curiousgal wrote: post #8

2022 I started a new job where we mainly use C# and I have to say, this is my favorite language now, especially with Visual Studio and Reshaper. I've never felt so productive and at ease while coding!

Rider is even cooler, with all the magic from ReSharper, and the much saner IntelliJ user interface.

Microsoft should be embarrsed at how good Rider is.
Post reply on HN