> Our North Star is "1 engineer, 1 month, 1 million lines of code" Can someone explain this? Are they suggesting that (eventually) one engineer can produce 1 million lines of Rust code in a month? Or replace 1 million lines of C code? Using new "powerful code processing infrastructure"... but would it understand the semantics? Are those semantics clearly documented?
Microsoft denies rewriting Windows 11 in Rust using AI
11–20 of 113 posts
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#12Earlier quoted context omitted.
>is pretty wild How is it wild? On social media I kept seeing things like people falsely expecting the end goal would require manually reading through a million lines of code. It seemed more like people making up reasons to be mad or trying to dunk on the author.
My read was rewriting one million lines of code per engineer month using ML to do the heavy lifting. Which is absolutely batshit. There's no way that can be reviewed properly, even if it's putting all of the review work on all of the other teams.
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#13The original LinkedIn post is pretty wild. I wonder if he did a fat line of coke before writing that, or if it actually were any concrete plans that have been worked out.
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#14Re: Microsoft denies rewriting Windows 11 in Rust using AI
#15Earlier quoted context omitted.
>is pretty wild How is it wild? On social media I kept seeing things like people falsely expecting the end goal would require manually reading through a million lines of code. It seemed more like people making up reasons to be mad or trying to dunk on the author.
My read was rewriting one million lines of code per engineer month using ML to do the heavy lifting. Which is absolutely batshit. There's no way that can be reviewed properly, even if it's putting all of the review work on all of the other teams.
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#16Earlier quoted context omitted.
My read was rewriting one million lines of code per engineer month using ML to do the heavy lifting. Which is absolutely batshit. There's no way that can be reviewed properly, even if it's putting all of the review work on all of the other teams.
With this mindset I feel like you would also think bumping a C++ compiler toolchain version is impossible due to all the different changes to code generation that could happen. This is already done today and has similar issues where technically all the code can be affected, but it's not reviewed via a process of manually reading every line.
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#17> Our North Star is "1 engineer, 1 month, 1 million lines of code" Can someone explain this? Are they suggesting that (eventually) one engineer can produce 1 million lines of Rust code in a month? Or replace 1 million lines of C code? Using new "powerful code processing infrastructure"... but would it understand the semantics? Are those semantics clearly documented?
My read is Rewrite it in Rust™ for the whole MS native language codebase, but with AI doing the heavy lifting of the rewrite. Except the heavy part of the rewrite would be the review process, and I would hope they aren't trusting that to predominately ML.
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#18Earlier quoted context omitted.
With this mindset I feel like you would also think bumping a C++ compiler toolchain version is impossible due to all the different changes to code generation that could happen. This is already done today and has similar issues where technically all the code can be affected, but it's not reviewed via a process of manually reading every line.
There's a nearly incalculable difference between bumping a compiler version and rewriting it in a different language.
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#19The simple fact that they have to deny it, meaning such an absurd is widely considered plausible, is already a sign of their reputation.
Re: Microsoft denies rewriting Windows 11 in Rust using AI
#20The original LinkedIn post is pretty wild. I wonder if he did a fat line of coke before writing that, or if it actually were any concrete plans that have been worked out.
As a goal for 2030, it doesn’t seem that wild. Shoot for the moon