Implications of Rewriting a Browser Component in Rust
This is in tune with my own experience using Rust in production: it can stop you from doing certain classes of mistakes, but it won&#x27;t stop you from doing stupid things.<p>But the idea that I don&#x27;t have to think about certain classes of problems allows me to give these stupid things more focus, which is surprisingly refreshing.<p>The predictable nature of Rust was so refreshing for me that I ended up using it even for smaller reusable scripts where I would happily have used Python before but soon got annoyed with obvious errors that would only show up once you run a program.<p>If you e.g. have a `print foo` in some obscure branch that rarely happens, that print will ruin your day if you use Python 3. If python would be a little like Rust you would get on save (or at least on compile) a hint or error, that the print should look like this: `print(foo)` for Python 3. You can be incredibly careful and rust will still catch things now and then, that would have gone unnoticed into production unless you have immense test coverage.<p>I <i>like</i> Rust for the experience I had with it. It definitly changed how I approach certain problems in a very good and productive way, even when I don&#x27;t use it.