Looks like it was misattributed as CC BY 4.0 but it should be CC BY-SA 2.1 Japan

You don't need to call it amateurish. It's free.

Those two ideas are not mutually exclusive. A thing can both be free and suck.

Here's a crazy idea. What if we are looking for AGI in the wrong place? We built a global internet. If we do achieve AGI maybe it will be a globally distributed one. If it did would we even know what to look for?

This is just awful. I can't even contemplate a more nuanced rebuttal because I don't want to engage with it. I feel more sorry for children today because of articles like this are being written about them.

I agree, this is like reading about how "lazy" or whatever my generation was when I was younger which we all know is BS now. It is angry assholes that want to an excuse to blame everybody but themselves for the state of the world.

I only learned about their CDN and protocol called Xet a couple of days ago https://huggingface.co/docs/hub/en/xet/index That puts it in the Cloudflare of AI models category.

SEM_EXTRACT, SEM_MATCH, WEB_SEARCH are pretty vague functions. Makes me wonder why you'd bother with the SQL part at that point and not just ask the question.

You need ways to sift through large amounts of unstructured data and do data analysis after. We created these functions to be able to use LLMs to parse unstructured data from the into structured data which we then process with a SQL like engine to map/group/filter etc.

I worried about this myself. 50% higher limits were nice but the flip side is you get used to it and then it just feels like they're taking 50% away. I'm not sure it's going to have the effect that Anthropic was expecting....or maybe that was the point. Who knows. I can see both perspectives.

Reminds me of the DBOS, everything's a database, ethos. https://www.dbos.dev/

Isn't "everything in a database" what AS/400 and PICK operating systems do?

Then there was Microsoft WinFS, which promised much but got killed in ~2003. A shame.

I'm excited about this and have some use cases already lined up but I'm continually worried about a grammar free-for-all and collisions as each extension author tries to modify the grammar. I'm hoping they already have something in place for that and I just haven't read about it yet. I'm concerned that you can load an extension and kind of mangle the interpretation of the syntax. Two author extensions could legitimately want conflicting parsers and there's no easy way to unload an extension in duckdb. Something like an explicit "GRAMMAR SQL" or "GRAMMAR GGSQL", etc would be nice.

Told them?

I have and the suggestion was received positively. Thanks for the suggestion to do that. DuckDB rocks!

What do you plan on stripping and what's your target? The Emscripten based build is ~10Mb. I have a component build so I'd be interesting on how you'd like to break it up.