The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

X : Our executive team is concerned that we need to up our game in order to out innovate Amazon.
Me : Do you map?
X : Yes
Me : Like this?
X : No. What's that?
Me : A map of a tea shop.

X : Why is that a map?
Me : Long story, all to do with how space has meaning. To keep it short, maps help people to focus on user needs, the components involved, to communicate missing components and scenario play ideas like staff becoming robots.

Me : They’re also good for measuring and managing capital flow, making investment decisions, removing bias and getting rid of duplication.
X : I don’t see how that helps with innovation?

Me : Well, innovation is a tricky word because we use it to describe many things. If you’re talking about differentiation with the adjacent unexplored then you’re experimenting in the “uncharted” space e.g. immortality with magic provided by the special custom built kettle.

X : That sounds like nonsense.
Me : A lot of what people think will be the next great innovation is nonsense. Actually, most of it is. That’s the nature of the uncharted space, it’s experimental, high risk and generally results in failure.
X : We need more reliable innovation.

~8yrs ago (Dec’12) I got a job @Google. Those were still early days of cloud. I joined GCP @<150M ARR & left @~4B (excld GSuite). Learned from some of the smartest ppl in tech. But we also got a LOT wrong that took yrs to fix. Much of it now public, but here’s my ring-side view👇

By 2008, Google had everything going for it w.r.t. Cloud and we should’ve been the market leaders, but we were either too early to market or too late. What did we do wrong? (1) bad timing (2) worse productization & (3) worst GTM.

We were 1st to “containers” (lxc) & container management (Borg) - since '03/04. But Docker took LXC, added cluster management, & launched 1st. Mesosphere launched DCOS. A lot of chairs were thrown around re: google losing this early battle, though K8 won the war, eventually 👏

We were 1st to “serverless” (AppEngine). GAE was our beachhead -- it was the biggest revenue source early on but the world wasn’t ready for serverless primitives. We also didn’t build auxiliary products fast enough. Clients that outgrew GAE wanted “building block” IaaS offerings.

1st to hadoop (map-reduce ‘04) but our hosted Hadoop launched in ‘15. AWS EMR was ~200M ARR by then. 1st to cloud storage (GFS ’03), but didn’t offer a filestore till ‘18! Customers were asking for it since 2014. Didn’t launch archival storage or direct interconnect till v. late.

Java was first released in mid-1995, just 6 months before JS.

By 98, when I went to college, Java was already used for all the first level courses in the CS program.

How did it catch on so quickly (just 3 years) to shift university curriculum, which is usually so slow/behind?

I wonder why Java was so respected and JS was not? Why/how was Java already seen as such a stable and mature language?

Not just Java, other languages (like python) were also released around/near 95, and also seemed to get to "mature" respect status. much quicker.

I bring all this up because my impression of Java in 98 was that it had been around "forever" (as had C++ first developed in 79, but not standardized until 98!), but that's not. true at all. These were all new languages around the same time.

I'm sure the language designs had different merits, and the target applications meant a different perception and reception, but...

it sure seems like the industry (and academics) just decided Java and C++ were the stable mature ones and langs like JS were toys.

BTW, before you assume JS was nascent/immature b/c the web wasn't much of a thing yet, remember that JS was actually released as LiveScript on the server before it was released in a browser. So "server-side JS" was always part of the story, not just Node 15 years later in 2009.

Ever wondered how the JVM debugger 'Evaluate' feature works in IDEs? Long ago I thought that the Java debug interface (JDI) actually allows you to specify the expression and get back its value.

However, this is not quite possible: there's no Java language compiler inside the JVM. When the process is paused JDI allows you to read or write any variables and fields or even execute an existing method with given arguments. But nothing like addition or multiplication.

On the other hand, #IntelliJIDEA debugger allows you to evaluate even statements! You can write there `for`, `if`, `while`, `switch` - whatever. You can even declare local variables. So how this works?

The answer is simple: IDEA debugger has a built-in interpreter for Java! If you access an existing variable or a field, call a method or instantiate an object, it queries JDI. Otherwise, IDE itself does all the calculations.

The amusing thing is that debugger authors didn't bother to make it as strict as Java itself, so the language inside the interpreter is a much more permissive version of Java. For example, you don't need to initialize variables there! Default values like 0 are used automatically.

People sometimes ask me what my vision of DeFi is. This is a very tough question. DeFi is very messy with thousands of experiments happening. But high level, I think DeFi will go through 2 phases:

During the 1st phase (next 2-5 years), we'll continue to build games, casinos, and speculative products.

This sounds uninspiring. But it has two main important consequences.

1) This will ultimately lead to hundreds of millions of users to install wallets and get uncomfortable with the UX.

2) This will force the tech (especially scaling) to mature.

Once we've achieved these two goals, phase 2 begins. In phase 2, products that serve real economic activities / integrated with the real economy will be built and flourish.

Right now, such products barely exist. @terra_money comes to mind. But this is the kind of products that I really look forward to. They are more economically sustainable, and create more value.