Wow, you're serious. So FYI, postgres has had FTS for decades. TIN is possibly an improvement on existing PG behavior, but proprietary to planetscale.
Mongo's older search system was strictly worse than ancient standard FTS on postgres. About five years ago Mongo added more sophisticated search options. Standard PG search has been pretty stagnant, but there are PG extensions (like TIN, some proprietary some not) that add more sophistication.
In the mean time, Mongo doesn't let you use SQL unless you're directly a customer of MongoDB. The native primitives for aggregation in Mongo are ghastly and feel like the era of RDBMSes before query planners were a thing. Plus transactions... are relatively new.
I've used Mongo, there are things I like about Mongo, but the main benefit is horizontal scaling and the main penalty is any query more complex than get/put is hard. Whether that is worth it (especially compared to alternatives like CRDB, TiDB, or Spanner) is really very specific to you.
This. We also thought MCP was useless, but now the workflows by ChatGPT and Claude are so good; it's as good as installing an app from the App Store. We launched MCP for our SaaS and immediately found users using it.
API and MCP all are just buzzwords for customers. What they care about is whether they can get tasks done in our SaaS using Claude or ChatGPT. If that happens, it's a success.
My company uses MCP in production to connect different AI products together that were developed by different teams. It makes the connections very easy, where a REST interface often has quirks and features that you have to understand.
That's fair. REST isn't much of a standard. MCP can be just as badly designed and documented as REST, but at least there's a standard for authenticating and listing the options. Reading through other top-level comments, this seems to be the theme. MCP usage is mostly driven by ease of connection.
Basically it's just bundling the API documentation into a standard format to plug into LLMs, if you're comfortable running prompt injection on yourself and downloading random text from random websites and telling your favorite LLM to use it to access your banking information.
I'm not sure I would call that riding. With all the poses I suspect this was some odd-ball cult practice. I'm sure the archaeologist who had to polish that knob on that anthropomorphic figure in that one panel #3 has some good stories. Probably significant that its the smoothest part of that figure.
The old joke about what they call a chicken fucker in Oklahoma comes to mind here except I think those pre-Turks were cavorting with leopards.
I was going to say that these ancient furries were about as much proto-Italians if not more than proto-Turks but then I noticed you said pre so maybe you meant simply that they predate the Turkic invasions.
I was trying to say that with the anthropological and archaeological data that we have available right now the best we can do is say that they pre-date the groups that are peopling the region today whose histories we understand. It is possible that some of those groups resident today share ancestry with those who built the sites but it is also possible that the original builder groups moved on due to environmental, societal, or other pressures we are not currently able to document.
Maybe the ones who built this site went to the Spanish/French border and are the ancestors of the Basques, who have a unique language. I'm not the guy to answer that question.
If I wanted to identify this group's descendants among modern people I would look for people who have a deep connection to cats like the ones depicted in their monuments.
And now you know why I am not much of an archaeologist. I get a little tired of every polished rock being something someone worshiped though it looks like for these people that probably fits.
Turks, and yes the Basques, among other Europeans, have a large amount of ancestry that is close to these people but specifically it peaks in Sardinians.
Technically, everyone could be descended from their closely related neighbors who got sick of the cat people, rather than from the cat people themselves, though.
Jason, here is a story about how much your work impacts us.
We run a decently sized company that processes hundreds of millions of images/videos per day. When we first started about 5 years ago, we spent countless hours debugging issues related to memory fragmentation.
One fine day, we discovered Jemalloc and put it in our service, which was causing a lot of memory fragmentation. We did not think that those 2 lines of changes in Dockerfile were going to fix all of our woes, but we were pleasantly surprised. Every single issue went away.
Today, our multi-million dollar revenue company is using your memory allocator on every single service and on every single Dockerfile.
For website hosting, it's okay but not great. We encountered issues when we tried to cache a lot of images. Their CDN storage seems really low compared to Cloudflare and Cloudfront. It results in a really bad hit ratio the moment we try to deliver a lot of images.
Ok so for hobby projects it wouldn't make sense to switch then, but glad to hear it works for you. I haven't been in a position where it would make sense - I have hobby projects where I don't care much about reliability, and then there's the infrastructure the company I work for uses and that's all on AWS
Seriously so happy to be running our production stack on mongo.