upvote
There's two ways to approach this — build tooling for existing Rust developers to get them to adopt the Microsoft stack, or build tooling for existing Microsoft stack developers to get them to adopt Rust.

I'd argue that the former is less important than the latter, and my understanding is that Visual Studio is still the IDE for Windows-centric development, so for those MS-first developers, Rust missing from VS means Rust is poorly supported, end of story.

reply
It would have to be the 2nd option. Who in their right mind would voluntarily choose Windows as their dev env? It will have to be those who are already there.
reply
Most people don't have a choice. Corporate IT has choosen what I run my machine on. I have used a native linux machine, but since my email is still on outlook, everybody uses teams, and all the non-code documents are on windows I end up having to have a windows machine. Linux in a VM under windows ends up being the easiest workflow (though I'm just starting to try WSL and so far it is looking good)
reply
> (though I'm just starting to try WSL and so far it is looking good)

WSL is really nice, as is Windows Terminal. I particularly love its fonts (but that's probably just me).

reply
Did they ever fix terminal performance?
reply
Mostly, yes. They didn't really apologize for the abuse they sent towards Muratori but they did essentially wind up with the architecture he proposed.
reply
I think just running cmd still uses much less memory but Terminal is much, much faster than it was.
reply
Outlook and Teams are both web apps, or at least they were when I last used them. Even if you download the "native" app it's just Electron. I haven't had trouble using either of them on Linux.
reply
Outlook is native. There is the new web version that it says don't use (yet)
reply
Which sends your login data straight to microsoft
reply
Plenty of us do, so far Valve has failed to make native builds for Linux appealing for game studios, even though they already have to deal with similar APIs on Android, iDevices and PS/Switch.
reply
This kind of stuff is why its hard to have good conversations about tooling. Windows is the best place for many kinds of software dev, but perhaps not the kind you are doing.
reply
When it is not the mandated option, under what circumstances is Windows the best choice for software dev? The only domain I can think of is gaming, and Valve is seemingly coming up fast to eat Microsoft's lunch in the next few years.
reply
Game development, graphics programming and GUI tooling.

The alternative being macOS, if Apple actually had competitive prices for all kinds of world economies.

reply
Valve is certainly increasing the viability of Linux as a platform for gaming, but I can't see developers targeting Wine or Linux for a major game over Windows directly. Not for a decade, if ever.
reply
Visual Studio brings a lot to the table for C++ development. Specifically the Debugger, although IntelliSense also often succeeds at queries that stump clangd.

If they can replicate that capability, I think it can be a draw.

I was a mac / Linux guy before my current gig, but Visual Studio is so much more capable than XCode that I basically only use the Windows machine except to debug mac-specific issues. Less so, now, admittedly, that the malware scanner process is literally always pegging a CPU core.

reply
Visual Studio does have a really nice C++ debugger - one would imagine the C++ debugging capabilities should translate to Rust.
reply
Hot code reloading, and incremental linking would be great, given the build times.
reply
deleted
reply
> Because it takes time.

That's an excuse, not the reason.

IntelliJ RustRover has been around for years.

Similarly, VS Code has had Rust plugins written by the community in their spare time years ago.

reply
> Even with coding agents

Because of coding agents? :D

reply