I know it's available, but I always assumed it would be a 2nd class citizen.
I just tried to install in on my personal macOS system. I tried brew, as Microsoft gives instructions for it...
> Warning: powershell has been deprecated because it does not pass the macOS Gatekeeper check! It will be disabled on 2026-09-01.
It went on to do more and then prompted for my password, but I canceled out of it. I'm not looking to get started with anything that starts with a deprecation warning. This is what I'm talking about when I say it feels like a 2nd class citizen. I can only assume I can't use 100% Powershell to admin a system, like one could with Windows.
I am building a new product from scratch in .NET. Not the full traditional MS stack but just .NET for backend and VueJS for frontend and Postgres for DB. I don't use things like Azure, SQL Server etc but .NET is solid. So yes.
What are the "best of breed" tools in your opinion?
In the enterprise world, dotnet with c# is one of the best choices, although recently I've been doing a lot of logic just with python running on serverless functions.
I never chose MS, ever. Most systems have been based on Debian servers. Some special needs I've used Alpine Linux and NetBSD (yes it does run on older, limited hardware).
Of course, some potential clients demand MS based solutions. I simply decline those contracts and ring them up 12-18 months later to see if the CTO/CIO has been replaced.
It really depends on the 'time-to-market' requirements. If it's a complex enterprise play, the .NET ecosystem with C# is hard to beat for developer ergonomics and long-term maintenance. However, for a high-performance AI-native startup, I’d likely lean towards a more heterogeneous stack (Python/Rust/Go). The 'Microsoft tax' isn't just about money anymore; it's about the cognitive load of being locked into the Azure-first architectural mindset.
You can build a .NET application without being locked in the usual MS ecosystem. I am building a greenfield SAAS product in .NET with VueJS and Postgres. Will deploy on AWS, Cloudflare etc.
C# is a great language, and .NET is a really good runtime that is cross-platform.
I would personally chose it over Java, and I think it is more "batteries included" than Go.
If you need to write a business/web application that is fairly easy to maintain and has good performance, yes I would pick C#.
Also, while functional programming etc is possible in C#, all the code I've seen has been very Object-Oriented. Classes for days. Dependency injection, factories, and other "Design Patterns" aplently.
Obviously with Python or Node.js you'll likely have an easier time getting off the ground but the performance will be worse (if that matters)
source: SWE manager at MSFT, mostly C# stuff. 10+ YOE with other languages prior to joining
It depends heavily on the domain. For B2B operations tooling, the real question isn't which stack to build with — it's which ecosystem your customers are already locked into.
If your target users live in Microsoft 365 + Azure AD, the integration advantages of the MS stack are hard to ignore regardless of technical preference. Same goes for teams deep in the Google Workspace or Atlassian ecosystem.
For our greenfield project we went with Kotlin/Spring + Next.js on the basis that most of our target customers use Jira+Confluence, so Atlassian ecosystem familiarity mattered more than stack choice itself.
DotNet 10 allows me to create a single web application for all three major platforms, and to ship it with the runtime baked in. This allows me to host said application anywhere I want.
If talking about non-web desktop/mobile software, the big issue comes down to GUI framework. Maui is optimized for mobile, Avalonia is superior on desktop. But other than that, thanks to the baked-in runtime it is becoming trivial to build a single GUI program and have it just run anywhere without significant rework.
Plus, C# has become an absolute pleasure to work with, and makes Java look practically obsolete. Hell, Java had to roll back its own implementation of string interpolation in 2024 because they just couldn’t make it work. C#? Working beautifully since 2015, and improved several times to even greater effect.
And if C#’s functional programming rustles your jimmies, you can easily use F# in the same project without complaint.
Finally, while Blazor webassembly might not be entirely ready for world+dog prime time just yet, it works great in an intranet where thick pipes are guaranteed, allowing me to give a hearty middle finger to everything JavaScript.
Honestly, while I will always evaluate every project to ensure that the programming platform is the best one possible, and have chosen other languages for good reasoning plenty of times. But anything which falls in the “anything will work well enough, generally speaking” bin has me reaching for DotNet almost every time.
Microsoft lives off of what Oracle, RedHat, HP or even IBM live off - commercial support. To large corporations, having someone to blame and who can vouch for or guarantee fulfilment of signed contracts means more than anything else, because it gives them legal way to offload responsibility and any legal or financial ramifications in case of a mistake. Windows owning the desktop operating system market, for now, is a clear choice for such services. So it depends on your needs rather than general question for value proposition as that depends solely on your specific requirements.
I know it's not popular, but I think Powershell returning objects is quite nice. It seems much better/easier than trying to parse raw text in Linux.
That said, if I'm making something new, I never go with an MS stack. I just wish I had some Powershell type options in Linux from time to time.
PowerShell is available for Linux and MacOS. Which means you can have the tool you like and run on a non-MS platform.
I know it's available, but I always assumed it would be a 2nd class citizen.
I just tried to install in on my personal macOS system. I tried brew, as Microsoft gives instructions for it...
> Warning: powershell has been deprecated because it does not pass the macOS Gatekeeper check! It will be disabled on 2026-09-01.
It went on to do more and then prompted for my password, but I canceled out of it. I'm not looking to get started with anything that starts with a deprecation warning. This is what I'm talking about when I say it feels like a 2nd class citizen. I can only assume I can't use 100% Powershell to admin a system, like one could with Windows.
I am building a new product from scratch in .NET. Not the full traditional MS stack but just .NET for backend and VueJS for frontend and Postgres for DB. I don't use things like Azure, SQL Server etc but .NET is solid. So yes.
What are the "best of breed" tools in your opinion?
In the enterprise world, dotnet with c# is one of the best choices, although recently I've been doing a lot of logic just with python running on serverless functions.
I never chose MS, ever. Most systems have been based on Debian servers. Some special needs I've used Alpine Linux and NetBSD (yes it does run on older, limited hardware).
Of course, some potential clients demand MS based solutions. I simply decline those contracts and ring them up 12-18 months later to see if the CTO/CIO has been replaced.
It really depends on the 'time-to-market' requirements. If it's a complex enterprise play, the .NET ecosystem with C# is hard to beat for developer ergonomics and long-term maintenance. However, for a high-performance AI-native startup, I’d likely lean towards a more heterogeneous stack (Python/Rust/Go). The 'Microsoft tax' isn't just about money anymore; it's about the cognitive load of being locked into the Azure-first architectural mindset.
You can build a .NET application without being locked in the usual MS ecosystem. I am building a greenfield SAAS product in .NET with VueJS and Postgres. Will deploy on AWS, Cloudflare etc.
C# is a great language, and .NET is a really good runtime that is cross-platform.
I would personally chose it over Java, and I think it is more "batteries included" than Go.
If you need to write a business/web application that is fairly easy to maintain and has good performance, yes I would pick C#.
Also, while functional programming etc is possible in C#, all the code I've seen has been very Object-Oriented. Classes for days. Dependency injection, factories, and other "Design Patterns" aplently.
Obviously with Python or Node.js you'll likely have an easier time getting off the ground but the performance will be worse (if that matters)
source: SWE manager at MSFT, mostly C# stuff. 10+ YOE with other languages prior to joining
It depends heavily on the domain. For B2B operations tooling, the real question isn't which stack to build with — it's which ecosystem your customers are already locked into.
If your target users live in Microsoft 365 + Azure AD, the integration advantages of the MS stack are hard to ignore regardless of technical preference. Same goes for teams deep in the Google Workspace or Atlassian ecosystem.
For our greenfield project we went with Kotlin/Spring + Next.js on the basis that most of our target customers use Jira+Confluence, so Atlassian ecosystem familiarity mattered more than stack choice itself.
TypeScript, C#, F#, Visual Studio, .NET, MAUI, Azure... lots to like and be super productive in.
The only good thing left of microsoft is Typescript language. That’s it.
DotNet 10 allows me to create a single web application for all three major platforms, and to ship it with the runtime baked in. This allows me to host said application anywhere I want.
If talking about non-web desktop/mobile software, the big issue comes down to GUI framework. Maui is optimized for mobile, Avalonia is superior on desktop. But other than that, thanks to the baked-in runtime it is becoming trivial to build a single GUI program and have it just run anywhere without significant rework.
Plus, C# has become an absolute pleasure to work with, and makes Java look practically obsolete. Hell, Java had to roll back its own implementation of string interpolation in 2024 because they just couldn’t make it work. C#? Working beautifully since 2015, and improved several times to even greater effect.
And if C#’s functional programming rustles your jimmies, you can easily use F# in the same project without complaint.
Finally, while Blazor webassembly might not be entirely ready for world+dog prime time just yet, it works great in an intranet where thick pipes are guaranteed, allowing me to give a hearty middle finger to everything JavaScript.
Honestly, while I will always evaluate every project to ensure that the programming platform is the best one possible, and have chosen other languages for good reasoning plenty of times. But anything which falls in the “anything will work well enough, generally speaking” bin has me reaching for DotNet almost every time.
Microsoft lives off of what Oracle, RedHat, HP or even IBM live off - commercial support. To large corporations, having someone to blame and who can vouch for or guarantee fulfilment of signed contracts means more than anything else, because it gives them legal way to offload responsibility and any legal or financial ramifications in case of a mistake. Windows owning the desktop operating system market, for now, is a clear choice for such services. So it depends on your needs rather than general question for value proposition as that depends solely on your specific requirements.