Experienced Devs

4008 readers

13 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

snowe

jmk1ng

drewsiferr

-17

Why enterprises use .NET and C# technologies? (lemmy.one)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/experienced_devs

26 comments fedilink hide all child comments

I looked for Senior Software Developer positions, and one of the things that I've noticed is that lots of enterprises look for people with experience with technologies such as .NET and C#.

I personally HATE Microsoft and their platforms. From my experience they take all the fun from developing by creating stupid compile errors with their stupid gigantic Visual Studio and buggy dependencies. Not to mention their ridiculous resources greedy and unsecured Windows OS! Also there are no healthy and independent communities around a their technologies. They don't open source much of their technologies so it would be easier to hack their tools, and harder to make security patches.

Why enterprises do that for themselves and for their developers?

Do you think enterprises will make a turn in this attitude?

you are viewing a single comment's thread
view the rest of the comments

[–] Buckshot 5 points 1 year ago

I'm working on migrating a lot of old .Net Framework code right now, we're generally going with a complete rewrite but that's more to do with poor architectural decisions and the fact a lot of it is VB rather than C#.

It's pretty impressive that code largely written up to 20 years ago is now running on a modern OS, and it's using the latest Framework 4.8 with all the latest security updates and I can open VS2022 and hit run and it builds and runs fine. Our issues are the maintainability of the code and how it was written rather than the framework itself.

Meanwhile, a few years ago now, I had a web project written in typescript, it was only about a year out of date and npm install failed. Turns out one of dependencies needed to build something with python2, updating that needed a new version of webpack and that broke something else that never got an update to the newer webpack. Installing python2 didn't work either I think but I can't remember why.

There's systems I wrote for .Net over a decade ago that I can guarantee are still running in production and haven't been touched in all that time.

In short, I think I'm agreeing with you. It's painful but it's possible.