> Rust would not have failed to compile at step one necessarily. True. In this case there was old code and new code. I assumed in a hypothetical hybrid Rust codebase, bindgen would be used to bring the types in old code…
> it's worth thinking about whether it's worth it. Totally agree we need to evaluate the trade offs of various paradigms. But, I think the most important aspect to understand is the impact on maintenance as opposed to…
IIRC, that specific bug was due to a few issues: 1. Mismatched type definitions in different translation units caused an implicit 32 to 16 bit conversion. 2. An addition to the 16 bit value overflowed, causing it to…
> Users don't care if you wrote it in Rust Totally agree! But they do care if Word corrupts a document that’s been open for 10 days (a bug that a principal engineer spent many, many weeks hunting down). > If you take…
I’m curious why we see so many papers and discussions about the difficulty in writing Rust relative to other languages. I would like to see more analyses of total cost of ownership. Yes, Rust requires approaching…
I totally agree with the author’s summary: > That trepidation and sinking feeling of “What are they going to break this time?” every time the WWDC’s date approaches, has been wearing me down in the past few years. What…
I worked on Word for years. Office has thousands of files over 10,000 lines with, uh, various degrees of test coverage and comprehensibility. After some time and experience, your mental model of the architecture ends up…
> Rust would not have failed to compile at step one necessarily. True. In this case there was old code and new code. I assumed in a hypothetical hybrid Rust codebase, bindgen would be used to bring the types in old code…
> it's worth thinking about whether it's worth it. Totally agree we need to evaluate the trade offs of various paradigms. But, I think the most important aspect to understand is the impact on maintenance as opposed to…
IIRC, that specific bug was due to a few issues: 1. Mismatched type definitions in different translation units caused an implicit 32 to 16 bit conversion. 2. An addition to the 16 bit value overflowed, causing it to…
> Users don't care if you wrote it in Rust Totally agree! But they do care if Word corrupts a document that’s been open for 10 days (a bug that a principal engineer spent many, many weeks hunting down). > If you take…
I’m curious why we see so many papers and discussions about the difficulty in writing Rust relative to other languages. I would like to see more analyses of total cost of ownership. Yes, Rust requires approaching…
I totally agree with the author’s summary: > That trepidation and sinking feeling of “What are they going to break this time?” every time the WWDC’s date approaches, has been wearing me down in the past few years. What…
I worked on Word for years. Office has thousands of files over 10,000 lines with, uh, various degrees of test coverage and comprehensibility. After some time and experience, your mental model of the architecture ends up…