Who is using the .NET stack for their startup (2022)?

I started my company back when news about .NET Core was first coming out (2016).

I've been bitten by Microsoft before (relied on tech they eventually killed), but decided it was worth it because of the modernization they had planned. Things such as AOT compilation, strong cross-platform support, lightweight runtime etc. was a giant productivity booster for me and my small team of 4 people.

Microsoft eventually backpaddled on a a few of their promises, but I still believe it was the right choice. I had doubts back then, but I would not hesitate today.

I can recommend https://stackshare.io/dot-net-core as a good starting point. As a .net developer, I always use .Net in the backend. I think it is very good in asynchronous programming.

I would find it hard to evaluate these answers without the inclusion of "upon what workstations" and "deployed via what" because if the startup requires developers to use Windows and deploys to Azure (or such), this isn't as newsworthy as heterogeneous workstations deploying on Bottlerocket/Container Optimized OS

Not exactly a startup (yet?), but I'm using .NET 6 in my side project to build the API backing a React SPA. It was funny arriving at it, because I started out by trying to choose between Python and Elixir, having left the Microsoft ecosystem 10 years ago (and vowing not to return to it). At the end of the day, .NET bubbled up to the top as the sweet spot of familiarity, maintainability due to strong typing, integration into the open source ecosystem, and ease of hiring should that ever become a concern (premature optimization, but still).

I just use it on the backend along with Entity Framework, a pretty neat ORM, and do my best to avoid lock-in into the rest of the Microsoft monoculture. Using Postgres for data, AWS for hosting, React with Vite for frontend because I would never trust MS to get that aspect right with their endless iteration of UI frameworks both on web and desktop.

We use .net core with a React Typescript frontend. Our production exe runs on bare metal Ubuntu instances behind NGINX.

I am. The core app is a desktop Electron app with a .Net 6 backend. There's some communication with a web api, also written in .Net 6 and hosted on Azure, but the desktop app is the heart of the product.

Even though it's a cross platform Electron app I haven't built the Mac version yet - so I can't answer yet for any issues that might pop up there. (Only reason being I haven't got around to buying a Mac to test it on.)

Two reasons for using .Net. The first was it's what I've used most in the day job. Second is that a core sdk I need to use inside the app is .Net. Rolling my own in a sexier language would have added months or years to the development time.

I don't work for a start up but...

.NET Core is great. It's good to go for cross platform development for anything non-gui related.

For client-side apps it is not cross-platform. There's MAUI which might hit all the targets you want, except GNU/Linux. Although Android/Linux is supported. The way to solve this is a web-based UI. There's several ways to go about having a locally running program with a web-based UI. Hijacking a web-based UI is not unique to .NET, so this is not an advantage, it's just this hack makes the lack of native UI not quite as important.

Also, which language/platform has really nailed down cross platform UI's while still being at least "somewhat" native on each target? There's really not many options. It's an industry wide problem. .NET has some decent escape hatches like Blazor. And maybe MAUI will get it right but the jury is still out.

As far as your development environment, you can use VS-code as your IDE in a cross platform way. Develop .NET software on a new M1 Mac? Yes you can! And with LSP you are not tied down to Microsoft tooling. With a little bit of configuration, you can can make Emacs or Vim a fully featured .NET IDE.

There's native AOT compilation so if you have some microservice that needs to spin up stuff, you don't need to worry about start up time.

Overall .NET just seems like an absolute killer tech. I think people are doing themselves a disservice to dismiss it just because it's from M$.

I haven't launched a startup on .NET recently, but I've been looking into modern .NET and I'm pretty impressed. I'll probably use it for my next side-project.

I think Blazor in particular has a lot of potential. I've grown disillusioned with front-end development over the past 5 years so it's worth trying something new and experimental. But I'm not sure I'd bet my career on it or ship it widely yet.

Me, I am writing most of tools for accelerate development and automating home bored tasks with csharp, it still the best prototyping language for me. Of course, I am not a startup yet, but a hope

Project Reunion has a lot of potencial.

In 2022 we use NET6, last .NET Core was 3.1 which reaches end-of-life soon.

Our SeekTable started as .NET Core 1.1 app 6 years ago, it was upgraded to 2.1, then 3.1 and now it is a NET6 app. Upgrades up to 3.1 were pain in the ass, API/SDK evolution was quick and not backward compatible, however last upgrade to NET6 was easy - this is more a change of the run-time version, as APIs are not changed anymore and become stable.