My read is that no customers will leave since they are much more interested in news coverage -- and this helps the AP focus more on news.
This is a tangent, but I wonder if they feel that they are just creating LLM training data and that few readers (even of Sunday papers) will actually read their reviews.
I wish there were some explain plans in either post, since I don't get what's going on.
If the query uses the index, then the on the fly tsvector rechecks are only on the matches and the benchmark queries have LIMIT 10, so few rechecks right?
Edit: yes but the query predicates have conditions on 2 gin indexes, so I guess the planner chooses to recheck all the matches for one index first even though it could avoid lots of work by rechecking row-wise
S3 Tables is designed for storing and optimizing tabular data in S3 using Apache Iceberg, offering features like automatic optimization and fast query performance. SimpleDB is a NoSQL database service focused on providing simple indexing and querying capabilities without requiring a schema.
This is very cool. Kuzu has a ton of great blog content on all the ways they make Kuzu light and fast. WebLMM (or in the future chrome.ai.* etc) + embedded graph could make for some great UXes
At one time I thought I read that there was a project to embed Kuzu into DuckDB, but bringing a vector store natively into kuzu sounds even better.
I was also very fond of Phabricator (all though my team preferred GitHub style pull requests) but I haven't had a need for it recently, so I haven't tried phorge myself.
On Chrome, I solve my too-many-tab issues with an extension [0] that closes the LRU tab once a threshold is reached (10 for me). I find the tabs I need are open and wide enough, and the tabs that autoclose were not useful anymore. About once a month I'm doing a research task where I actually want many tabs and I turn it off temporarily.