georgewfraser

Yes this is a dbt product - will be in the dbt cli soon, we shipped it initially as a separate tool while it’s in preview.

AWS is a great home for DuckLabs. They just want people to use more compute and storage, so they have a degree of technology-neutrality. This is the key to allowing DuckDB to continue to grow in whatever directions are natural, rather than being warped by some kind of walled garden data platform strategy.

What pgbouncer does is indeed core functionality. Compare Postgres to MySQL and sql server, where analogous standalone connection pools are rarely used. The fundamental reason pgbouncer needs to exist is Postgres’ utterly retrograde design. Other examples: xid wraparound, conflict with recovery, lack of undo space.

Slack is such a simple product, and is so strategic as an interface for AI, Anthropic has to be considering building their own Slack. Hopefully this tag approach is an MVP and it proves the potential of workplace messaging as an interface for AI, but also the limitations of relying on the extension points they salesforce chooses to provide, and it turns into a full fledged slack competitor from anthropic soon.

I assure you I wrote it myself

Claude-in-Slack is a big enough feature to overcome the slack-connect network effect. Openness is absolutely key! I wrote this post because I hoped that if Anthropic is already planning to do this I might be able to influence them to make open-data part of the plan. But openness by itself isn't a big enough feature to get users.

Also true! The most important thing is that the NewSlacks commit to interoperability. I think Anthropic has a special opportunity to lead the way here, because they have a track record of standing by their principles to an extraordinary degree.

You can only access public channel data, you can't even access that at scale, and Claude needs to be more natively integrated in ways that Slack will never allow.

I talked to the timescale CTO at pg conf a few years ago and asked him what timescale does differently than a standard columnar database that makes it better suited for time oriented data. He said a bunch of things and I said “but columnar databases do those things.” Then he got mad at me.

I guess it’s just another columnar dbms after all?

They make a really good criticism of Iceberg: if we have a database anyway, why are we bothering to store metadata in files?

I don’t think DuckLake itself will succeed in getting adopted beyond DuckDB, but I would not be surprised if over time the catalog just absorbs the metadata, and the original Iceberg format fades into history as a transitional form.

This is exactly right. We even went so far as to build a proof of concept internally, and the technical challenges are just very different. The simplest way to explain it is that Fivetran connects a skinny pipe (APIs) to a fat pipe (databases) while Census connects a fat pipe to a skinny pipe.