I'm a .NET developer with 5 years of experience, mostly in the enterprise space. I've worked on large projects with .NET 3.5 - 4.7, and recently I've been build

I'm a .NET developer with 5 years of experience, mostly in the enterprise space. I've worked on large projects with .NET 3.5 - 4.7, and recently I've been building things in .NET core. Honestly, .NET core makes a lot of sense for new projects that need to be highly scalable. If you have an API service that's hosted in a cloud provider, or a tool that generates PDFs of items, or a tool that scrapes API data and chucks it in a database, then this is great. These are simple applications that do not need an awful lot of authentication, crazy UI frameworks, or other windows-only features. The code itself runs faster [1]. It might not matter for business / CRUD applications, but that's a nice to have thing. The biggest selling point is cross platform support. Now, I don't care if the company switches from Windows 2016 VM's to some variation of RHEL. My code will work on that too. This gives your organization improved flexibility and reduced technical debt. If you have a big legacy application using .NET Framework, it's probably not worth rewriting it for .NET Core. You will run into package conflicts. I have had to rewrite ".NET Framework only" pacakges to support .NET Core. That will throw your estimates off and probably delay the project. And that becomes really difficult to justify to project stakeholders. [1]: https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-at-7-million-requests-per-second/ https://www.ageofascent.com/2019/02/04/asp-net-core-saturati...