paveway

So you're saying Google Wave was an undertaking born directly out of events that happened here on HN?

That's not what I remember about Google Wave. Where are the moments of these facts recorded?

And because that protocol didn't work, they killed off and/or radically altered unrelated chat and RSS products?

I don't feel that's true. Google has implemented other new consumer facing protocols and products since then.

What are the pieces that tie together Wave, Reader and XMPP integration, other than timing and the fact that RSS and XMPP are open standards?

Although cyberwarfare and technological vulnerabilities that affect ballot collection and counting seem to be more potent than gerrymandering at this point, with modern elections.

Gerrymandering probably still matters in swing states like Ohio and Florida, but only if modern tampering methods have been ruled out everywhere else.

And benchmarks with rigor, I might add. Noting important dependencies that match chipset, bare metal CPU architecture/bus wiring and compiler choices.

In particular, I've spoken with people who have cited significant differences in performance, when using proprietary compilers matched to vendor CPU chipsets, for Linux/OpenJDK compilation, which then changes the profiling of the JVM benchmark, on the same bare metal crate.

Meanwhile, L2 cache misses, due to object reference churn, are the final deal breaker with the JVM, if I've read correctly and read enough about JVM performance. Beyond even garbage collection overhead, fundamental JVM performance cannot be tuned to optimize CPU cache use.

Briefly paraphrased, the JVM performs messaging/referencing with String references, that look like "java.lang.Object@%HASH_CODE%" and when you instantiate and garbage collect many instances (millions of those hellishly long fully qualified java names) across many operations, costing many cycles, you'll always suffer incurred latency, because most of your objects are frequently populated and then evicted from the L2 cache, no matter how long they actually live in the JVM heap.

I don't have the link handy, or I'd post it.

But long story short, even though a JVM benchmark may be performant, benchmarks do not peg CPU resources according to real life use cases.

And changing the OS, motherboard, and compiling from source on your own physical hardware can provide benefits that might not be obviously worth the extra effort to compile from source bootstrapping all the way from the kernel to the JVM, before deploying your java artifacts.

I feel like the Google Drive/Docs/Hangouts combo pack provides all the things that Wave was supposed to be, no?

All the ground-breaking features, such as live interactive multi-user caret presence are part of Docs. Did Wave promise more than that?

What are the missing pieces that got lost along the way, and never made the jump?

How about buying them a phone, and a $20 gift debit card, and then letting the app store jackals have their way with whatever happens to the rest of the cash, until it's all spent?

Probably a horrible idea, considering all the other complexities of the internet at large, and some of the careful supervision it necessitates.

I mean, consider the sad tale of "Slender Man."

https://www.theguardian.com/world/2015/mar/13/slender-man-st...