Thread replies: 6
Thread images: 2
Thread images: 2
File: 1471743416857.jpg (60KB, 500x600px) Image search:
[Google]
60KB, 500x600px
Why is .NET/C# so shit? If you want to do any sort of optimization you need to drop progress of .NET all the way back to 2005.
(P)LINQ? shit
Enumerators? shit
Compiler optimizations? non existent, even for basic stuff like using same reference inside a local function
WPF MVVM? shit
You end up with async/await C without having to worry about malloc if you want any sort of high quality/speed code.
Look at this shit http://www.actiprosoftware.com/products/controls/wpf their DataGrid control drops FPS even while resizing, my custom data grid can have 1000 threads accessing and writing data to it, no lag while resizing, 60+ FPS, yet they charge $800 for it, INSANE.
>>
>>58849947
>not knowing how to apply yourself with Oracle
>blaming the platform for your own diaper shitting shit eating under performance
>>
>>58849947
>He fell for the C# meme
Dude come on, it's 2017. Hit the C book or C++. Or at least Rust
>>
>>58850033
I never said I don't know C/C++.
I read entire 5k pages of Intel x86 manual. I just happen to be developing in C# and when I check ILDASM/ASM output i want to kill myself.
>>
Because the "people" that use it are shit.
>>
File: 1465887734989.gif (480KB, 493x342px) Image search:
[Google]
480KB, 493x342px
.NET doesn't need compiler optimizations for the high level language since it automatically optimizes in MSIL.
Also async/await is just the automated/easy way to spawn threads for methods. You could easily just manage the threads yourself like with any other language.
And MVVM is a pattern that you don't have to use to develop windows applications (I agree it's shit).
Ive never used the data grid control, but why would I need to when I can write my own grid control? It sounds like you're complaining about some of the default features of .NET which is akin to complaining about Java's swing libraries.
Thread posts: 6
Thread images: 2
Thread images: 2