mrsmrtss

7 ms·

1.
by mrsmrtss 4d ago
Agreed on async. You better know if a function does IO, hiding that can lead to nasty surprises.
2.
by mrsmrtss 3mo ago
> JavaScript is faster than C# Are you joking? C# is in another leage, when we talk about performance.
3.
by mrsmrtss 4mo ago
That's not how TDD works. You test the whole chain and all the components with tests and you can move from top to bottom with TDD, it's actually how you should do it.
4.
by mrsmrtss 4mo ago
> while if you wrote it exactly like Java, you'd probably end up with slower code. That's not the case for some time already, at worst you get similar performance with Java and with a little effort you can get significantly bet
5.
by mrsmrtss 4mo ago
I don't get what the big problem is with function coloring. You basically only need async when doing IO, and you had better know when a function does it, or you may have a bad surprise at some point in the future.
6.
by mrsmrtss 4mo ago
Maybe startup time was a problem before AOT?
7.
by mrsmrtss 4mo ago
So you try to say that Java gets to be more semantically sound by making bad choices early on? That does not make sense. Those choices are very difficult fix today and many of them can't be fixed. Say what you want but semantically mor
8.
by mrsmrtss 4mo ago
For almost 10 years now, we have not published anything .NET to the Windows platform. .NET is more performant on Linux today than Windows, and I would say development is also better there (using Rider). However, we do still have devs who pr
9.
by mrsmrtss 4mo ago
As if C# is Windows only? Today C# runs also almost everywhere.
10.
by mrsmrtss 4mo ago
C# (.NET) would probably be the winner here. Go standard library is rather minimalistic compared to it.
11.
by mrsmrtss 4mo ago
Fun it is not. if err != nil It's amazing how they managed to design a new language with all the flaws of '90s languages.
12.
by mrsmrtss 5mo ago
C# will have more advanced sum types this year, it's currently in preview.
13.
by mrsmrtss 5mo ago
Well, C# has more powerful pattern matching, only compiler exhaustiveness on types is missing today. In Java, sum types (sealed interfaces/classes) require all members to have the same parent, so they can be used only in very narrow ca
14.
by mrsmrtss 5mo ago
Reified generics, value types, nullable reference types, LINQ are only some of the things that would give C# an edge in DevEx today.
15.
by mrsmrtss 5mo ago
If you work with old .NET Framework, then maybe I would agree. What kind of issues do you have in standard library or how they are only biting you? Nothing is perfect, but compared to other (popular) alternatives, C#/.NET is the best y
16.
by mrsmrtss 5mo ago
Exactly, we have had many interns with zero C# experience become fluent in a couple of months and those with prior TypeScript or Java experience get there even faster. A good IDE (like Rider) helps also.
17.
by mrsmrtss 6mo ago
Maybe this is why they retired Single Server PostgreSQL and are now offering only the new Azure Database for PostgreSQL (flexible server). Zero problem with the latter for us so far.
18.
by mrsmrtss 6mo ago
I see that it's fashionable to bash everything MS related in HN, but let's not pretend that the other major cloud providers don't have their own problems (e.g. https://www.ft.com/content/7cab4ec7-4712-413
19.
by mrsmrtss 6mo ago
Fully agree with this! I think today .NET is probably the most batteries included platform you can get. This means that even if you use third-party libraries, these typically depend only on first-party dependencies, making it much less like
20.
by mrsmrtss 6mo ago
Autoboxing is more a Java problem mainly because of type erasure with generics. C# has "proper" generics and no hidden boxing is occuring there.
21.
by mrsmrtss 6mo ago
I think that goes for any major cloud provider, not only AWS. But nothing is free, you pay a hefty premium to get this (compared to plain infra providers like Hetzner for example).
22.
by mrsmrtss 6mo ago
Add WarningsAsErrors for prject and you are done.
23.
by mrsmrtss 6mo ago
I had the exact same thoughts reading it.
24.
by mrsmrtss 6mo ago
True, it's in preview currently, but actually .NET is already very efficient with async today also - https://hez2010.github.io/async-runtimes-benchmarks-2024/ (.NET9 tested here).
25.
by mrsmrtss 6mo ago
In .NET 11 C# async management moved to the runtime, mostly eliminating heap allocations and also bringing clean stack traces. You really only need to think about ConfigureAwait(false) when building shared libraries or dealing with UI frame
26.
by mrsmrtss 7mo ago
No, it's not, it's a SQL builder.
27.
by mrsmrtss 7mo ago
> I favor a more functional style of programming and C# ends up making everything 5 times more verbose than Kotlin. As if you can't program C# functional style.
28.
by mrsmrtss 7mo ago
Care to elaborate what problems you have with .NET package manager (Nuget) and build process? I think having a single way of doing things a is in itself a big bonus compared to the situation in Java (Maven vs Gradle).
29.
by mrsmrtss 7mo ago
.NET, VueJS, and PostgreSQL are also my preferred stack today. For back-end development, C# .NET is a super productive and performant stack, and it would be foolish to disregard it.
30.
by mrsmrtss 7mo ago
The Benchmarks Game has some highly optimized implementations and is not a good representation of typical code. Some languages allow you to go a lot lower than others if needed, which adds verbosity, that does not mean typical code must be

More ›