We were even able to downgrade our cloud servers to smaller instances, literally.

I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.

Pros:

* Stability

* Very decent standard library

* Good balance between productivity and robustness

* Great package management

* Extremely easy to upgrade, so essentially free goodies (performance) every year or so

Cons:

* Very MSFT dominated (obviously)

* Subpar tooling outside of Windows (I'm looking at you C# Dev Kit)

* C# has way to many features, it feels bloated

* Culturally, it feels like .NET devs are less "passionate" about their work

* The freaking stigma of being a .NET dev: you will never be as cool as the guys who work with Node/Python/whatever

Edit: Also I'd like to add EFCore as one of the pros of the ecosystem. Hands down the best ORM. Others don't come close.

I really, REALLY wish I was in another timeline where I could say in an interview "yes, I use Linux on my desktop and Rider for my IDE" without being seen as a traveler from outer space.

I enjoy working with modern C# way more than node.js but... that's it.

https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals...

Basically, you can now write scripts in C# without the ceremony of a solution or project file — writing some code in a cs file and running `dotnet run myFile.cs`will execute the file directly.

You can also shebang to make it directly executable!

Hoping this inspires more people to give C# a go — it's incredible these days. Come in, the water is fine.

I ran benchmarks, showing 2-10x+ improvements.

Got told, “lol no, this service is unlike Bing”. For context, Bing has amazing blogs on this*.

This, btw is inside networking for Azure…

Not sure at what point I should stop caring. Could easily improve operating expenses to the tune of hundreds/billions per year if they applied this across Azure.

https://devblogs.microsoft.com/dotnet/bing-com-runs-on-net-c...

In a world obsessed with AI and web tech, this is a refreshing read!

  var pixels = new uint[renderers.width * renderers.height];
  var pixels2 = MemoryMarshal.Cast<uint, ulong>(pixels);
  pixels2[idx] = ...

Spans is such a fundamental tool for low level programming. It is really unfortunate they were added relatively late to the language. Now every new version includes a slew of improvements related to them but they will never be as good as if they were there from the start or at least as early as generics were.

C# is a great language, it's now very modern and has the best parts of Typescript, while leaving out the bad ones.

It's also extremely fast and multi-platform.

It also doesn't have the fragmentation that Java or JVM langs has.

And it's also open source nowadays. I think Sillicon Valley hasn't caught up with those recent changes, I bet more startups would be using C# if they knew.

I love C# and .NET and I use them extensively but I dislike the fact that the framework still kind of forces you into OOP.

If you like to have a more functional workflow you have to roll your own stuff or wrap objects in functional constructs.

But .NET is excellent for startups because:

-it is very fast to develop in

-has excellent tooling

-it is batteries included

-generally you have ONE way to do things that is accepted by most developers

-documentation is very good

-it supports large codebases with ease

-community is large enough

-you can use it for many areas, from embedded, to high performance computing, to desktop, mobile, web backend and web frontend

-it is performant

Don't know how trustworthy is this but it seems like it never was on top30: https://hnrankings.info/45888620/

This has 74 upvotes and posted 16hrs ago.. @dang?

Every since they got rid of the Microsoft packages feed, it's just been a complete mess.

Ubuntu's own documentation states:

> .NET 10 will be available in the Ubuntu archive for Ubuntu 24.04+ and included in main upon its official release

But it isn't available?

I wish CPP development was as robust as C# development is

Seems like a good update, though! And I'm glad it's early enough that updating the framework probably shouldn't break anything. Really as long as there's no issues with the DearImGUI dependency (would be a surprise!), I'm pretty happy about the update.

Yup.

dotnet tool install --global dotnet-ef --version 8.0.8

It looks like they got someone from Apple to write their press release.

[1]: https://learn.microsoft.com/en-us/dotnet/core/compatibility/...

Edit. I was not aware that the gap between System.Text.Json and Newtonsoft narrowed, take my comment with a grain of salt, please!

Yes, a lot of great features have been added over the years. But it also introduces some amount of cognitive load and confusion. Take the first new feature in the example:

> Field-backed properties simplify property declarations by eliminating the need for explicit backing fields. The compiler generates the backing field automatically, making your code cleaner and more maintainable.

Huh, I thought we have had this for years, what were they called, ah Auto-Implemented Properties- so why is there a need for this? In this example:

  // Automatic backing field with custom logic
  public string Name
  {
      get => field;
      set => field = value?.Trim() ?? string.Empty;
  }

  get;

I feel like the documentation is always somewhat lacking in explaining the reasoning behind new features and how it evolves the language from earlier versions.

Since Nadella took over, MS made some substantial steps forward: On Azure, around 30% is Linux; MS went cross platform with some of its most successful apps/ecosystems. Its not that MS behaving like a friend today, but their Dev-tools are really great - at least they care for Devs, i wish they would care for Office users as well.

C# + .NET is from my perspective the most developed and most mature eco system when it comes to business applications.

I really like it!