efromvt

Hah I suppose it’s all relative on fast - Trino’s certainly intended to support ‘interactive analytics’ vs being a pure ETL platform. Def seconds vs milliseconds for Druid/clickhouse/duckdb in general though.

As a huge duckdb fan, I can’t think of a workload set I have where the two overlap, so I don’t see them as competitive - I would either pick Trino/Presto or DuckDB as the obvious solution.

Yeah there was a vibe shift towards OpenAI being much more competitive for daily use and then Opus 5.5 hit. Will be curious to look back and see if that shows in data. Of course, could change tomorrow.

This is super cool! Been looking into procedural tree generation for a project and that paper is a great starting point.

Given that most of their improvements here are positioned as RL on their last base train, seems like just doing some additional RL would work fine?

You gotta have that octopus body with distributed intelligence

Was excited to take a Waymo, loved the entire experience, would extra love it when they reenable highway usage in LA.

I think you can model this as locked down buckets, wider engine access (spark/presto/etc), and apply the controls at the engine level. (it's not inherently different from making sure your DB files are locked down, if you squint at it). This does obviously block any non-engine access which has downsides. I agree that it is generally much less mature with lakehouses than eneterprise DBs.

I unironically love that we've come back around to the hive metastore (there are pros to the decentralized and centralized catalog, it's good to have options)

Love competition in the local data SQL space, makes everyone better

I think a service that simplifies things enough can get people to pay for it, but semantic layer is tough because you often also do want to encode sensitive information, you need to minimize latency, and it’s in the critical path of a bunch of other stuff. You’d need to differentiate quite a bit vs a local hosted option with more flexibility. That’s why semantic layer vendors are often semantic layer ++ ; you want to hook into an ecosystem to get sticky. Doesn’t mean it won’t work!

I’m a big fan of the strict naming as an abstraction above tables and reuse as blend key approach, it also greatly simplifies aggregate resolution like you have. (Landed on the same abstraction level when building a semantic model personally).

Lots of 404s on the docs pages - might be worth an audit of links?

Data is the remaining moat! (Though I LOVE the amount of accessible public data and WASM has really lowered the barrier to performant data driven UIs (webgl here though? Maybe it’s just agents), so not advocating for more moats, enjoying all the cool products )

I actually agree with your point overall, but Falcon 9 uses the Merlin, not the newer raptor 3 for starship which is more 3d printing and has had some teething issues (no definite causation, and I expect they’ll get it sorted).