Hi C# guys out or everyone else too,

I found this in an StackOverflow answer: https://docs.google.com/document/d/...

What do you think?

Yeah yeah we've heard it a thousand times. VMs aren't fast enough blah blah garbage collection bad, bytecode too transparent. As a java dev I probably hear this around 10 times a second. No, the languages are fine. Garbage collection is great. If you need absolute performance, use C or C++, else C#/Java are perfectly fine especially for "business" applications (i.e. everything that isn't low level)

Also this is fucking retarded

"If we pick up random two developers - one who knows C# and another who knows C++ - I would guess that C# developer would be a little bit faster than C++ developer. But as project grows larger - project scalability becomes a problem. And by scalability I mean - application development performance (how quickly you can launch your application), how much ram your application consumes - after some time C++ developer will win eventually C# developer."

If language is ever a problem in industries, then people won’t use JS as backend, instead everyone use C or C++

As someone who started out in Java, moved to C# and is now using GML and Vala, C and C++ are great and have advantages... But not everyone has the time to build everything from scratch when we have stable, easy and (arguably) better alternatives?

When people claim performance is the #1 key and they aren't coding directly in machine code doesn't care about performance as a #1 priority (yes I know this is over-exaggerating but you get the point)

@lxmcf With C++ compiler optimizes your code so you don't need to write in machine code. One exception - you want to use MMX or SSE to boost some of algorithms. But in our C++ project there is only one place where we use Assembler - in media processing

A lot of baseless speculation in that post. Also cites needing to learn new language as though that was unexpected or difficult for anyone with basic OOP knowledge

He says that c# is compiled to machine code upon execution? What is the VM for then?

@AlgoRythm .NET applications still need CLR to load assemblies, manage types, JIT-compile IL and manage heap. IL compilation just allows to make program execution faster (as opposite to byte code interpretation)

I clicked the thing I most disagreed with and they were blaming tools unrelated to the issue (visual studio being slow)

I stopped reading after that because first of all it's not slow (besides boot up) on my 8 year old laptop. Then there are also other editors one can do the exact same.

All 10 are false.

Select one and I'll explain why with no problems

@NoToJavaScript I agree with you in disagreeing with all the points. But the point I am interested in is the large scale project point. What do you think about that?

PS: I like your username.

@12bitfloat Not the only thing retarded in the document

@devTea There is a reason not everyone is using C++ or even C. Some just dont want to agree it I guess

@lxmcf I think in todays app development performance is the least important point on the list (sadly).

@Gxost I read somewhere they are working on AOT compilation.

@hypervtechnics they only use C or C++ on some specific tadk in the app, not every logic or transactions. Same reason SP is superior to ORM, you just don’t optimise everything