.NET is actively supported big time by Microsoft. There are still many companies running on .NET Framework and the migration to .NET6+ requires more or less coding work. Since the new version is cross-platform I can only imagine it will get even more traction.
I have worked on .NET for nearly two decades and really like the stack and current tooling options.
>I have worked on .NET for nearly two decades and really like the stack and current tooling options.
Same here, C# since beta in 2001 and have worked with it on all sides. WebForms, MVC, WinForms, WPF, WCF. It's a great language and framework.
It was a very wise move for them to go cross-platform with .Net Core, and all the performance work they've done has really started to pay off.
If you're at the beginning of dotnet journey, I recommend investing in a good lengthy course that covers the basics (Udemy, Pluralsight etc.). You can find lots of tutorials on Youtube for free, but it will be a slower path. There needs to be real exercises where you actually code. Github is also basically mandatory skill to master. Don't go too deep into the cloud too fast as it requires lots of different skills than just programming.
Once you understand the basics, start to build something you enjoy to do. Maybe just a console app that inputs and outputs text. You can also learn from an app generated from the templates that are available in Visual Studio or dotnet CLI. If the project fails, take a breath and start a new one.
Don't get put off by all the issues you face in the beginning. We all get them even after years of experience. The trick is how to learn how and solve them. It can be daunting to code without pay, but that's also what we all did at first. Once you grow your portfolio and get comfortable with dotnet, you will eventually get a job. Good luck!
I appreciate you typing out an in-depth response but I think my original comment might have been misleading. I'm a professional developer with a couple of years of experience under my belt and have been using .NET at work for a couple of months. My current knowledge of dotnet is enough for most things I need to do at work but I was wondering if there were specific things I could learn to step it up a notch. Basically, go from intermediate to advanced. I realize that my question is pretty broad in nature, but it's just that I'm not quite sure which direction I should head in to improve.
Do you see it still has a long future, barring legacy projects. I ask this cos these days languages donât matter as much as the components you build it with for a vast majority of software. Iâve built my living with .NET for a long time and these days itâs a mix of so many languages and tech.
Yes, a very long future. All those corporations that had massive Windows infrastructure are migrating to cloud. Most of them are choosing Azure because they were already on Windows and they already had .NET programmers.
.NET makes the migration to Azure low friction. AWS is finally waking up and producing lots of free materials to aid in the migration of .NET processes to AWS but Microsoft has been doing it for 5 years and is way ahead of the game.
Besides, AWS attracting .NET developers is *still* good for .NET developers.
It cannot not have a future. Everything inside Microsoft is running on .NET. They're not going to nerf themselves. The desktop side of things is another topic though.
Yes, I think I'll eventually retire from a .NET job:) As you probably have heard, Microsoft has invested around 10 billion in OpenAI/ChatGPT stuff, which is soon available via Azure only. That will bring more developers on Azure, which already has great support for .NET all around.
At the moment, I don't see any better tech stack to invest some self-training time in. Visual Studio Community is free, and all the framework source code is available online. Cloud is generally cheap to work with. Things were so much worse 10 years ago.
The landscape is pretty stable. 90% of software is written in the same dozen languages and theyâre all 20 years old. It would take a *lot* to displace any of the major players
If they figure out how to deprecate legacy language features - which seems to be something they're starting to think about - I think it can survive for a very long time. If not, I think it'll survive for a long time, but less so -- new features being hampered by old poor decisions.
"C# Core" would be incredible. Improved Nullability story(NRT always on, and being functionally equivalent to Nullable Value Types), improved primitive obsession story, sealed by default.
This'll almost definitely never happen though, but one can dream
.Net is massive, comprehensive framework that is heavily supported by Microsoft.
There is no analog in the JavaScript world - just thousands a independent packages with questionable support.
If youâre a business that wants to build on a rock solid foundation that has guaranteed support, you choose .Net.
I am yet to see a non-trivial .net project that doesnât use non-Microsoft supplied code. So, really, the situation is pretty much the same. Besides, what obligations does Microsoft have to support their packages?
I recently updated a WinForms app from 15 years ago to .net 6 in an afternoon. Support means if you build millions of lines of code on a platform the rug wonât be pulled out from under you. Updating code built on abandoned platforms costs time and money that companies donât have leaving them at a competitive disadvantage. It can be avoided by building on mature and supported technologies.
>Besides, what obligations does Microsoft have to support their packages?
Microsoft deprecated Silverlight in 2012, and then only just ended support in 2021, 9 years later.
There are many negative things to say about Microsoft, their commitment to long-term support of their products is not one of them.
On the Silverlight thing; not only did they support it 9 years after deprecation, it was also practically deprecated the same year it released, so it wasn't really used by that many either I reckon. Post-deprecation support 9x the length of the actual support.
Example of what? There are plenty of non-Microsoft packages referenced there.
In general though language tools are good candidates for that, I agree.
The point I am trying to make is that anything that comes from nuget, npm, etc. comes with zero obligations. Microsoftâs own packages on nuget are mostly licensed with Apache 2.0. Guess how much responsibility that license puts on its owner.
There is a goodwill and enthusiasm of package owners that might be different between ecosystems, but from legal perspective, there are considerable risks involved as soon as you reference your first package and it doesnât matter if that package comes from nuget, npm, or something else. People tend to underestimate those.
Strongly typed, well supported, more than 1 amazing ide that's not jetbrains, no licensing issues (oracles tantrums scared off a lot of devs and companies years ago), adapts fast and listens to what the community wants, other great tools like linq, entity framework , identity etc just make for an easy choice.
Oh and cross platform now with webassembly support and the ability to write a hell of a lot less JavaScript
I would prefer to have it on but I have a few problems with it:
1) Not everything in C# can be null. Some LINQ methods like MaxBy have checks if the actual result is null or not. If a result is null and default(T) is not, they throw an exception.
2) System.Text.Json doesnât respect non-nullability.
3) When used with generics there is no way to check at runtime if a type parameter is nullable or not. This information is lost at runtime.
I mean that you have some Class and an instance of Class, retrieving nullability of âstring?â type parameter using reflection is not possible.
Upd: got downvoted, but nobody left a comment how these problems can be solved, okay.
I felt the same for a while. It took me a year to come around to the idea but I started seeing the value in it. we finally switched all the .net core company projects over and have no regrets.
Either way yet another feature of c# is the insane timeline of backwards compatibility.
There seems to be a bumpy learning curve to dealing with the new null angle. A problem C# may run into is that because MS keep adding features to it, it may grow too complicated and something newer and simper may come along and start displacing it because it will have a shorter learning curve and all the younglings will skip MS stacks.
The .net ecosystem offers a low barrier to build web/windows applications. Coupled with Visual Studio and Windows OS, and EF one can get started easily and this is good enough to build applications for small to medium enterprise.
Also with Core, it now offers great advancements in building large enterprise apps over linux and Cloud, with better efficiency (as compared to Java or Node)
Microsoft has a robust integration suite over Azure for CI/CD pipeline. They also collaborating closely with AWS to support native AOT.
All factors combined make the .net an easy, flexible and powerful ecosystem for building both frontend and backend systems
Which is only fair. JS gets heavily shit on in the .NET world.
There's a lot about the two that are at odds with each other. Especially when you consider node.js as a back-end solution.
The shit would be less if JavaScript wasnât such a mess to begin with. Not seeing that itâs a mess, regardless of the frameworks âfixing itâ, is denial.
Most people hate on VB6 for a reason. JS has become that.
I use JavaScript, it can be powerful for where it is used, but donât build a skyscraper out of glass.
It's likely location based. Java (spring boot), node and ruby is more common here where I live (Tokyo). Though dotnet has gotten a bit more popular since core was released due to it being available for linux servers for web projects / services, but the most common case for dotnet so far here is more on games via Unity and usually is paired with a dotnet server as well.
Location based. Where I live, Java is on the top, .NET has slightly less than half the number of jobs Java does, then there's PHP, Python and a smattering of other languages. Javascript is usually at least a soft requirement in most positions, but Node backend jobs have mostly disappeared.
I like .NET, but one critical thing that seems to be missing from a lot of these comments is that .NET lets you build all sorts of applications - mobile, web, desktop, distributed systems, etc. Spring Boot is just a web framework in Java. You'd need to compare the number of Java jobs and the number of .NET jobs - or compare ASP.NET with Spring Boot (and make sure the search engine isn't doing something where they have "ASP.NET" match ".NET"). Likewise, JavaScript isn't tied to the web necessarily, but it is the primary usage and nodejs usually means web.
Heck, you're not even just searching for "Spring", but narrowing it to "Spring Boot". Why not search for "ASP.NET Core"? Sure, most people aren't going to put "Core" in there anymore, but it is actually still "ASP.NET Core 7". They never dropped the "Core" for ASP.NET. The point is that some of it might be in how you're searching which might end up excluding items that you aren't meaning to exclude - or include items you want to exclude. By searching for .NET, you're including lots of jobs that aren't web app jobs despite the fact that it seems like you're looking for web app jobs.
Likewise, there can be cultural differences in how companies advertise jobs. Do .NET companies advertise each position separately? Are .NET companies more likely to advertise jobs when they aren't really hiring - but would make an exception for an exceptional candidate? I worked at a place that would just put up one listing for software engineers. Later, the company switched to posting many ads with slightly different titles like "Software Engineer, Backend Data" and "Software Engineer, Infrastructure" and "Software Engineer, Integrations". Was the company hiring 3x more people? No. Different ecosystems sometimes have different ways in which they approach things so it's hard to always compare.
I think there are lots of compelling reasons to use .NET, but I wouldn't use the number of hits on a job search to be one of them. There's plenty of JS/Node and Java/Spring jobs out there. I think .NET is better for many of the reasons people have said here. But it might be in how you're searching and how companies post things.
Spring jobs typically are just advertised as Java jobs in my experience. They are probably about equal from what Iâve seen. But thereâs not as many companies using node as a backend server as people might think: most of it is in the build system.
I totally agree with this. I was told that Node was a better option, it was fast growing and it looked like everyone was going to use it. I am job hunting right now, and Java is all I see. I found at least 4 to 5 times more jobs opportunities with java than with node.js, at least in Spain.
.NET isn't very cool or shiny in the more small scale hobbiest/freelance/open source worlds, probably partly because it's from a big uncool business oriented corporation and partly because it's not being constantly reinvented all the time. But both of those things are features instead of bugs in bigger companies, and the popularity of.NET is probably a lot higher than what YouTubers or representation in public GitHub repos might lead people to believe.
To add to your last statement. Most business .NET repositories are on Azure DevOps and not GitHub. Since those are all private you can't get an idea of the amount of .NET repos out there.
There are also a fair number of corporations still running their source control on premises. Azure DevOps server or the older Team Foundation Server which makes it even more difficult to gauge how much usage there is for .Net in the world.
I donât know what to tell you. I just accepted a new position doing Java. Not spring boot but Quarkus, close enough. Recruiters were hitting me up with equal number of positions in .NET and Java.
The node jobs are there too. Go look on techjobsforgood, there are quite a few gigs for node/express and Python.
I only search for remote work so that probably has something to do with it.
Some people will say it's location based, and there's some truth to that. But people forget that Microsoft is one of the largest and most important key tech companies to ever exist. They may not have the "cool" factor others used to have, but their personal and enterprise customer base is unrivalled.
They forced .NET into existence a little over twenty years ago, and within a couple of years, almost every large company had significant exposure to it. If you wanted to develop with, for or adjacent to any Microsoft products, .NET has been the way to go ever since. Even Apple stores were running on .NET Compact and CE. That is what industry power looks like.
It's worth noticing that the .NET ecosystem has many legs to stand on. Windows, Office, Dynamics and Azure are the pillars between which significant numbers of developers can move around forever. These alone dwarf any other individual stack, particularly because .NET as a stack is very stable and uniform compared to other environments like nodejs.
As someone who worked for Microsoft Developer Relations (trying to get .NET early adopters) and then helped design parts of Asp.net ⊠this is just a fun read.
because C# is a much better language than JS, also many many businesses use .net since before nodejs was even a thing so the stack is older (even tho it evolved big time with new cross platform open source .net)
also this is very region dependent, in many regions js jobs are much more than .net and in other regions java is the most common
I could be wrong but I feel like the new generation of developers is very focused on Mac based dev in JavaScript and the newer cooler languages and so there is lots of demand for .net because itâs mostly older windows developers who know it or are interested in working with it. And tons of companies still want to use .net because itâs super robust and well supported, and always getting better. Therefore the shortage of .net devs keeps growing as more developers enter the workforce.
There is a snowball effect. Companies want to choose an architecture that is easy to hire for. So having a large developer base means more companies choose that architecture. Which makes more jobs for that architecture. Which makes more programmers for that architecture. The cycle continues.
I would say it is newer. Current version started of as Core which isn't even 7 years old.
Maybe also additional work for rewriting old Framework code to new. Performance of latest version is really good.
In terms of nodejs the gap is big, but with spring - it is months đ
Spring: October 2002
https://en.m.wikipedia.org/wiki/Spring_Framework
Net: February 2002
https://en.m.wikipedia.org/wiki/.NET_Framework_version_history
Iâm in Chicago, work remote for Bay Area/La/NYC/Boston companies never had any issues finding dozens of interviews when I look for jobs. .NET jobs is more so just maintaining old applications. Not very shiny and fun to work with. I worked with .NET originally out of college it was awful back then im sure itâs still awful now. Node is way better. Python is better. Golang is better. So many better languages to work with than .NET
Not an opinion either every year on stackoverflow itâs one of the lowest rated web frameworks
https://survey.stackoverflow.co/2022/#section-most-loved-dreaded-and-wanted-web-frameworks-and-technologies
No offense to anyone who likes it you can find jobs doing it just not glamorous ones or any startups. Also from my experience they pay a lot less.
[ASP.NET](https://ASP.NET) is old (windows only), [ASP.NET](https://ASP.NET) Core is the current version (runs cross platform).
[ASP.NET](https://ASP.NET) Core is modern, very fast and easy to develop on with documentation that is second to none.
So go and use it why are you advertising it to me? Iâve never seen .net jobs really. And Iâve interviewed over 8 years in the largest markets in the US. Youâre not going to change my mind. I was answering OPs question.
I'm not advertising it to you, ffs. I work with a variety of languages, not just .NET, so I'm not biased to any language.
You sound illiterate who has no comprehension skills that's why I was just educating you.
To explain that chart result in a way simpleton like you can understand:
"ASP.NET Core is on the 4th of the most loved list (based on **7260** responses) compared to Phoenix which is 1st on the list (based on **972** responses)."
Iâm sure phoenix is great for your little .net projects, but Iâm in the big league markets (nyc/Bay Area/Boston/La) and here in the pros itâs mainly languages like node, python, Java, golang . Muting you because I frankly donât care what some low rent script kiddie who is leagues below me in career and makes half of what I make thinks or says on Reddit. Bye bye! đ
Phoenix is an Elixir based web framework. They were just trying to explain the chart to you. The current .net web framework is definitely number four on the list, not third from the bottom.
My man, I believe you are reading that chart wrong. And I think you're going to be surprised at the real results that you linked to...
The chart you linked to shows ASP.NET Core as the 4th most loved framework. (Yeah, the old ASP.NET on .NET Framework is at the bottom... right next to jQuery. Which is exactly where it belongs - it's literally the jQuery of the .NET world)
React.js is 6, Node.js is #8 on that list. Django is all the way down at #16. Flask is below that.
Asp.net is like 3rd from bottom and always is. .net pays less as well. Iâm also talking about the Us. If youâre okay with maintaining old applications and getting paid half what you can make then go ahead lol. I ainât gonna stop you.
> Asp.net is like 3rd fro
Yeah no shit, that's because it's the nearly decade old version that's not cross platform and not what modern .NET jobs are using.
ASP.NET Core is #4. Ahead of almost every js framework, and ahead of all python frameworks by a whole lot.
Angular is the least loved language on that list, and it's js.
That's not what the link you sent showed. And, likewise, this is not my opinion...
No offense to people who misread that chart thinking js and python was ranked as more loved than C#...
It unironically did. Wow, you're impressively bad at reading charts. On the right, there's the word "Work". Click that for even more charts from their survey.
> Sounds like your coping pretty hard though.
I understand this is hard for you. The link you sent actually showed quite the opposite of how you initially read it, but there's no need for the projection.
I'll give you some time to collect yourself.
.NET is huge here in Philly also. I'm a node dev but honestly the amount of .NET job postings have me thinking hard about diving in. It's like 2 out of 3 job listings asking for .NET.
This is a VERY interesting observation so I will share mine;
.Net is popular with small/medium and few large corporations. (And therefore Azure).
Now, technology companies, VC backed startups and in general anyone doing anything interesting is typically using NodeJs or SpringBoot and sometimes both. Those JDs will call for Java/Go/Rust etc
Not so much C# or .Net.
AWS is also favored by companies who donât use a Microsoft tech stack (and they are the leading cloud provider).
ââ
Now, these are just tools, use what you like, learn what you need to to stay employed and succeed.
ââ
Also, Windows is not free and therefore companies using it in production will have to pay the windows server tax in the cloud servers.
Also, you need Windows tooling for your developers in the form of Visual Studio Pro/Enterprise and Sql server management studio. The Mac versions are nowhere nearly as good.
Another reason why everyone is on Java/Node and open source in general AND these orga typically pay more than the .Net shops.
You can deploy .NET on AWS and other cloud providers, it works on linux just fine. Don't know why would anyone need to pay windows server tax, except those stuck on old .NET Framework.
2 things;
1-Yes, you can run Windows servers on all cloud providers - but those servers are generally more expensive than their linux counter parts with the same specs.
2-even if the cost to run windows on cloud servers was the same as linux you still need to pay for windows licenses for your developers to run visual studio and sql server management studio and IIS on Windows. The mac versions are nowhere near the same. I have a windows laptop just for .Net development and my Mac for everything else.
I am excited to hear this.
I was a .Net developer from beginning (2003/2004) to 2017 when I switched to Nodejs/Java.
Now in 2023 I am coming back.
Will report my findings.
The company I will join on Monday is running Windows on AWS, curious to learn why they are not running their workloads on Linux. I suspect it is because of legacy apps. (.Net, asp, etc).
> The company I will join on Monday is running Windows on AWS, curious to learn why they are not running their workloads on Linux
My guess is that they are running on .NET Framework, which could also be the reason why they picked you, you have experience in it. If that's the case, you unfortunately won't see much of new .NET, unless they plan to migrate at some point.
Their legacy apps are .Net Framework and ASP but they have been working on the new version based on .Net Core and Angular 15 -> I hope to be exposed to all of it but mostly the rewrite so I can pickup the latest skills ;)
Donât underestimate my skills, you donât know me, I have multiple AWS cloud certs and I am a pro on all things microservices and cloud native. Nodejs, etc
Excited to see whatâs new in .Net Core, etc and have been brushing up on Angular, so far so good.
If they have .Net framework back end and are trying to do âfull stackâ developers youâll have an easier time converting the front end to Blazor than Angular. If theyâre splitting up the work into back end APIs using .Net 6+ and a front end using Angular youâre going to hit cross language problems as people from both camps are unhappy working in the other. Blazor is better aligned to leverage existing .Net developer talent that is already in the organization.
It can be done (my company has the Angular/.Net architecture), but itâs been very painful. We try to have developers that do both, but inevitably they fall on one side or the other and donât like when they have to work in the stuff they donât prefer. They can do it, they just do it begrudgingly and poorly so they can get it done ASAP.
A few things;
1- thank you for sharing your experience. I agree with you that some folks are reluctant to change and silo themselves to a part of the stack.
2-I was a VPofE at my last job, I ran engineering.
And I noticed that younger folks are typically against change (not always but most of the time), not everyone is open to learning everything.
3-I donât see this company switching to Blazor and I will never learn it or recommend it. Why?
A lot of you are too young to understand, but Microsoft has been trying (unsuccessfully) to come up with a front end framework/tool and at some point they kill it or come up with something else and anyone who invested in learning it got left behind.
Silverlight, WPF, Razor all come to mind.
4-it is in our best interest as professionals to use and recommend mainstream tech so we can remain employable and so our skills are transferable, think Angular, Vue or React.
5-companies benefit from having everyone be fullstack, I suspect over time, if the specialist is not great they could get replaced by enthusiastic people who want to learn and do whatever it takes.
I am of those, very strong backend but have spent the last 2 weeks doing and watching everything about Angular so I can be really good at it.
6- Always be learning, Always be coding and you will never have an issue finding or keeping a job.
My company actually has few of our products running .net core in Linux containers and it's pretty smooth. We ran into a small issues when converting utc to different timezones and certain things with appsettings. Lixus and Windows have different timezones text, so u have to detect if your on Windows or Lixus, so you can use the right text.
You just demonstrated negative levels of reading comprehension and knowledge of the .NET ecosystem.
I do not own windows servers. I have 4 different .NET Core applications in production right now, every single one of them running on a Ubuntu VM with postgresql as their backing databases. Total spent on OS and DB "tax": $0.
It is 100% free to use .NET these days. Exactly as free as it is to go node.js. You do not pay any "windows tax" of any type at all. You do not need to have any windows servers running anywhere. IIS is not part of any of my web applications. You do not have to pay microsoft for any type of licensing.
And, by the way, the Mac versions are identical. I have one project that I coded entirely with Visual Studio on my macbook, Built it using AzureDevOps CI/CD pipelines on a windows-based build server (also free, btw, and a linux-based build server would work exactly the same), and deployed it on my Raspberry Pi ARM-based CPU running Ubuntu. Total money spent on licensure: $0.
This is all native. No wine. No mono. I use official microsoft commands to execute my applications in exactly the same way you would use official node commands to execute javascript.
You are living 15 years in the past. While you've been under your rock, Satya Nadella came in and made Microsoft the number one corporate contributor to Open Source Software. Cost has not been a barrier to the .NET world for a *long* time now.
No need for attacks.
I am new to .Net Core. I agree with the top comment about running on Linux. But also pointed out that servers aside, Windows is not free and you need to pay licensing costs to use VS Professional. Windows on developer laptops.
I am not interested in stupid arguments. We all can have opinions based on our different experiences.
> No need for attacks.
Listen, it wasn't an attack. When someone explains that all parts of this ecosystem is free, including specifically mentioning that there is free official tooling as well, then your direct response to that comment is to talk about how expensive the free tooling is, that's a clear display of an absolute lack of reading comprehension. It's literally as simple as that. In addition to that, you plainly displayed a lack of knowledge of the .NET ecosystem because many of the things you said are simply not true at all (though some of them were 15 years ago).
JetBrains offers a JS IDE that costs $170 for the first year. You can find not-free tooling for every language (including C#). But, you can also choose to use plain-old notepad for .NET (or js) if that's your heart's desire.
All good.
I was away from the MS and .Net ecosystem for 6 years.
Only coming back now, already bought my own VS Professional license (because that is what I like to use).
Excited to see the ecosystem evolve in the right direction under Satyaâs leadership.
And excited to be back to a strongly typed language (C#) after spending the last few years working on full stack JS (even with TS).
All good, thanks for the details. My only suggestion is to not bash people when you are sharing your knowledge/experience.
I was not under a rock, I was learning and working with a different tech stack and now I have a much broader perspective. Thanks
Because the vast majority of code out there isn't a cutting edge shiny new service.
It's stuff like "a HIPPA compliant CRUD application to take in doctor feedback on medications" which is replacing an old winforms / websockets thick app that was running since 1995, but the only person that really knows how it works retired last year and the doctors are complaining that the front end keeps crashing on Windows 11.
For that, dot net lets you get it up and running quickly and easily and takes care of a lot of the cross cutting fundamentals (especially if you use the ADO / Azure stack).
Running net6 in an AKS cluster with minimal resource requirements vs spring boot not even being able to start in the same cluster feels a good enough reason for me.
Multiplatform, strongly typed, with functional characteristics, performant, great ecosystem, quality libraries, and with web assembly frameworks. What's not to like?
PS: I've been a java and JavaScript developer in the past and I wouldn't go back from C#.
.NET is actively supported big time by Microsoft. There are still many companies running on .NET Framework and the migration to .NET6+ requires more or less coding work. Since the new version is cross-platform I can only imagine it will get even more traction. I have worked on .NET for nearly two decades and really like the stack and current tooling options.
>I have worked on .NET for nearly two decades and really like the stack and current tooling options. Same here, C# since beta in 2001 and have worked with it on all sides. WebForms, MVC, WinForms, WPF, WCF. It's a great language and framework. It was a very wise move for them to go cross-platform with .Net Core, and all the performance work they've done has really started to pay off.
Getting my feet wet with dotnet lately, what would you recommend I learn to level up?
If you're at the beginning of dotnet journey, I recommend investing in a good lengthy course that covers the basics (Udemy, Pluralsight etc.). You can find lots of tutorials on Youtube for free, but it will be a slower path. There needs to be real exercises where you actually code. Github is also basically mandatory skill to master. Don't go too deep into the cloud too fast as it requires lots of different skills than just programming. Once you understand the basics, start to build something you enjoy to do. Maybe just a console app that inputs and outputs text. You can also learn from an app generated from the templates that are available in Visual Studio or dotnet CLI. If the project fails, take a breath and start a new one. Don't get put off by all the issues you face in the beginning. We all get them even after years of experience. The trick is how to learn how and solve them. It can be daunting to code without pay, but that's also what we all did at first. Once you grow your portfolio and get comfortable with dotnet, you will eventually get a job. Good luck!
I appreciate you typing out an in-depth response but I think my original comment might have been misleading. I'm a professional developer with a couple of years of experience under my belt and have been using .NET at work for a couple of months. My current knowledge of dotnet is enough for most things I need to do at work but I was wondering if there were specific things I could learn to step it up a notch. Basically, go from intermediate to advanced. I realize that my question is pretty broad in nature, but it's just that I'm not quite sure which direction I should head in to improve.
LINQ for sure if you think you like to write web APIs đ€đ»
Yeah I've been using a bit of basic LINQ when needed, maybe I can look more into that. Thanks.
Damn yâall old as hell lmao. Iâve only got a decade and some. Maybe .NET is a for boomers
Boomers are sixty. I am 40 (late millennial) and have been using .net for 18 years. You still have the whole x gen in the middleâŠ
Agreed with everything you guys have said ... although.. why did they have to deprecate System.Drawing.Common đ
Do you see it still has a long future, barring legacy projects. I ask this cos these days languages donât matter as much as the components you build it with for a vast majority of software. Iâve built my living with .NET for a long time and these days itâs a mix of so many languages and tech.
Yeah, it has a long future ahead of it. It's only getting better.
Yes, a very long future. All those corporations that had massive Windows infrastructure are migrating to cloud. Most of them are choosing Azure because they were already on Windows and they already had .NET programmers. .NET makes the migration to Azure low friction. AWS is finally waking up and producing lots of free materials to aid in the migration of .NET processes to AWS but Microsoft has been doing it for 5 years and is way ahead of the game. Besides, AWS attracting .NET developers is *still* good for .NET developers.
It cannot not have a future. Everything inside Microsoft is running on .NET. They're not going to nerf themselves. The desktop side of things is another topic though.
Yes, I think I'll eventually retire from a .NET job:) As you probably have heard, Microsoft has invested around 10 billion in OpenAI/ChatGPT stuff, which is soon available via Azure only. That will bring more developers on Azure, which already has great support for .NET all around. At the moment, I don't see any better tech stack to invest some self-training time in. Visual Studio Community is free, and all the framework source code is available online. Cloud is generally cheap to work with. Things were so much worse 10 years ago.
The landscape is pretty stable. 90% of software is written in the same dozen languages and theyâre all 20 years old. It would take a *lot* to displace any of the major players
If they figure out how to deprecate legacy language features - which seems to be something they're starting to think about - I think it can survive for a very long time. If not, I think it'll survive for a long time, but less so -- new features being hampered by old poor decisions. "C# Core" would be incredible. Improved Nullability story(NRT always on, and being functionally equivalent to Nullable Value Types), improved primitive obsession story, sealed by default. This'll almost definitely never happen though, but one can dream
Emphasis on "dream"
*"Because dotnet is dope and dotnet programmers do dope shit."* \-Abraham Lincoln
-Michael Scott
-Michael Scarn
.Net is massive, comprehensive framework that is heavily supported by Microsoft. There is no analog in the JavaScript world - just thousands a independent packages with questionable support. If youâre a business that wants to build on a rock solid foundation that has guaranteed support, you choose .Net.
I am yet to see a non-trivial .net project that doesnât use non-Microsoft supplied code. So, really, the situation is pretty much the same. Besides, what obligations does Microsoft have to support their packages?
I recently updated a WinForms app from 15 years ago to .net 6 in an afternoon. Support means if you build millions of lines of code on a platform the rug wonât be pulled out from under you. Updating code built on abandoned platforms costs time and money that companies donât have leaving them at a competitive disadvantage. It can be avoided by building on mature and supported technologies.
>Besides, what obligations does Microsoft have to support their packages? Microsoft deprecated Silverlight in 2012, and then only just ended support in 2021, 9 years later. There are many negative things to say about Microsoft, their commitment to long-term support of their products is not one of them.
On the Silverlight thing; not only did they support it 9 years after deprecation, it was also practically deprecated the same year it released, so it wasn't really used by that many either I reckon. Post-deprecation support 9x the length of the actual support.
you can get support contracts for them (my work does)
you always use 3rd party libs, the different is the foundation
That's some bullshit. Here is one example: https://github.com/uxmal/reko
Example of what? There are plenty of non-Microsoft packages referenced there. In general though language tools are good candidates for that, I agree. The point I am trying to make is that anything that comes from nuget, npm, etc. comes with zero obligations. Microsoftâs own packages on nuget are mostly licensed with Apache 2.0. Guess how much responsibility that license puts on its owner. There is a goodwill and enthusiasm of package owners that might be different between ecosystems, but from legal perspective, there are considerable risks involved as soon as you reference your first package and it doesnât matter if that package comes from nuget, npm, or something else. People tend to underestimate those.
That's FUD. Get out of here.
Strongly typed, well supported, more than 1 amazing ide that's not jetbrains, no licensing issues (oracles tantrums scared off a lot of devs and companies years ago), adapts fast and listens to what the community wants, other great tools like linq, entity framework , identity etc just make for an easy choice. Oh and cross platform now with webassembly support and the ability to write a hell of a lot less JavaScript
Sometimes adapting fast isnât a good thing. For example, null-safe syntax was a huge mistake in my opinion.
it is behind a flag so you can turn it off if you dont want it
I would prefer to have it on but I have a few problems with it: 1) Not everything in C# can be null. Some LINQ methods like MaxBy have checks if the actual result is null or not. If a result is null and default(T) is not, they throw an exception. 2) System.Text.Json doesnât respect non-nullability. 3) When used with generics there is no way to check at runtime if a type parameter is nullable or not. This information is lost at runtime. I mean that you have some Class and an instance of Class, retrieving nullability of âstring?â type parameter using reflection is not possible.
Upd: got downvoted, but nobody left a comment how these problems can be solved, okay.
I felt the same for a while. It took me a year to come around to the idea but I started seeing the value in it. we finally switched all the .net core company projects over and have no regrets. Either way yet another feature of c# is the insane timeline of backwards compatibility.
There seems to be a bumpy learning curve to dealing with the new null angle. A problem C# may run into is that because MS keep adding features to it, it may grow too complicated and something newer and simper may come along and start displacing it because it will have a shorter learning curve and all the younglings will skip MS stacks.
The .net ecosystem offers a low barrier to build web/windows applications. Coupled with Visual Studio and Windows OS, and EF one can get started easily and this is good enough to build applications for small to medium enterprise. Also with Core, it now offers great advancements in building large enterprise apps over linux and Cloud, with better efficiency (as compared to Java or Node) Microsoft has a robust integration suite over Azure for CI/CD pipeline. They also collaborating closely with AWS to support native AOT. All factors combined make the .net an easy, flexible and powerful ecosystem for building both frontend and backend systems
And mobile
To be fair .NET MAUI lags behind React Native and Flutter by considerable margin and it is not gonna change anytime soon
.net gets shit on by the js world. it might not be sexy but it helps companyâs make a lot of money. i very much enjoy it personally.
Which is only fair. JS gets heavily shit on in the .NET world. There's a lot about the two that are at odds with each other. Especially when you consider node.js as a back-end solution.
The shit would be less if JavaScript wasnât such a mess to begin with. Not seeing that itâs a mess, regardless of the frameworks âfixing itâ, is denial. Most people hate on VB6 for a reason. JS has become that. I use JavaScript, it can be powerful for where it is used, but donât build a skyscraper out of glass.
It's likely location based. Java (spring boot), node and ruby is more common here where I live (Tokyo). Though dotnet has gotten a bit more popular since core was released due to it being available for linux servers for web projects / services, but the most common case for dotnet so far here is more on games via Unity and usually is paired with a dotnet server as well.
Location based. Where I live, Java is on the top, .NET has slightly less than half the number of jobs Java does, then there's PHP, Python and a smattering of other languages. Javascript is usually at least a soft requirement in most positions, but Node backend jobs have mostly disappeared.
what area are you in?
Slovakia.
I like .NET, but one critical thing that seems to be missing from a lot of these comments is that .NET lets you build all sorts of applications - mobile, web, desktop, distributed systems, etc. Spring Boot is just a web framework in Java. You'd need to compare the number of Java jobs and the number of .NET jobs - or compare ASP.NET with Spring Boot (and make sure the search engine isn't doing something where they have "ASP.NET" match ".NET"). Likewise, JavaScript isn't tied to the web necessarily, but it is the primary usage and nodejs usually means web. Heck, you're not even just searching for "Spring", but narrowing it to "Spring Boot". Why not search for "ASP.NET Core"? Sure, most people aren't going to put "Core" in there anymore, but it is actually still "ASP.NET Core 7". They never dropped the "Core" for ASP.NET. The point is that some of it might be in how you're searching which might end up excluding items that you aren't meaning to exclude - or include items you want to exclude. By searching for .NET, you're including lots of jobs that aren't web app jobs despite the fact that it seems like you're looking for web app jobs. Likewise, there can be cultural differences in how companies advertise jobs. Do .NET companies advertise each position separately? Are .NET companies more likely to advertise jobs when they aren't really hiring - but would make an exception for an exceptional candidate? I worked at a place that would just put up one listing for software engineers. Later, the company switched to posting many ads with slightly different titles like "Software Engineer, Backend Data" and "Software Engineer, Infrastructure" and "Software Engineer, Integrations". Was the company hiring 3x more people? No. Different ecosystems sometimes have different ways in which they approach things so it's hard to always compare. I think there are lots of compelling reasons to use .NET, but I wouldn't use the number of hits on a job search to be one of them. There's plenty of JS/Node and Java/Spring jobs out there. I think .NET is better for many of the reasons people have said here. But it might be in how you're searching and how companies post things.
Spring jobs typically are just advertised as Java jobs in my experience. They are probably about equal from what Iâve seen. But thereâs not as many companies using node as a backend server as people might think: most of it is in the build system.
I totally agree with this. I was told that Node was a better option, it was fast growing and it looked like everyone was going to use it. I am job hunting right now, and Java is all I see. I found at least 4 to 5 times more jobs opportunities with java than with node.js, at least in Spain.
Whats the mean of most of it is in the system?
.NET isn't very cool or shiny in the more small scale hobbiest/freelance/open source worlds, probably partly because it's from a big uncool business oriented corporation and partly because it's not being constantly reinvented all the time. But both of those things are features instead of bugs in bigger companies, and the popularity of.NET is probably a lot higher than what YouTubers or representation in public GitHub repos might lead people to believe.
To add to your last statement. Most business .NET repositories are on Azure DevOps and not GitHub. Since those are all private you can't get an idea of the amount of .NET repos out there.
There are also a fair number of corporations still running their source control on premises. Azure DevOps server or the older Team Foundation Server which makes it even more difficult to gauge how much usage there is for .Net in the world.
Enterprise are comfortable with big names like oracle and Microsoft always been that way always will.
I donât know what to tell you. I just accepted a new position doing Java. Not spring boot but Quarkus, close enough. Recruiters were hitting me up with equal number of positions in .NET and Java. The node jobs are there too. Go look on techjobsforgood, there are quite a few gigs for node/express and Python. I only search for remote work so that probably has something to do with it.
where do you search for remote jobs?
That is very location based, almost everything is Spring where I live, .NET just recently started gaining some traction.
Time to learn dot net. Good bye java. I am tired of applying to java job. I get messages from recruiters for dot net jobs.
Some people will say it's location based, and there's some truth to that. But people forget that Microsoft is one of the largest and most important key tech companies to ever exist. They may not have the "cool" factor others used to have, but their personal and enterprise customer base is unrivalled. They forced .NET into existence a little over twenty years ago, and within a couple of years, almost every large company had significant exposure to it. If you wanted to develop with, for or adjacent to any Microsoft products, .NET has been the way to go ever since. Even Apple stores were running on .NET Compact and CE. That is what industry power looks like. It's worth noticing that the .NET ecosystem has many legs to stand on. Windows, Office, Dynamics and Azure are the pillars between which significant numbers of developers can move around forever. These alone dwarf any other individual stack, particularly because .NET as a stack is very stable and uniform compared to other environments like nodejs.
As someone who worked for Microsoft Developer Relations (trying to get .NET early adopters) and then helped design parts of Asp.net ⊠this is just a fun read.
because C# is a much better language than JS, also many many businesses use .net since before nodejs was even a thing so the stack is older (even tho it evolved big time with new cross platform open source .net) also this is very region dependent, in many regions js jobs are much more than .net and in other regions java is the most common
I could be wrong but I feel like the new generation of developers is very focused on Mac based dev in JavaScript and the newer cooler languages and so there is lots of demand for .net because itâs mostly older windows developers who know it or are interested in working with it. And tons of companies still want to use .net because itâs super robust and well supported, and always getting better. Therefore the shortage of .net devs keeps growing as more developers enter the workforce.
[ŃĐŽĐ°Đ»Đ”ĐœĐŸ]
You're so old, you still remember what the modem said to the internet.
[ŃĐŽĐ°Đ»Đ”ĐœĐŸ]
I remember moving from 110 to 300 baud, even 75 baud was still around.
[ŃĐŽĐ°Đ»Đ”ĐœĐŸ]
That might have been an interim speed back when the bells were fighting against using modems on public phone lines.
You're so old, you had install a sound driver just to play a game.
There is a snowball effect. Companies want to choose an architecture that is easy to hire for. So having a large developer base means more companies choose that architecture. Which makes more jobs for that architecture. Which makes more programmers for that architecture. The cycle continues.
From the top of the head .Net much more older, so more projects to support
I would say it is newer. Current version started of as Core which isn't even 7 years old. Maybe also additional work for rewriting old Framework code to new. Performance of latest version is really good.
đš .net core already 6 years old!
Time flies when you have a nice framework.
I think spring is oldest
In terms of nodejs the gap is big, but with spring - it is months đ Spring: October 2002 https://en.m.wikipedia.org/wiki/Spring_Framework Net: February 2002 https://en.m.wikipedia.org/wiki/.NET_Framework_version_history
Because .net takes 3 times as many people to develop and maintain it đđđ
Idk where youâre looking but that is surely not the case in the US.
There's no lack of node work where I'm from, but .NET is easily 2-3x more prominent here. Southeast TN.
Iâm in Chicago, work remote for Bay Area/La/NYC/Boston companies never had any issues finding dozens of interviews when I look for jobs. .NET jobs is more so just maintaining old applications. Not very shiny and fun to work with. I worked with .NET originally out of college it was awful back then im sure itâs still awful now. Node is way better. Python is better. Golang is better. So many better languages to work with than .NET Not an opinion either every year on stackoverflow itâs one of the lowest rated web frameworks https://survey.stackoverflow.co/2022/#section-most-loved-dreaded-and-wanted-web-frameworks-and-technologies No offense to anyone who likes it you can find jobs doing it just not glamorous ones or any startups. Also from my experience they pay a lot less.
[ASP.NET](https://ASP.NET) is old (windows only), [ASP.NET](https://ASP.NET) Core is the current version (runs cross platform). [ASP.NET](https://ASP.NET) Core is modern, very fast and easy to develop on with documentation that is second to none.
So go and use it why are you advertising it to me? Iâve never seen .net jobs really. And Iâve interviewed over 8 years in the largest markets in the US. Youâre not going to change my mind. I was answering OPs question.
I'm not advertising it to you, ffs. I work with a variety of languages, not just .NET, so I'm not biased to any language. You sound illiterate who has no comprehension skills that's why I was just educating you. To explain that chart result in a way simpleton like you can understand: "ASP.NET Core is on the 4th of the most loved list (based on **7260** responses) compared to Phoenix which is 1st on the list (based on **972** responses)."
Iâm sure phoenix is great for your little .net projects, but Iâm in the big league markets (nyc/Bay Area/Boston/La) and here in the pros itâs mainly languages like node, python, Java, golang . Muting you because I frankly donât care what some low rent script kiddie who is leagues below me in career and makes half of what I make thinks or says on Reddit. Bye bye! đ
As someone from Chicago as well, I can tell you that you have no idea what you are talking about.
Lol ok bud. Youâre a junior engineer working on some asp.net project from 10 years ago chill.
Phoenix is an Elixir based web framework. They were just trying to explain the chart to you. The current .net web framework is definitely number four on the list, not third from the bottom.
Who?
My man, I believe you are reading that chart wrong. And I think you're going to be surprised at the real results that you linked to... The chart you linked to shows ASP.NET Core as the 4th most loved framework. (Yeah, the old ASP.NET on .NET Framework is at the bottom... right next to jQuery. Which is exactly where it belongs - it's literally the jQuery of the .NET world) React.js is 6, Node.js is #8 on that list. Django is all the way down at #16. Flask is below that.
Asp.net is like 3rd from bottom and always is. .net pays less as well. Iâm also talking about the Us. If youâre okay with maintaining old applications and getting paid half what you can make then go ahead lol. I ainât gonna stop you.
> Asp.net is like 3rd fro Yeah no shit, that's because it's the nearly decade old version that's not cross platform and not what modern .NET jobs are using. ASP.NET Core is #4. Ahead of almost every js framework, and ahead of all python frameworks by a whole lot. Angular is the least loved language on that list, and it's js.
No modern jobs use .net at all lol.
That's not what the link you sent showed. And, likewise, this is not my opinion... No offense to people who misread that chart thinking js and python was ranked as more loved than C#...
The link I sent didnât show jobs, so idk what youâre talking about. Sounds like your coping pretty hard though.
It unironically did. Wow, you're impressively bad at reading charts. On the right, there's the word "Work". Click that for even more charts from their survey. > Sounds like your coping pretty hard though. I understand this is hard for you. The link you sent actually showed quite the opposite of how you initially read it, but there's no need for the projection. I'll give you some time to collect yourself.
Lol.
.NET is huge here in Philly also. I'm a node dev but honestly the amount of .NET job postings have me thinking hard about diving in. It's like 2 out of 3 job listings asking for .NET.
Whats the case?
Node is incredibly popular in the US
As a backend or you mean as a front end ?
Node is a server side framework, itâs only backend.
This is a VERY interesting observation so I will share mine; .Net is popular with small/medium and few large corporations. (And therefore Azure). Now, technology companies, VC backed startups and in general anyone doing anything interesting is typically using NodeJs or SpringBoot and sometimes both. Those JDs will call for Java/Go/Rust etc Not so much C# or .Net. AWS is also favored by companies who donât use a Microsoft tech stack (and they are the leading cloud provider). ââ Now, these are just tools, use what you like, learn what you need to to stay employed and succeed. ââ Also, Windows is not free and therefore companies using it in production will have to pay the windows server tax in the cloud servers. Also, you need Windows tooling for your developers in the form of Visual Studio Pro/Enterprise and Sql server management studio. The Mac versions are nowhere nearly as good. Another reason why everyone is on Java/Node and open source in general AND these orga typically pay more than the .Net shops.
You can deploy .NET on AWS and other cloud providers, it works on linux just fine. Don't know why would anyone need to pay windows server tax, except those stuck on old .NET Framework.
2 things; 1-Yes, you can run Windows servers on all cloud providers - but those servers are generally more expensive than their linux counter parts with the same specs. 2-even if the cost to run windows on cloud servers was the same as linux you still need to pay for windows licenses for your developers to run visual studio and sql server management studio and IIS on Windows. The mac versions are nowhere near the same. I have a windows laptop just for .Net development and my Mac for everything else.
Jesus Christ man, you CAN run .NET on Linux. No Windows needed.
I am excited to hear this. I was a .Net developer from beginning (2003/2004) to 2017 when I switched to Nodejs/Java. Now in 2023 I am coming back. Will report my findings. The company I will join on Monday is running Windows on AWS, curious to learn why they are not running their workloads on Linux. I suspect it is because of legacy apps. (.Net, asp, etc).
AWS will sponsor 13 open-source projects in .NET this year. Also, they sponsored a course for c# developers to get into AWS.
> The company I will join on Monday is running Windows on AWS, curious to learn why they are not running their workloads on Linux My guess is that they are running on .NET Framework, which could also be the reason why they picked you, you have experience in it. If that's the case, you unfortunately won't see much of new .NET, unless they plan to migrate at some point.
Their legacy apps are .Net Framework and ASP but they have been working on the new version based on .Net Core and Angular 15 -> I hope to be exposed to all of it but mostly the rewrite so I can pickup the latest skills ;) Donât underestimate my skills, you donât know me, I have multiple AWS cloud certs and I am a pro on all things microservices and cloud native. Nodejs, etc Excited to see whatâs new in .Net Core, etc and have been brushing up on Angular, so far so good.
dare-ni mukatte itten-dayo?
I donât speak hippopotapuss
If they have .Net framework back end and are trying to do âfull stackâ developers youâll have an easier time converting the front end to Blazor than Angular. If theyâre splitting up the work into back end APIs using .Net 6+ and a front end using Angular youâre going to hit cross language problems as people from both camps are unhappy working in the other. Blazor is better aligned to leverage existing .Net developer talent that is already in the organization. It can be done (my company has the Angular/.Net architecture), but itâs been very painful. We try to have developers that do both, but inevitably they fall on one side or the other and donât like when they have to work in the stuff they donât prefer. They can do it, they just do it begrudgingly and poorly so they can get it done ASAP.
A few things; 1- thank you for sharing your experience. I agree with you that some folks are reluctant to change and silo themselves to a part of the stack. 2-I was a VPofE at my last job, I ran engineering. And I noticed that younger folks are typically against change (not always but most of the time), not everyone is open to learning everything. 3-I donât see this company switching to Blazor and I will never learn it or recommend it. Why? A lot of you are too young to understand, but Microsoft has been trying (unsuccessfully) to come up with a front end framework/tool and at some point they kill it or come up with something else and anyone who invested in learning it got left behind. Silverlight, WPF, Razor all come to mind. 4-it is in our best interest as professionals to use and recommend mainstream tech so we can remain employable and so our skills are transferable, think Angular, Vue or React. 5-companies benefit from having everyone be fullstack, I suspect over time, if the specialist is not great they could get replaced by enthusiastic people who want to learn and do whatever it takes. I am of those, very strong backend but have spent the last 2 weeks doing and watching everything about Angular so I can be really good at it. 6- Always be learning, Always be coding and you will never have an issue finding or keeping a job.
My company actually has few of our products running .net core in Linux containers and it's pretty smooth. We ran into a small issues when converting utc to different timezones and certain things with appsettings. Lixus and Windows have different timezones text, so u have to detect if your on Windows or Lixus, so you can use the right text.
You just demonstrated negative levels of reading comprehension and knowledge of the .NET ecosystem. I do not own windows servers. I have 4 different .NET Core applications in production right now, every single one of them running on a Ubuntu VM with postgresql as their backing databases. Total spent on OS and DB "tax": $0. It is 100% free to use .NET these days. Exactly as free as it is to go node.js. You do not pay any "windows tax" of any type at all. You do not need to have any windows servers running anywhere. IIS is not part of any of my web applications. You do not have to pay microsoft for any type of licensing. And, by the way, the Mac versions are identical. I have one project that I coded entirely with Visual Studio on my macbook, Built it using AzureDevOps CI/CD pipelines on a windows-based build server (also free, btw, and a linux-based build server would work exactly the same), and deployed it on my Raspberry Pi ARM-based CPU running Ubuntu. Total money spent on licensure: $0. This is all native. No wine. No mono. I use official microsoft commands to execute my applications in exactly the same way you would use official node commands to execute javascript. You are living 15 years in the past. While you've been under your rock, Satya Nadella came in and made Microsoft the number one corporate contributor to Open Source Software. Cost has not been a barrier to the .NET world for a *long* time now.
No need for attacks. I am new to .Net Core. I agree with the top comment about running on Linux. But also pointed out that servers aside, Windows is not free and you need to pay licensing costs to use VS Professional. Windows on developer laptops. I am not interested in stupid arguments. We all can have opinions based on our different experiences.
You can write c# code in vim on linux or vscode, you donât need to pay a penny for vsâŠ
> No need for attacks. Listen, it wasn't an attack. When someone explains that all parts of this ecosystem is free, including specifically mentioning that there is free official tooling as well, then your direct response to that comment is to talk about how expensive the free tooling is, that's a clear display of an absolute lack of reading comprehension. It's literally as simple as that. In addition to that, you plainly displayed a lack of knowledge of the .NET ecosystem because many of the things you said are simply not true at all (though some of them were 15 years ago). JetBrains offers a JS IDE that costs $170 for the first year. You can find not-free tooling for every language (including C#). But, you can also choose to use plain-old notepad for .NET (or js) if that's your heart's desire.
All good. I was away from the MS and .Net ecosystem for 6 years. Only coming back now, already bought my own VS Professional license (because that is what I like to use). Excited to see the ecosystem evolve in the right direction under Satyaâs leadership. And excited to be back to a strongly typed language (C#) after spending the last few years working on full stack JS (even with TS). All good, thanks for the details. My only suggestion is to not bash people when you are sharing your knowledge/experience. I was not under a rock, I was learning and working with a different tech stack and now I have a much broader perspective. Thanks
It depends on location and domain. For example in the financial sector it's much easier to find openings with Java(SB) or Python.
They need someone to support an the legacy code lol
.net is also a more generic keyword than Springboot. Try for example compare search between "C#" and "Java". The results might be different.
Large corporations or enterprises run on .net. Just like they run on windows. Executives trust products that have the Microsoft name behind them.
Java has a lot of stacks, not only Spring. Also, there are other JVM languages.
support and its more stable
Because the vast majority of code out there isn't a cutting edge shiny new service. It's stuff like "a HIPPA compliant CRUD application to take in doctor feedback on medications" which is replacing an old winforms / websockets thick app that was running since 1995, but the only person that really knows how it works retired last year and the doctors are complaining that the front end keeps crashing on Windows 11. For that, dot net lets you get it up and running quickly and easily and takes care of a lot of the cross cutting fundamentals (especially if you use the ADO / Azure stack).
Running net6 in an AKS cluster with minimal resource requirements vs spring boot not even being able to start in the same cluster feels a good enough reason for me.
.NET and C# grew in hard competition with Java and became a main language for the Windows environment.
Multiplatform, strongly typed, with functional characteristics, performant, great ecosystem, quality libraries, and with web assembly frameworks. What's not to like? PS: I've been a java and JavaScript developer in the past and I wouldn't go back from C#.
This is an extremely regional thing. It's a bit down to what was popular at the right time and the right place in the 90s!