> [At Microsoft] we’re excited about the possibilities. While there are many questions still left to figure out about how Rust fits into the overall Microsoft engineering story, we encourage others to join us in taking a serious look at the language for their systems programming needs.
@codesections Why worrisome? Do you think they're planning a coup by not really understanding Rust and then flooding crates.io with un-Rusty packages?
> Why, [do you find Microsoft's enthusiasm for Rist potentially] worrisome? Do you think they're planning a coup by not really understanding Rust and then flooding crates.io with un-Rusty packages?
Nothing so dramatic as a coup :)
But Microsoft is *really big*, and if they get into Rust in a big way then, very suddenly, a *large* fraction of the language's users would be Microsoft folks.
And it's only natural for the priorities of a language to reflect the needs of its users
@codesections Mozilla's running it. It'll probably be fine.
> Mozilla's running it [#rust].
Not anymore. Mozilla folks are pretty influential (which shows how powerful a large org with lots of paid open-source contributors can be!) but Rust is self governing.
> It'll probably be fine. Probably.
Agreed. That's why my take is "potentially worrisome" and not "we're all doomed!" :D
Yeah, fair enough. But, from the same post, here's their list of priorities:
> how to regulate the usage of the “unsafe” superset of Rust at scale, lack of first-class interoperability with C++, and interoperability with existing Microsoft tooling.
Those are *not* priorities for me, so, meh
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.