richsinn

(Or I guess you could write Scala in a non-functional, Java-y way, but that would defeat the purpose of using Scala...).

B. What about Scala? Would you say Scala is a "good fit" for people leaving Java because it's also built on top of the JVM? Or would it be a "bad fit" because the idioms and functional-nature of Scala are vastly different than Java? Or how about Kotlin?

I'm not thinking about "successor" in terms of "Java-specific" design patterns. I'm thinking successor in terms of - can Rust, with concurrency as a first-class-citizen and C-like perf with a safer programming model, replace Java for many of the "higher-level" applications that would've typically been written in Java?

The Homo genus evolved around ~2-3 million years ago; homo sapiens came about ~250K years ago. What's not to say that 2 to 3 million years from now, there'll be some other intelligent species from other genus branches? It always tickles my brain to think about this.

Also relevant: https://io9.gizmodo.com/5780020/if-humanity-went-extinct-wha...

src: https://en.wikipedia.org/wiki/Eichmann_in_Jerusalem#The_bana...

Just sayin... :)

Check this article out: "Xi Jinping May Be Less Powerful Than He Seems" ( https://www.theatlantic.com/international/archive/2017/04/xi... )

The fact of the matter is that the outside world knows very little about the inner workings at the top of the Communist Party in China.

A specific example - the practice of keeping the entire codebase at the company under a single "source" repo. Pre-Google - it would've been considered outrageous to have the entire codebase of a sophisticated software company keep their entire software contents under a single repo. But Google did it, and other companies have followed suit successfully (as Google DNA has leaked to other companies).

Yes, of course keeping code in a single repo is not a "new invention". Linux is a single repo; many smaller companies have only a single repo because their only product is a single web app. Google keeps nearly 100% of their entire codebase in a single repo - and that was definitely a novel approach at the time.

Yes, you're absolutely correct. But here's the thing - it was actually Google that pioneered many of this. Many of the big/competent companies that are following these practices are because of Google's "DNA" leaking into those companies (via former employees bringing along the best practices learned at Google, etc.)

* https://www.scientificamerican.com/article/undergoing-fertil...

* https://toxtown.nlm.nih.gov/text_version/chemicals.php?id=24

* https://www.theguardian.com/lifeandstyle/2015/feb/10/phthala...

Of course, there's debate as to whether these similarities between the Japanese and Korean languages are a result of language convergence or divergence. But considering how close the two countries are (historically and geographically), it's probably a mix of both.

[1]http://en.wikipedia.org/wiki/Subject%E2%80%93object%E2%80%93...

[2]http://en.wikipedia.org/wiki/Subject%E2%80%93verb%E2%80%93ob...