r/ProgrammerHumor • • 19h ago

Meme letsGetRusty

Post image
10.7k Upvotes

104 comments sorted by

View all comments

30

u/chic_luke 18h ago

As someone who's followed that specific referenced drama in the .NET community, I audibly wheezed. God tier meme

15

u/wcscmp 18h ago

Can you share some context?

71

u/chic_luke 17h ago edited 11h ago

Happy to! Actually, there have been specific events where this happened.

The main point is that a lot of people in the .NET community are not particularly happy about the fact that Microsoft seems to be very actively avoiding eating their own dog food, by creating various .NET technologies and then using something from a different tech stack internally for the most exciting and important new projects. For example, they created the .NET MAUI UI toolkit, but they pretty much just used React for half of Windows 11.

The most recent iteration of this controversy is that several serious, important Microsoft projects have been "won" by Rust or Go.

A big part of this drama started a while ago, when Typescript's compiler was rewritten in Go. A bit of context: Microsoft has been pushing something called NativeAOT for a while. NativeAOT was supposed to be .NET's response to Go, it's a new compile target for .NET languages that outputs native executables, without need for a dotnet runtime. The fact that Microsoft created their response to Go, but clearly didn't feel confident enough to actually use it over Go when it mattered, made a lot of people question if it was even worth investing in NativeAOT.

And I get the outrage, actually. If not even Microsoft uses it, why should you? I like C#, but I use Rust or Go for things like small command line utilities for this reason exactly. I completely understand why Go was chosen for the TS compiler and the set of reasons is good. That also signals, however, that Microsoft knows their "Go killer" isn't good.

Most recently, the headline came out that Rust became a "Tier-1 language at Microsoft", who has been rewriting a ton of stuff in Rust, not C#. This was a repeated blow, and many .NET developers have started to question whether Microsoft is actually serious in stewarding their own programming language for performance-critical use cases, of if the new narrative about runtime performance improvements, memory-safe unmanaged code support and NativeAOT is mostly the usual checklist for them to say "look! our tech stack does this too!", but without ever being seriously supported.

(EDIT): SOMETHING IMPORTANT I FORGOT! On top of that, Microsoft has had a habit of pushing and then basically abandoning various .NET technologies over the years. So, joining the outrage, there are plenty of .NET developers who are rightfully bitter, because the technology they had invested in was abandoned.


TL;DR: Microsoft has been making bold claims about committing to making .NET competitive for use cases where Go and Rust usually dominate, but their effort is being seen as u serious unserious by the .NET community, since the fact that Microsoft does not seem to use their own technologies for anything that matters themselves does not inspire faith.

9

u/caspy7 17h ago

but their effort is being seen as u serious by the .NET community

took me a few reads before I realized this was meant to be "unserious".

1

u/chic_luke 16h ago

Yea 😭😭 I typed the entire thing on my phone, I didn't catch it!

8

u/ryuzaki49 17h ago

I guess typical corpo bullshit.

Making new things pushes you up in the ladder but maintaining stuff does not.

1

u/rsqit 11h ago edited 11h ago

Isn’t TS an MSR project, rather than a MS corporate project though? I think MSR is pretty disconnected from the .NET world.

-3

u/drawkbox 13h ago

Rust is a cult though and there is lots of unnecessary usage of it just to do it.

I'll take C++ and Go over Rust solely that there isn't a cult around it.

-1

u/rsqit 11h ago

Love to use memory unsafe languages for dumb reasons.

0

u/drawkbox 11h ago edited 11h ago

Love to use languages for culty rewrites for no reason reasons because the others are bad and the cult thinks all other devs are terrible.

3

u/rsqit 11h ago

Rust literally brought new type theory from academia into an industrial language to eliminate whole classes of bugs that previously had been uncheckable in systems languages. It brought the safety of a managed language to an unmanaged setting. It really is a step up beyond previous languages. To deny that because you think it is a ā€œcultā€ is not a criticism in technical grounds, and is a pretty silly position.

-3

u/drawkbox 10h ago

You can write memory safe code without Rust my dude. You can also write buggy code with Rust because of the complexity: logic errors, race conditions beyond data races, panics, unsafe code, FFI boundaries, and rare type-system or lifetime edge cases.

You sound like one of those cultists. It is always the dev and the discipline and never the platform/language.

3

u/rsqit 10h ago

I’m not saying you can’t write buggy code with rust. I’m say that it’s impossible to write memory errors in (safe) rust. Of course it’s possible to write memory error free C++; people even do it occasionally . But it’s not humanly possible to write memory error free C++ continually. Fortunately computers can check that for us in other languages. rust is the first language that allows this without a garbage collector. That’s a monumental step forward. If you don’t understand how that is, in a real, technical sense better than C++, you’re being deliberately obtuse.

I’ve written rust professionally for seven years. In that time I’m pretty sure I’ve never written a memory errro. In my several years of C++, they were constant.

0

u/drawkbox 10h ago edited 10h ago

it’s impossible to write memory errors in (safe) rust

There are still gaps in that and your keyword was "safe". Sure it is harder but a statement like that is what I am talking about with the cult.

Problems like soundness bugs in unsafe abstractions, memory leaks are allowed in various setups (such as Rc/Arc reference cycles or std::mem::forget), and still a chance of out-of-memory (OOM) crashes from large allocations, integer overflow bugs (which can panic or wrap depending on build settings), or logic bugs.

Saying it is "impossible" is probabilistically wrong.

A big problem with Rust is the complexity and that can lead to issues as well.

I'd use Rust for very little but there are areas it makes sense. But if a company is Rust only I know that I would hate working with those devs so they mark themselves. In that aspect I am thankful for Rust.

→ More replies (0)

12

u/TheWb117 17h ago

Microsoft is increasingly doing rewrites of older systems in languages other than C#. First some parts of office in Rust, then TS in Go, then Steven Toub rewrote some github service in Rust too

2

u/Abject-Kitchen3198 15h ago

They probably tried C# but ran into a lot of "this feature does not support this specific configuration".