Hiding the complexity behind nice interfaces makes it actually more difficult to understand programming.

This is a very important point, that most of my colleagues with OOP background seem to miss. They build a bunch of abstractions and then say it's easy, because we have one liner in calling code, pretending that the rest of the code doesn't exist. Oh yes, it certainly exists! And needs to be maintained, too.

I don't like being on this picture.

Stack overflow.

Celsius is tied to points of ice melting and water vaporising. Since water is very important for the life on our planet, it makes even more sense than arbitrary chosen meters or seconds.

Isn't there rule 34?

Password=a");drop table users;--

Alas, it's longer than 16 characters. Protection works!

Gopher, the Go language mascot mixed in with Rust language mascot.

Q-tip fits the ear. Dick fits the bun.

Are those both chicken breast?

I've already made this choice. Switched from C++ to Go, and now I never want to touch another language at all. Since I'm not writing kernels or embedded, Go is pretty fast for everything else. Not very popular in gamedev, but that's just a lack of 3rd party libs, specifically native graphics support.

As for other languages, I can't justify unnecessary complexity that is generally welcome by those language communities. Go is straight simple yet powerful, and I admire that.

Which adds up to 180%. And that is all you need to know about deadlines.

I wonder if you deem Firefox buggy or having not enough features?

Using Firefox since it came out and never experienced any troubles.