3 ms·
I've been working with .Net from day one on large high traffic projects. No. It's overcomplicated, moves so fast that the maintenance overhead is insane, the o
by cjk2 3y ago
I've been working with .Net from day one on large high traffic projects.
No. It's overcomplicated, moves so fast that the maintenance overhead is insane, the open source ecosystem is incredibly volatile and immature and the attention of Microsoft is akin to a schizophrenic monkey. The tooling provided by Microsoft is buggy and unreliable and half the platform abstractions (certificates for example) are fucked up messes which cause endless deployment problems. Not only that you're working in a graveyard of abandoned projects and frameworks and legacy 3rd party components you still depend on because Microsoft sold everyone the ideology and then threw it out of the window or changed direction rapidly.
Oh and don't get me started on C# which started off reasonable but is now the car Homer Simpson designed https://simpsonswiki.com/wiki/The_Homer https://simpsonswiki.com/wiki/The_Homer
All this shit however did pay my mortgage off.
- criddell 3y agoIt’s possible that everything you said is 100% true and it’s miles ahead of everything else.
- cjk2 3y agoYou’re not wrong from a historical perspective. It was that or PHP for me. I chose well. I would not choose it now so I don’t think it holds any more. Go will become the next .net in 20 years.
- lawn 3y agoLogically possible yes, but that's not the reality.
- dagaci 3y agoHaha, thats exactly i thought! But my experience is the opposite of everything he said!