You are viewing a single comment's thread.

view the rest of the comments →


[–] 00001000001100110101 0 points 21 points (+21|-0) ago 

As someone who used to develop in .Net, let me be the first to say fuck that language. Their have been so many revisions to it in the past 2 years alone, no one can fucking keep up anymore. Anonymous tuples? Metadata programming? Dynamic Expando objects? Reflection based programming by assembly? Why doesn't .Net stick to one construct, instead of merging Javascript, Python and misery into .Net. IT was a great language, but let's just re define properties for the lulz. Let's also do dynamic reflection on DLL files, and ignore access modifiers through binding flags. Like WTF?! Doesn't that negate the entire point of access modifiers?


[–] alphasnail 0 points 10 points (+10|-0) ago 

They apparently missed the memo that sticking to one method and perfecting it is the route to go. Shame. Could have been a good thing.


[–] 00001000001100110101 0 points 7 points (+7|-0) ago  (edited ago)

It really could have. Then they decided to create .Net framework and .Net core, and make it uni directional compatible from .Net Core -> .Net Framework but not the opposite way(It may be opposite, but the point still stands). So if you start off with the wrong class type, you have to recreate the entire project, and this doesn't become known until after two libraries are created. Then the wrapper libraries for core are called XX.Core.YY, not to be confused with .Net framework libraries, which have the XXCore.YY notation...

Edit: Also python and Java for the most part work out of the box and are platform independent. .Net added that feature AFTER the initial implementation, so it's all over the place.


[–] Shilly_Mc_Shillface 0 points 1 points (+1|-0) ago 

used to develop in .Net, let me be the first to say fuck that language

You don't have to compile.



[–] glassuser 0 points 1 points (+1|-0) ago 

YOU don't, but it's still compiled.