more experiments.

It’s good at all kinds of stuff that is search adjacent, “find amesent parks with water feature within 100 miles of me that have rv parking nearby”, etc

This will of course never be underminded by aggressive marketing

Rote classification doesn't require AI. You described a SELECT statement that was developed half a century ago

Pseudo SQL

  select l.id, l.name 
    from locations as l 
    where l.type = 'amusement_park'
      and exists (
         select id from locations as l2
            where l2.type = 'rv_parking'
             and distance(l2.geo, l.geo) < $nearby_distance
      )

But what we should have is a good map software where you could filter by type and distance (How many amusement parks can be in that circle?) and quickly check if there's a RV parking nearby.

The hard job is collecting the data.

Anthropic should buy you

China

while ClickHouse can scale down to compete with duckdb, I dont believe (but happy to be corrected) that duckdb can scale up like ClickHouse can.

most people dont have that scale problems, but when you do...

I can see their logic - instead of breaking people's builds, they are being the nice guys and letting you pay them back later. BUT, any time you break convention, you've dipped into your trust budget (even if you communicate it way more clearly than was apparently done here.)

Same price for regular and cheaper fast mode. Happy for these incremental improvements.

for LLMs as implemented today?

How can you cut latency by more than 1x? I am no intending to be snarky, it just doesn’t fit my brain how you can reduce a measure time by more than the original starting time.

Put differently, 1/40 is not the same as 1x - 40x. I’d phrase as Reduced by 97.5% or 0.975x

There are two ways to express such ratios, and both are equally valid. (Though "x" is usually reserved for "40x" and "%" for "97.5%".)

You're absolutely right!

taalas!!!