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

The Case for C# and .NET

chrlschn.medium.com

Post reply on HN
Print view View original

71–80 of 376 posts

Re: The Case for C# and .NET

#71

Post by torginus »

klysm wrote: post #23
labrador wrote: post #5

> For the front-end, JavaScript is unavoidable (for now) Author really needs to give Blazor a try. I wrote some comments last week speculating that I'd use Dart or TypeScript with C# .NET on the client because WebAssembly doesn't do DOM manipulation, but turns out I should have waited to learn it better before making a comment. I've learned I can add events and event handlers to elements without ever leaving C#. Then…

Blazor server was not executed on well. It's a poor react clone before react had hooks. The ecosystem is also small and not flexible. I would choose javascript over it, unless I already had a large investment in C#/.NET.

What? It's Razor templating on the frontend. It's also an MVVM framework, and has much more in common with Angular than React.

Re: The Case for C# and .NET

#72

Post by locusofself »

jimbob45 wrote: post #42
evasb wrote: post #30

I wouldn't lose a second to C# or any MS platform unless required for employment reasons. https://github.com/OmniSharp/omnisharp-vscode/issues/5276

Why would you ever waste time using VSCode for C# when VS and JetBrains Rider exist?

I work at Microsoft as a SWE and use VS Code for c# and js. I've been using VS and Rider a bit as well, but after years of doing python and everything else in VS Code, it's just so familiar and it works just fine for everything my team does so far.

Re: The Case for C# and .NET

#73

Post by bayesian_horse »

jimbob45 wrote: post #42
evasb wrote: post #30

I wouldn't lose a second to C# or any MS platform unless required for employment reasons. https://github.com/OmniSharp/omnisharp-vscode/issues/5276

Why would you ever waste time using VSCode for C# when VS and JetBrains Rider exist?

Can they develop remotely on a linux server? Last I checked VSC is the only one that can.

Re: The Case for C# and .NET

#74

Post by faeriechangling »

jimbob45 wrote: post #42
evasb wrote: post #30

I wouldn't lose a second to C# or any MS platform unless required for employment reasons. https://github.com/OmniSharp/omnisharp-vscode/issues/5276

Why would you ever waste time using VSCode for C# when VS and JetBrains Rider exist?

Licensing costs, licensing costs, and the fact that you often don't need to go through corporate approvals to download VSCode and the C# extension particularly if you are an employee who isn't nominally a "software developer".

VSCode with the C# extension is the preferred C# development environment of corporate shadow IT.

Re: The Case for C# and .NET

#75

Post by pjmlp »

kaba0 wrote: post #66
andrewstuart wrote: post #7

C# and TypeScript seem to be far and away the most popular programming languages today. At least from the perspective of recruiting in Australia. Python is on the way up and third most popular but well behind C# and TypeScript. Golang is on the way up but very small in terms of number of developers. Java is on the way down but will never vanish, it's just not super popular any more. Ruby is small enough to just be a…

C# vs Java seems to be very country-dependendt. Certain countries are huge C# shops, while in others it is barely existing.

In others, consulting shops do both, including on the same project.

Re: The Case for C# and .NET

#77

Post by bayesian_horse »

chaostheory wrote: post #58

Reading this post, it seems like the author never tried Typescript which seems to be heavily influenced by C#. I hate JavaScript as a language, but Typescript is very palatable. Like it or not JavaScript and Typescript are the franca lingua of programming for now

It does seem like the author doesn't have much experience outside dotnet and node.

Re: The Case for C# and .NET

#78

Post by simooooo »

noisy_boy wrote: post #31

My understanding is that with .NET Core, the experience of developing and running on Linux is on-par with Windows(?). However, my impression is that once it comes to building web services, ASP.NET has more "windows-specific" assumptions/moving parts - can someone knowledgeable on this correct me if I'm wrong?

I run all my .NET core apps containerised in Linux. Works the exact same as on windows

Re: The Case for C# and .NET

#79

Post by pacifika »

jeremycarter wrote: post #54
andrewstuart wrote: post #7

C# and TypeScript seem to be far and away the most popular programming languages today. At least from the perspective of recruiting in Australia. Python is on the way up and third most popular but well behind C# and TypeScript. Golang is on the way up but very small in terms of number of developers. Java is on the way down but will never vanish, it's just not super popular any more. Ruby is small enough to just be a…

IMO Python and C# are not comparable. Python is at best a simple scripting language, you really can't build anything globally scalable on it. No offense to people who use Python daily, just my own observations (probably wrong).

Instagram

Re: The Case for C# and .NET

#80

Post by phito »

mccorrinall wrote: post #57
sandreas wrote: post #18

I also think that C# and .NET are awesome. Especially latest releases dotnet 6 and upcoming 7 have a ton of new things to be even more productive. I like the fact, that you can develop command line apps, Web APIs, Desktop Apps and smartphone apps all with the same toolset, including the fact that deployment is possible on nearly every major platform for every major platform (except iOS and macOS Apps, as always only…

I tried writing a simple crud api with asp.net, which should parse and respond json. It was the worst development experience I ever had while writing json apis. Validation? Not existent. OpenAPI/swagger documentation generation? Not existent. Then it also tried to force me into using MVC, while acting that it is express with its middlewares. I switched back to node.js with fastify and wrote my app in an hour. I reall…

The issue here is that you didn't know what you were doing (which is completely normal when trying a new language)
Post reply on HN