Therefore saying "I'm straight" or "I have a boyfriend/girlfriend" is saying - I fuck people of opposite sex. Also sex is a certain biological attribute, not only intercourse. But I guess you're 14 and ain't getting any.

Therefore when people publicly announce a pregnancy - that is nothing more than gloating that they had great sex.

I'm yet to see a straight guy be shamed for being straight. Many are shamed for having a lot of random sexual encounters, but they are quite proud of being straight and fucking many girls.

Illegal and socially acceptable are different things.

Fine. If that's the case, would these "evil rich" do us all a favour and pay for the overwhelming publicly funded protection they get?

Communism arose from the notions of self sustaining communes. It's not scalable, but is very widespread.
Your family is communist. The Amish are communists. However, having the whole country communist dos not work because we don't trust each other.

JVM JIT tends to be the best

Yes... Micro benchmarks are exactly the best way to verify real performance. /s

Banks don't want to leave JVM, they don't care much about Scala or Java....

C/C++ are great when it comes to highly predictable data flows or very small modules. Otherwise it's extreme cost of constant profiling of the code to actually identify the changing patterns that cause slowdowns. That being said, C/C++ can be much more than 2x performance of a JVM.

And what 32 bit integer is not a 32 bit integer in C/C++ or Java?

1: Those bounds checks come at a cost of having overflows getting in the way of actually checking bounds. An overflow of an unsigned value results in just a small number... that means that you still have to check the lower bounds no matter what.
2: They store the same number of values as unsigned, it's just handling of those values and comparison operations differ. A signed and unsigned 32bit integers store 2^32 values.
3: Crypto algorithms do not operate numerically, thus 2147483647 * 100 will yield exactly the same result for uint32 and int32 as much as any crypto algorithm is concerned.
4: Therefore you send 2147483648 in binary form as 4 bytes = 0x80000000

The fact that lack of unsigned integers has not stopped Java shows that the designers made the right choice. If you need to have a value larger than 2bn you will probably not be satisfied with 4bn and will need a larger type. And in general, you rarely need to operate numerically without a sign.

I hope you are kidding here, because that is far from the case. Java is still the de-facto language for most server-side applications. RoR never outgrew it's hipster background. It has been 7 years since RoR had it's hype peak... The hype waned and RoR is still a rarity.

Your assumption of the intention for the default methods is incorrect. They were a result of mixin envy, not adding new default implementations for future proofing.
Java developers tend not to have issues with future proofing for new functions in interfaces.