jbonatakis

Big shout out to the Udvar Hazy Center in Chantilly, Virginia which has both an SR-71 and the Discovery Space Shuttle, as well as a bunch of other really interesting aircraft.

What makes you wonder about that other than the word "Open" in their names?

z.ai is a fairly well known AI lab out of China and their GLM models are probably the most popular outside of Anthropic or OpenAI’s. I don’t think it’s presumptuous for them to not introduce themselves in a post on their own blog, I think you’re just a bit out of the loop here.

The whole video seemed generated to me

I honestly don’t think I could blow through a 20x plan in a day if I was trying. What are you doing that uses so many tokens?

Yet. But it’s built by the guy who created Vitess and cofounded PlanetScale, so while it doesn’t have sharding implemented at the moment I think it would be foolish to discount it. Plus it’s open source.

Multigres is the one that comes to mind

This doesn't even make sense. Postgres is and has been open source since the 90s and AWS has had an existing Postgres offering since approximately always.

They acquired Crunchy Data and now have some of the most prominent Postgres developers working there.

> I'm still waiting for a Postgres provider to just let me mirror data directly to Iceberg, so I can plug in my own stateless query engine.

The issue that each of those providers above has recently adopted Postgres as a secondary product aimed at supporting their main product, an OLAP database or engine, so they don’t want you plugging in your own query engine.

I’d bet you’re likely to see this from a Postgres-specific provider first, like Supabase.

I’d like to second this. Being able to change the color using the dial would be…satisfying.

I’ve built a similar thing against Snowflake, with one added layer: tenant-scoped views with the ID baked in, and an associated tenant-scoped role that only has read access to its own views.

It also lets you make updates to the underlying table (shared between all tenant views) and then separately update the views. As long as you aren’t making breaking schema changes you can more easily validate the changes before releasing.

> A data warehouse on the other hand is an OLAP database and is optimized to work on columns

A bit of a pedantic nit here: a data warehouse is a usage pattern. It’s not necessarily tied to any specific technology, however it is commonly implemented with OLAP systems like Snowflake, BigQuery, etc. But there’s nothing stopping you from building out your data warehouse in Postgres or MySQL. If you’re stitching together disparate datasets to build a unified model for analytics, you’ve got yourself a data warehouse no matter what system it lives on.

This is how I feel with my Airpods. Just break already!

That’s well beyond what a stock Postgres server would reasonably handle