C# has become shit.

I work since 2013 with C# (and the whole .NET stack) and I was so happy with it.
Compared to Java it was much lean, compared to all shitty new edge framework that looked like a unfinished midschool project, it was solid and mature.

It had his problems,. but compared to everything else that I tried, it was the quickes and most robust solution.

All went in a downhill leading to a rotten shit lake when all this javascript frenzy began to pop up and everyone wanted to get on the trendy bandwagon.

First they introduced MVC, then .NET Core, now .NET 5-6-7-8.

Now I'm literally engulfed with all these tiny bits of terror javascript provoked and they've implemented in all the parts of their framework.

Everything has to be null checked at compilation time, everything pops up errors "this might be nulll heyyyyy it's important put a ! or a ? you silly!!!" everywhere.

There are JS-ish constructs and syntax shit everywhere.

It's unbearable.
I avoid js like a plague whenever I can (and you know it's not a luxury you get often in the current state of a developer life) and they're slowly turning in some shit js hybrid deformed creature

I miss 2013-2018, when it wass all up to me to decide what to do with code and I did some big projects for big companies (200-300k lines of code without unit tests and yes for me it's a lot) without all this hassle.

I literally feel the need c# had to have some compiler rule you can quickly switch called "Senior developer mode" that doesn't trigger alarms and bells for every little stupid thing.

I'm sure you can' turn on/off these craps by some hidden settings somewhere, but heck I feel the need to be an option, so whoever keeps it on should see a big red label on top of the IDE saying "YOU HAVE RETARDED DEV MODE ON"

So they get a reminder that if they use it they are either some fresh junior dev or they are mentally challenged.

  • 1
    two lines in and I hit the ++ button
  • 1
    @aviophille Lot of people do


    Wake up
  • 0
    Nice rant. Sadly, I didn't use C# for a long time so don't have comparison material. I just hope it gets big on linux because it was always much fun to write
  • 0
    Java will never die i will fight for java forever
  • 0
    @retoor c# is a lame ahh goofball language created by pedophille bill gates who gangbangs little kids in assholes at the epstein island
  • 0
    i haven't used the latest 7-8. but .net core felt like the best thing that happened to .net.

    Nice syntax, good docker support, truely cross OS. Cross platform libraries.

    All very nice things.

    But I can definitely see the issue with nullable checks during compilation. Aren't these warnings though? So they can be ignored?
  • 0
    I like C# and most of the new styles are rejected by style checks in most of my projects anyway.
  • 0
    Has become? It has always been.
  • 1
    if you look at c# and see javascript-elements, you should really go visit your eye doctor.
  • 1
    Id disagree
    C# has always been super strict with nulls

    back then, nullable wasnt a thing unless you wrap it in Nullable etc

    Now it's a normal type and hence the excessive checks, it's nothing to do with JS
    Without these "u sure it's always not null?", we'd see way more unintended errors and at server-side, that's unexpectable
  • 0
    Just add <Nullable>disable</Nullable> to your project file and stop complaining.
  • 0
    I also fail to see what elements of js it has adopted.
    It’s was and still is very far away from js.
  • 3
    @superdupernova of course not, everyone knows Result<T, E> is the only way to do things properly.

    Embrace Rust, let it take over your codebase, rewrite everything in Rust and become one of us, one of us, one of us, one of us, one of us, one of us
  • 0
    TBF that null crap came out of Rust
  • 1

    Like the whole world is not complaining about js.

  • 0
    @superdupernova Unless you have been hired yesterday out of school, no they aren't.

    You do them when you need them
  • 0
    @tosensei If you don't see them, you should really read a book about javascript and one about C# so you can learn those languages
  • 0
    @Lensflare The same happened to your programming career apparently
  • 1
    @IHateFrameworks subtract those elements that BOTH have inherited from C, and you've got no commonalities left.
  • 0
Add Comment