I don't trust languages named after the creator, Philip.

As for the safety dispute, my quick search said that Fil-C has managed memory (gc named FUGC) and runs about 2-4x slower: you decide.

At those prices I wonder if it also reviews the design for ineffectiveness in performance or decomposition into maintainable units besides catching the bugs.

Also the examples are weird IMO. Unless it was an edge/corner case the authentication bug would be caught in even a smoke test. And for the ZFS encryption refactor I'd expect a static-typed language to catch type errors unless they're casting from `void*` or something. Seems like they picked examples by how important/newsworthy the areas were than the technicality of the finds.

Here's an idea: allow downvotes for green posts with published guidelines on when downvoting is and is not appropriate. We can collectively filter out the pure spam efficiently to make it less worthwhile to post.

These details don't detract from the efficiency. The postal code can prefilter every other field which can frequently narrow down to one. I would leave the ability for the user to override with free form data entry as data isn't perfect and changes over time.

I don't remember asking for "efficiency" in typing out an address, something we teach children how to do. It doesn't seem like a societal problem worth iterating over.

These tools are more than often wrong, and cause more grief for the user than any potential help it could provide.

There is no developer in the world that knows this data better than the person typing it into the form.

I'd like any person or system asking for my information one field at a time to minimize my time and effort to give it to them.

When they make erroneous assumptions, which they often do, they steal more of your time and effort than it would take without "assistance".

I bet a large majority of Americans have their city and state uniquely identified by their zip code

if it's not unique, a trivial fallback would be to not populate anything, and that's where we are today

What always bothers me with enums, sealed-types, etc is that I can't compose a new ad-hoc set based on elements of someone else's enum. You can make one using the other but not the other way around, TypeScript's is more general.

Of all the features only the M6 processor and maybe C2 modem interest me.

Because it's my 'dev machine' an OLED display only raises the price.

Well you could have a virtual particle whose mass could be time-averaged.