Originally Windows was written in assembly and ran on top of DOS, but since Windows 2000 and XP, it’s been exclusively running on the NT kernel, which is written primarily in C, with some C++ in there as well.
Microsoft is quickly writing more and more Rust code these days. They rolled out Rust kernel components even before Linux, and their efforts actually include rewrites rather than making the API available to developers.
There’s decades of code in Windows, but the successful conversion for DirectWrite font parsing is probably a sign of things to come. MS seems to even be porting some COM modules to Rust, which would be the last thing I would start to port (so many pointer pointers!).
Atom usage dropped off dramatically in favour of VS Code or the fully open source VS Codium, there’s no point in Github writing it’s own code editor when it’s hosting a much more popular, more powerful, and equally open source editor in one of its repos.
There may be good examples out there, but I’d argue Atom isn’t one of them. VS Code was clearly intended to be a spiritual successor with MS branding IMO, it is a fork of Atom, and it is equally open source (MIT license).
Originally Windows was written in assembly and ran on top of DOS, but since Windows 2000 and XP, it’s been exclusively running on the NT kernel, which is written primarily in C, with some C++ in there as well.
The actual userspace is mostly C++ and C#.
And basically the entirety of dotnet 6 forward is spans. It’s all spans. All the way down.
Microsoft is quickly writing more and more Rust code these days. They rolled out Rust kernel components even before Linux, and their efforts actually include rewrites rather than making the API available to developers.
There’s decades of code in Windows, but the successful conversion for DirectWrite font parsing is probably a sign of things to come. MS seems to even be porting some COM modules to Rust, which would be the last thing I would start to port (so many pointer pointers!).
True! Their embrace of Rust is certainly heartening to see.
Let’s just hope they don’t follow it up with the other two E’s in their typical playbook.
Please do go ahead and name the last open standard that Microsoft intentionally destroyed.
EEE is the fucking boogeyman on Lemmy. You just mention it’s name and a bunch of nerds shit their pants and upvote.
Atom died about 13 months ago.
Just because they’re in a relative lull in the desktop space doesn’t mean they’ve stopped.
Atom usage dropped off dramatically in favour of VS Code or the fully open source VS Codium, there’s no point in Github writing it’s own code editor when it’s hosting a much more popular, more powerful, and equally open source editor in one of its repos.
Github had been funding development of Atom until MS bought them, put Atom on maintenance mode for 4 years, then killed it.
There may be good examples out there, but I’d argue Atom isn’t one of them. VS Code was clearly intended to be a spiritual successor with MS branding IMO, it is a fork of Atom, and it is equally open source (MIT license).
@masterspace @entropicdrift https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish#Examples_by_Microsoft
Unless I’m missing something, the most recent example there is from 2002 which, to my own horror, was more than 20 years ago.
I did upvote… but my pants are pristine