this post was submitted on 13 Nov 2024
836 points (96.1% liked)

Greentext

4459 readers
730 users here now

This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.

Be warned:

If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Serinus@lemmy.world 52 points 1 week ago (19 children)

C# is nearly the same, but much, much better.

  • It doesn't (usually) come with the Java culture 8 layers of abstraction. This isn't in the Java language. This isn't in OO. Yet nearly every Java programmer makes things way more complicated than it needs to be.
  • It's a prettier language. Similar syntax with less bullshit.
  • It's open source
  • It's still multiplatform. Modern dotnet / C# works on anything.
  • Both Visual Studio and Visual Studio code are great IDEs that blow Eclipse out of the water
  • It's one of the most common business languages.
  • It's going to be supported forever.

If I could restrict the world of programming to two languages, it'd be C# and Rust. C# for most things and Rust for a lower level language.

[–] PlusMinus@lemmy.world 8 points 1 week ago (11 children)

Nah, C# suffers from a lot of the same shit Java does. Needing everything to be a class is just no longer a good design choice (if it ever was). AOT support is still lacking. I don't get, why it does not have typdefs. I think the solution / project structure is unnecessary and I could probably think of more stuff I dislike about C#. But imho, it still beats Java.

Golang is my choice over C# any time. I strongly prefer how interfaces are handled and I actually like the error handling.

[–] Serinus@lemmy.world 15 points 1 week ago (1 children)

Needing everything to be a class

In 2015 they added scripting. If you're making a real project, you should absolutely use classes. (It's not that hard. Don't do the Java shit.) But you can absolutely write one off scripts just fine.

AOT support is still lacking.

Publishing your app as Native AOT produces an app that's self-contained and that has been ahead-of-time (AOT) compiled to native code. Source.

[–] PlusMinus@lemmy.world 5 points 1 week ago

I think you misunderstood my post. I am quite proficient with C#. I just think other languages do it better.

AOT is not where it should be yet, because not all libraries have full stripping support.

load more comments (9 replies)
load more comments (16 replies)