The article isn't very clear but assuming it's a 16-bit numerator and 8-bit denominator, then MSN's answer to [0] lays it out (although for higher bit sizes). If the denominator was 16-bit, then the top-rated answer (by caf) to the same SO question seems like another approach, but that wouldn't be a one line change.
My layman understanding would be that you're not gaining anything other than a more abstract model. If you want performance, the code is going to boil down to the equivalent linear algebra + quaternion operations.
I agree that they shouldn't have re-edited the movie based on Carrie Fisher's death IRL, but that scene is a masterclass in bad writing.
Rian's intention was to demonstrate some semblance of humanity remained within Kylo. But the optics are that he is truly weak and in the end isn't even bothered much by the (for all he knows at the moment) imminent death of his mother. Had Kylo fired the shot he at least would have surpassed Vader in evilness, whether or not Leia saved herself.
I agree with the "fans" that she should have died in that scene, but since Rian was too scared to snuff Leia before Luke the scene shouldn't have been written in the first place.
Rust compilation is strict but not cruel. The suggested fixes associated with compilation errors are very friendly to beginners (one notable exception is errors around lifetimes).
Your concerns regarding "feature creep" are reasonable and would be expected for a language trying to displace C++.
