nsfw936421

Maybe only counting new/edited LoC in that language. But also probably not completely fair.

It certainly does. It's way simpler to keep up all invariants and to review the few percent lines of code in unsafe blocks than making sure that the 30 million lines of code are free of undefined behavior.

Is some part of the code it battle tested of course it's complete unreasonable to rewrite it in any language, but if you have to do a major rewrite anyway or write a new component you should definitely use a memory safe language. And no it doesn't matter that there is an unsafe escape hatch because it's literally impossible to write low level kernel stuff or FFI to other languages without unsafe because Rust can't uphold/guarantee the invariants of the hardware itself or the behavior of other languages.

As said it's possible to edit PDFs but of cause it's a pain in the ass because that format doesn't have a lot of semantics information about the original source. PDF doesn't understand how to reflow text to the next line.

It's a bit like having a Photoshop file with many layers, saving the image as PNG, sending that PNG to someone else, they open it in Photoshop and than complain about why Photoshop is trying to prevent the PNG from being edited.

You can edit the PNG but it's a pain in the ass because the original layer information is lost. Same with PDF. Nobody ever tried to prevent anyone from trying to edit PDFs but of it's more that fixing some minor typo is certainly is a pain in the ass because thats not what this format was designed to do.

It's also not feasible to deconstruct a PDF. It doesn't have a concept of paragraphs and lines. Almost all semantic relations and information is lost while saving a PDF.

To be fair PDFs are not meant to be edited (especially not by Word). PDFs are the product not the source. It's like trying to "edit" the ingredients of a cake after it's finished. You don't edit the cake, you edit the recipe and make a new cake.