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?
For this precise reason, I've stopped buying things like baby food, baby toiletries, skin lotion, etc. from Amazon. I now purchase direct from the respective online store, or sites like walmart.com/target.com
Furthermore, this kind of stuff always makes me wonder if/when other genus will eventually evolve into "intelligent" beings (with "intelligent" being loosely defined).
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.
Anyone use the Eisenhower Matrix? A few really productive people I know seem to use it to great effect. Was wondering if anyone here has any tips with their experiences.
Props to Business Insider for writing this piece. I like to call them the "TMZ of Business News" - but once in a while they do very good reporting/pieces like this.
Of course it's hard to say if they completely, 100% invented anything from scratch. But they sure did "pioneer" a lot of unique practices that other software companies were not following at the time.
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.
> Mostly just stuff any competent company would/should be doing. it's google though, so they act like it's super awesome.
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.)
(Or I guess you could write Scala in a non-functional, Java-y way, but that would defeat the purpose of using Scala...).