I really dislike C#'s naming convention of UpperCamelCase public fields but I also don't want to change it for my own projects. After all, when in Rome do as the Romans do and all that

Arghh, I hate decisions ;~;

Do as the Romans. Orgies and upper case. And communal ass wipe sponges. I think they got at least one thing right.

Yes! Exactly what I dislike about C# also. Glad I‘m not the only one.

I dislike public fields.

@retoor I'm always a quick shot, hah ladies? ;)

C#:
"You want a public property and name it the same as its type? Well fuck right off then!"

@Lensflare

The only proper way C# should have handled class types is prefixing them with T. TCustomer, TString, etc.

And don't get me started on why C# (or any programming language) has to be case-sensitive.

Replace all that {...} nonsense with with begin...end

That's the start of a beautiful language.

@PaperTrail lol
Disagree on everything that you said 😂

> Replace all that {...} nonsense with with begin...end

I just threw up a little.

@PaperTrail I have to agree with Lensflare on this one lol

Fucking romans.

GERGOVIA LII NEVER FORGET

@PaperTrail Just go do some basic or cobol or something equally stupid

@Lensflare > "I just threw up a little."

Delphi forever!!! :)

@retoor > "Also, it's for performance better."

I think it was to pander to the C/C++ crowd.

Language compiler performance hasn't been a thing since the 90s. Delphi/Pascal, Visual Basic, etc proved that over and over again.

Only benefit is in the extreme, like compiling Apex Legends/Call of Duty, which you wouldn't use C#/Java/etc anyway.

No one should be thinking 'I'm going to convert my C# business app to C++ so it compiles faster!'

Also because the concept of what "not case sensitive" actually means is a total headfuck.

@donkulator why is it a headfuck? It appears pretty straightforward to me. I‘d hate it but it doesn’t confuse me.