There is an equivalent syntax in Rust to both of those examples, and in both cases I find it less verbose. The template variant is roughly equivalent to:
fn func<T: FloatingPoint>(fp: T) { ... }
And the "auto" variant is similar to impl argument in Rust:
From your description, it sounds like they decided to use a "number" typed field for the post codes. This is of course incorrect, post codes are really just strings. While the bug manifests itself on firefox, it is hard to blame it for implementing the field according to spec [1]. Chrome decided to ignore the spec and leave the field more free-form, which in turn enables developers to use it incorrectly without detecting the compatibility bug.
> User agents must not allow the user to set the value to a non-empty string that is not a valid floating-point number. If the user agent provides a user interface for selecting a number, then the value must be set to the best representation of the number representing the user’s selection as a floating-point number.
Electron is pretty much the same nightmare anyway. Just because it runs in chromium doesn't mean it preserves the sandbox. All electron apps have full access to your filesystem and os, even from their chromium window context.
Fuzzing isn't really practical if all you do is just generate a totally random bit stream for input. There are many much more clever and robust strategies to hit as many edge cases as possible. Check AFL[1] for some details on generating smart random input files. You can also combine that with pretty advanced dynamic execution analysis to fuzz against unknown processor instruction sets, like in sandsifter[2].
Well, the support is pretty decent in evergreen browsers (and it already was for a while), and in case of electron, you have precise control over your runtime, so it's not really a problem. Also many engines have already done quite substantial optimizations for handling wasm modules in combination with JavaScript. It's all done with backward compatibility in mind, so what works today will continue to do so.
There exist a great one, which is called Figma. They use electron in combination with WebAssembly to make it fast. I'd say that's a pretty decent choice.
There is also Figma, which is a direct competitor to sketch that is multiplatform, and they indeed run on electron (and even directly in browser). For me that's a great example of electron app done right, as you won't really notice any performance issues.
And the "auto" variant is similar to impl argument in Rust: