Shoothe

> It’d be fair to say that I could’ve written an equivalent service in Ruby in a tenth of the time it took me to write this one in Rust.

Ha, I had the same feeling when I needed to create a simple REST service that'd just process a request using command line tools. Seems easy but Rust's tooling is full of rough edges. Code completion sometimes works sometimes doesn't, cargo cannot install dependencies only (without building source) so it's not good for Dockerfile layers, etc. etc. Borrow checker is not bad at all for people that worked with languages with explicit memory management (where you do ownership tracking in your head anyway).

Long story short I spent 2 days working on the service and had 80% done but figured out the rest would take twice as much if I want this to be production quality. I scraped the project and rewritten it in node, using one or two dependencies in 2 hours.

I'll be trying Rust again surely and I'm glad that articles like this one exist!

I'd be interested in looking at the generated IL, especially for nullability info and default interface methods.

Yes, WebAuthentication will supersede U2F and it's backward compatible (meaning you can use your Yubikeys, but the API is different).

I guess they mean extra API that utilize stuff that's in HTTP/2 but not in HTTP/1.1.

I wonder what do they do with Service Worker updates that the browser normally does every day or so. Do they somehow block install and activate events? If not then the attacker just needs to update the worker and the history repeats.