Applet actually.
The notion of an "app" didn't come until 2008 with the iPhone.

Your memory is partially correct. What it was actually touted as was:

“Java: A simple, object-oriented, network-savvy, interpreted, robust, secure, architecture neutral, portable, high-performance, multithreaded, dynamic language.”

Well I would pick b, because it isn't a hexadecimal digit.

{ 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F } are hexadecimal digits.

There's nothing dumb about it at all. First of all, the prefix 0b cannot be confused with a hex digit because you need the prefix 0x to get hex.

Secondly, if you're concerned about b looking like a hex digit, well, there's your problem. Lowercase hex digits are the devil's work. Always write hex digits using uppercase letters, as $DEITY intended.

Finally, what the hell is the z supposed to stand for in 0z?

I completely, totally, utterly, and vehemently disagree with you on that.

Given a choice, I think autonomous cars at some point WILL be programmed with such a choice. For example, hitting an elderly person in order to avoid hitting a small child.

FTFY.

And the ship just happened to have enough fuel to change its course and make its way to a some star instead of wherver it was going? In a time-frame short enough that the human brain inside the robot didn't die? Doesn't seem likely to me. Also, that fireball that was supposed to be a sun exploding was pretty unrealistic. I mean, a sun doesn't look like a fireball, and a supernova explodes pretty much instantaneously from your ship's point of view. It's doesn't gradually expand like that. You get hit by it expoloding and you're gone. There's no pretty fireball.

Thanks for posting that explanation. It helps me not completely feel like I wasted my time watching it. That said, I think it would have been much better as a 10-page short story.

And just one's own laziness. I mean, if someone has a disability that makes using the shift key difficult (for example, you only have one good hand, or you are looking at pr0n while writing code), then I sympathize. But if they have no such disability, then they're just lazy. It's not that difficult to type an underscore character.

What is meant by "inside" in this context?

That issue was great.
https://archive.org/stream/sta...

The GP said 200MB, not 200mb.

That said, yeah, even 200MB is a joke at 20mbit/s.

If you say some person's weight is 400 pounds, and it's pointed out to you that no, their weight is in fact only 208 pounds, and you try to argue that 400 was "close" to 208, then you probably would only have about 1 person in a million agreeing with you. A factor of 2 is not "close", and a factor of 10 is not even remotely close. I think you're confusing logarithmic closeness with geometric closeness.

Fine; we can agree to disagree on what "close" means.
But back to the original point... Why did you quote the wrong figure (400k/day) on an article that you yourself linked to?

400k/day is wrong by a factor of two. That's not "close" by any stretch of the imagination, especially considering that 400k/day is a yearly growth rate of 2%, while 200k/day is a yeary growth rate of 1%. Those growth rates are fundamentally different when compounded.