Live data from Hacker News

The Case for C# and .NET

chrlschn.medium.com

371–376 of 376 posts

Re: The Case for C# and .NET

#371

Earlier quoted context omitted.

.NET core can run on any platform it wants, but as long as it's from Microsoft, the company as we know it, I won't even write "Hello, World!" with it. A language can't be the fastest at everything in today's mature language ecosystem. OTOH, Debian's "Programming Language Games" benchmarks shows it's on par with Java (which is not slow in any means), and not as fast as you claim [0]. In the page I shared, some C# benc…

Small nitpick, Nodejs has a JIT (via V8) and you will be surprised at its performance when compared to Python.

I know, I've written NodeJS for a very short time, and remember liking it. However I can't position it into my current ecosystem where code is probably be seen by multiple people and need to understand/improve it.

Thanks for reminding, BTW. :)

Re: The Case for C# and .NET

#372
post #270

Earlier quoted context omitted.

I’ve been a C# developer for a decade and I still think it’s hopelessly convoluted for getting very simple things up and running. Maybe there is something wrong with me, but it’s just not intuitive to me and it has frankly never been. I do think the move to core and then core to .net has improved things, but it’s still a really weird and way of doing things compared to other languages that I have worked with, and mos…

I wholly disagree as a person who worked in C#/.NET for over 15 years and recently waded into Node/JS/TS dev. C# and .NET are hands down the easiest platform to start on.

In my decade around management that was not my experience with onboarding new people.

Maybe that is because we didn’t have a fascist linter for C# the way we do with Typescript, but it’s always been much, much, harder to get people to make “good” C# code in my experience. It hasn’t been hard to have the build things in C#, but it’s been hard to get people to build things the same way so that they can work on each others code flawlessly. So hard that I would never again consider using resources on it until developers drop significantly in pay, which isn’t likely to happen until I’m retired, if ever.

I wonder if it has to do with regional differences. I’m Danish, everyone (there are odd cases, but it’s more “everyone” than “almost everyone”) here has a CS degree and often they’ve been taught Java, sometimes C# but poorly, while obtaining it.

Re: The Case for C# and .NET

#374

There are 171 posts at the time of writing, only one (this one) includes the character ♯

Will you tire of posting about this stupidity? https://news.ycombinator.com/item?id=32117175

Oh I do hope not. As Dr Johnson said, "when a man is tired of mocking Microsoft, he is tired of life".

Re: The Case for C# and .NET

#375
post #163

Earlier quoted context omitted.

> that the official repo can only "unlist" packages, not delete them or that the publish times sometimes have horrible delays It's to avoid the npm left-pad problem. nuget.org packages are idempotent. For the publish times, I found out you can cut it in more than half if you tell nuget to ignore caches.

Idempotent, in which way? Do you perhaps mean immutable?

Yes, sorry, I meant immutable, not idempotent.

Re: The Case for C# and .NET

#376

There are 171 posts at the time of writing, only one (this one) includes the character ♯

Will you tire of posting about this stupidity? https://news.ycombinator.com/item?id=32117175

You don't think something being hard to input can be blamed on the OS at all?

The only built-in way to type a sharp outside wordpad is to have a special registry key set then hold alt and type +266F, isn't it? That sounds to me like it falls under "dreadful support for Unicode".

Post reply on HN