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

.NET Core 3.0 Concludes the .NET Framework API Porting Project

github.com

Post reply on HN
Print view View original

111–120 of 317 posts

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#111

Post by samuell »

denisw wrote: post #15
jeswin wrote: post #7

Given that our deployment platform was Linux (for a .Net Core 3.0 project), I was determined to use Linux and VS Code for development. That was a fail; the verbose nature of C# and the Framework APIs make it impossible to be productive without significant help from a full-fledged IDE like Visual Studio. One might think the verbosity can be reduced by clever coding (and adopting a functional style), but that's not so…

If you install the VS Code's C# extension, you should be getting autocomplete and quick fixes such as adding impport statements automatically. https://code.visualstudio.com/docs/languages/csharp

I can second that. Worked better on Xubuntu/VSCode than on Windows/VSCode even. Really smooth in fact, with intellisense/autocompletion and more just working. Then, I used it only on small CLI apps so far.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#112

Post by jmkni »

oblio wrote: post #34
codeulike wrote: post #28

Earlier quoted context omitted.

- Allow functions outside of classes What do you mean? Isn't that just anonymous functions?

He wants top level functions. He wants to not have to write classes if he thinks the domain doesn't need modelling as objects.

You could create an F# class library, put your functions in there, and then call them from C#?

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#113

Post by daniel-levin »

gtsteve wrote: post #32
jeswin wrote: post #7

Given that our deployment platform was Linux (for a .Net Core 3.0 project), I was determined to use Linux and VS Code for development. That was a fail; the verbose nature of C# and the Framework APIs make it impossible to be productive without significant help from a full-fledged IDE like Visual Studio. One might think the verbosity can be reduced by clever coding (and adopting a functional style), but that's not so…

If you'd like to develop on Linux, I suggest trying Jetbrains Rider. It's as good as VS in most cases, and better in several. I've used it as my primary IDE for most of this year.

Seconded. As another commenter on this thread said, make sure you have a powerful enough machine. I work with Angular a lot. For me, Rider's killer feature is Angular integration [1]. It is far more powerful than Visual Studio's.

[1] Other paid-for Jetbrains products such as IntelliJ Ultimate have the same integration

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#114

Post by samuell »

Can I use the occasion to recommend an VERY good book on modern C# programming: "Functional Programming in C#" by Enrico Buonnano:

https://www.goodreads.com/book/show/31550964-functional-prog...

I'm only a few chapters in, but already it has transformed my C#-writing in many ways, and I have ton of practical ideas on how to better structure my programs in a functional way as I go on.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#115

Post by lultimouomo »

pjmlp wrote: post #81
lultimouomo wrote: post #74

Earlier quoted context omitted.

JetBrains stuff does feel sluggish and occasionally hangs on my 2016 XPS-13 with 8G of ram. It gets the job done, but it's not pleasant. On my new Ryzen 3600 with 32G of ram it runs smooth. So if you go for JetBrains, I definitely advise not to cheap out on the hardware. Rider on Linux was very good for me, working on C# azure functions.

32G?!? Where does one find such employers??? Not to mention how crazy it sounds having 32GB for an IDE. Visual Studio, Netbeans and Eclipse run perfectly fine with 8 GB.

I am self employed, and invested the lump sum of 800€ (+ screen that I already head) for a reasonably beefy desktop machine. I'm not saying that 32G is the minimum required to run JetBrains IDEs well; I'm saying 8G is not enough and 32G is definitely enough to run it alongside a bunch of containers and other stuff.

I agree that JetBrains stuff is resource hungry (maybe excessively so); to me it is still worth using it for Java, C#, Python, iOS and Android. For C++ I prefer Qt Creator (though I must say that the idea of switching to CLion and having a consistent IDE experience across all platforms that I work on is tempting).

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#116

Post by fauigerzigerk »

pjmlp wrote: post #83
fauigerzigerk wrote: post #59

Earlier quoted context omitted.

One of the key problems of our time (besides antibiotics resistance, climate change, lack of affordable housing, poverty, rise of nationalism and totalitarian ideologies, mass surveillance, etc) seems to be the impossibility of reliably generating reference counted code from code written for a tracing GC.

Nah, that key problem will eventually be sorted out with a couple of generational changes.

I'm serious (even if it may not sound like it). COM is a fantastic platform, because it provides simple and efficient interoperability between language runtimes.

But code written for tracing GCs cannot be automatically transformed into COM's (or any) reference counting scheme. And that's why we have this endless tug of war between those who want to build on top of COM versus those who want to build on top of .NET.

It's not just a Microsoft problem either. Our industry has been wasting a ton of resources on duplicating everything for a bunch of different languages/runtimes and it's all either because of GC incompatibility or license incompatibility.

It's not a minor problem even if there are more important problems in the grand scheme of things is what I'm saying.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#117

Post by sword_smith »

FpUser wrote: post #85
manigandham wrote: post #69

Earlier quoted context omitted.

Well do you really need to mock everything? And if so, how is that different than any other stack? Most of the time this is just "enterprise patterns" without any thought about whether it's worth it. I've seen too many small LOB apps that have 5 tiers of code for no reason.

I am seeing it all the time when consulting for companies. Their developers just love taking relatively small things and turning it into multilayered monster with insane amount of dependencies for code, development building pipelines and deployment.

I am designing financial software for the crypto industry and I definitely prefer the ability to 1) have a high test coverage, and 2) quickly be able to write regression tests. Without dependency injection with mockable objects, that would not be possible.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#118

Post by sword_smith »

manigandham wrote: post #69
sword_smith wrote: post #67

Earlier quoted context omitted.

It would seem to me that you wouldn't be able to mock all the classes if you followed this strategy.

Well do you really need to mock everything? And if so, how is that different than any other stack? Most of the time this is just "enterprise patterns" without any thought about whether it's worth it. I've seen too many small LOB apps that have 5 tiers of code for no reason.

Probably not but it is in my opinion very nice to have the ability to mock evertyhing if and when you need it.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#119

Post by dvfjsdhgfv »

jug wrote: post #3

.NET Core 3.0 was major achievement for Microsoft and I like the air surrounding the project and some around it like Visual Studio Code and Windows Subsystem for Linux. The teams working for Windows development are overall on a roll these days and it's both sad and a little mysterious how Windows 10 is still struggling with QA issues, decisions like dismantling their internal testing teams, dual control panels and in…

I can sum up the situation with two sentences:

I hate writing Win32 apps, but I love using them. I love writing .NET apps but I hate using them.

The problem with Win32 apps is that although they look ugly, in general they're blazing fast and work basically everywhere. The problem with .NET apps is although they're aesthetically pleasing, they require the relevant version of the framework to be installed. I remember fighting with installing a .NET-based driver installer that insisted on installing an ancient version of .NET that Windows wouldn't allow to install. Win32 support is still universal.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#120

Post by tonyedgecombe »

gnud wrote: post #41
jug wrote: post #3

.NET Core 3.0 was major achievement for Microsoft and I like the air surrounding the project and some around it like Visual Studio Code and Windows Subsystem for Linux. The teams working for Windows development are overall on a roll these days and it's both sad and a little mysterious how Windows 10 is still struggling with QA issues, decisions like dismantling their internal testing teams, dual control panels and in…

I love it every time I get the 'old' control panel. It means I know where the switches are, and more importantly, what they do. The new UIs change with every minor update. Layout, labels and semantics. It's truly horrible. Please don't encourage Microsoft to mess it up even more.

Not only that but the new interface is becoming just as complex as the old. By the time they have finished they will be back where they started.
Post reply on HN