3 ms·
The blog post proposes an incremental migration. From the next to last section "How can we change programming language?": > The reason I am writing this post
by rectang 6y ago
The blog post proposes an incremental migration.
From the next to last section "How can we change programming language?":
> The reason I am writing this post is because device emulation, the main security attack surface for VMMs, can be done in a separate program. That program can be written in any language and this is where Rust comes in. For vhost devices it is possible to write Rust device backends today and I hope this will become the default approach to writing new devices.
For all those criticizing the knee-jerk impulse to rewrite, you're arguing against the wrong post!
- xiphias2 6y agoIt seems that the controversies in the comments come from the inexact title. It should have been ,,Why QEMU should incrementally move from C to Rust'', or something similar, that reflects the content of the article better.
- roblabla 6y agoOr maybe people should read the post instead of reading too much into the title?
- afiori 6y agobut the title is important, it claims that the article will give sufficient reasons for QEMU to stop using C in some natural sense and move to Rust. if this is not the reflective of the content or it is a tongue in check exaggeration following a c common template (similarly to the "considered harmful" titles) it is reasonable to criticize the title (it is less reasonable to criticize the article under the assumed content)
- pdimitar 6y agoI'd expect a technical audience to be already aware that any such efforts can only ever be incremental -- so your elaboration would be redundant.