@abestanway@agounardes Well, the 94% percent includes indeed people who were bumped over $1M by the QSBS income, but 74% corresponds to $1M income without the QSBS income. The real fallacy here, though, is that these percentages refer to dollar values of the exclusions, not number claims/people.
@agounardes The 94% refers to the dollar amount of the exclusions, not the number of people affected. The majority of claims come from people with much lower incomes.
Ever wanna just know if a line of code is being hit? Or how often? Or from where? In prod!?
We've been hard at work making that just a click away with https://t.co/YIJsVGr0wd!
@felixge Rando question - is there any code out there for parsing trace files that allows some degree of random access to different time spans, rather than the reader API in x/exp/trace that reads all events?
FWIW, for Side-Eye we turn traces into DuckDB, which works out nice for analysis
@asubiotto I don't really know what I'm talking about. The rationalization for LSMs that I've heard was that Google popularized them because GFS is append-only. Otherwise, in CRDB, the read-amp and write-amp are killing us, and the fact that writers externalize the cost to later compaction.
@justinjaffray @brandur After Redpanda, I think SingleStore will be the next big WASM user (and they seem to want to go beyond stored procedures https://t.co/vxuUx9VODG).
Also, Scylla, Postgres, TiDB and CockroachDB seem to all be experimenting with it. It's definitely coming to a DB near you.
@largedatabank@CockroachDB I think you're playing word switcheroo. In an open source context, "freeloading" generally means not contributing back code, not $ (to the extent that it means anything at all).
But what we all really want, as you admit, is Amazon's $, not their patches.