How is he dunking on .net?

I think one of his main points is server .net was (and is) great.

But the UI part of it was cloudy.

I see it as complimentary to the post not contradicting it.

The UI part is exactly what I meant. WinForms was a godsend for professional developers making line-of-business apps, because previously if you used first-party dev tooling, you either had to deal with the considerable limitations of Visual Basic, or you had to deal with MFC that was low-level enough that all the things that were tedious about Win32 remained tedious. In comparison, Borland had Delphi, and there was a good reason why it was so popular back in 90s and early 00s, and why Microsoft ultimately acqui-hired its main designer specifically to work on .NET (and it very much shows in the design of both C#, which owes as much to Component Pascal as to Java, and of WinForms, which is so similar to VCL).

With WinForms, we actually got something that was convenient without shackling you. And the whole cross-language story was great, too, especially around .NET 2.0 - with C++/CLI you could very easily wrap any random native code C or C++ library for consumption from .NET, with end-to-end integration in the build system, IDE etc.

Eh, WinForms did a lot to make Win32 UI accessible and usable -- especially layout and easy customization -- but I have to differ on the cross-language story. It was great, IF you were making primarily a C# program that happened to use some C/C++ components.

From the native code side, it was not so great. The .NET 2.0 CLR had very poor support for hosting from the native side and really wanted you to make a program that was .NET first, it didn't work well if you wanted something like primarily a C++ program that hosted a C# UI in the same process. Reverse P/Invoke via native exports wasn't exposed, so creating DLLs for consumption by non-.NET programs was difficult. Mixed mode debugging was and still is painful, with the debugger being glacially slow at some operations like OutputDebugString() processing and blocking some native features like data breakpoints, and the CLR eating access violation exceptions from native code so they couldn't be debugged properly. Build-mode wise, we had to ban C++/CLI assemblies depending on C# assemblies because the C# project system didn't handle incremental builds properly and forced the dependent C++ assembly to rebuild all the time.

These issues still largely exist and are an issue with WPF. It's a great UI framework, but it's unusable unless your front end is primarily a C# program.

The guy getting std’s from Russian girls who Warren Buffet doesn’t talk to anymore.

That Bill Gates?

Seems he might have other priorities these days?

Lot of SMBs run sql server and .net

lift and shift into the cloud used to be the path of last resistance on Azure.

I still remember the day the disks dissappeared on the prod db running on gcp.

What is property tax?

Rent.

Then income tax is rent too. In fact both are taxes, the rest is meaningless rewording.

The stock is tanking. Their moat is small to non-existent.

Kind of crazy considering how while teams (even dev) were forced into using it be the designers.

I haven’t even seen it mentioned at work recently.

It is truly staggering to see a tool used by (almost) every large tech company in the world so quickly lose ground. I don't think they're done done, but their position in the value chain has shifted drastically.

It’s manager speak for “less than.”

The manager class sees worker units as fungible.

Must be from the divide and conquer school of management.

Should Accounting exist?

Should Legal exist?

Should Facilities exist?

Surely your average employee could own each of these functions.

And the worst job market maybe ever for that age group?

But that decade includes the first Trump administration also.

I don’t think that supports your argument.

What is probably happening is the job crisis for young people.

The army is once again an attractive job.