This is a really good point that wasn't fully clear to me - this post definitely focuses on the \COPY from psql, rather than the CopyFrom backend.
I've gone ahead updated the post in the introduction to highlight that this post is about `psql`. My goal here is to try and understand Postgres better - so thank you for pointing this out :). I think writing a future post going into the backend code you mentioned is necessary. My goal is to have solid reasoning on why `COPY` is faster, and I'll need to keep writing these posts to get there.
Let me know if you think it's still unclear - I don't want to leave up any article that's potentially confusing.
I've also cleaned up the language a bit around `libpq`, I mistakenly restated the description of `libpq` from the Postgres , which is stated as "libpq is the C application programmer's interface to PostgreSQL. libpq is a set of library functions that allow client programs to pass queries to the PostgreSQL backend server and to receive the results of these queries.", but you two are correct, my statement was confusing.
One wonders if ChatGPT could self-replicate - using these API keys as a bootstrap. Lots of individual users computes would certainly lower the threshold for being cut off for billing reasons.
One wonders if eventually - historians will plug all the content from a person's personal notes, their diary, their chat logs, into an LLM, and perform research by talking to the AI about the person's life?
If you trained an LLM against all the recorded discussions of Einstein - is it that different from talking to Einstein himself?
In theory, you may be able to ask the LLM about the person's life, as if it was the person, but you won't get more facts out than you provide as input. It may still make up credible info.
Regarding your last question, it wil lack an enormous ammount of data that make up a person's experience. Moreover, talking to sound like <X> isn't the same as thinking like <X>.
It reminds me of the later part of the book Accelerando, where synthetic personalities made up from historical records (could be anyone from Cleopatra to Newton) keep being reincarnated in a near, post-singularity future. They are handed out an FAQ that tries to bring them up-to-date on the current state of affairs.
Of course you can not do any research - discover new things - by doing this. The AI can only repeat what it has been fed or make up lies. You cannot discover new material by using AI.
One level further: the historian asking questions is itself an AI meaning as soon as primary sources are provided, interesting history insights flow out.
Only illegal to not accept cash for debts. A merchant can refuse to do business with you in cash since you're not in debt at the checkout counter (as no transaction has occured)
Ah, I thought it was the claim about "legal tender". As in, my folded-up $10 bill is legal tender, and you (the vendor) must accept it, even if you don't like dealing with cash registers, coins, petty theft, and counting change.
Generally been a fan of these sorts of models - SQL data is very malleable - and treating the tables as movable from the start really helps move faster as a developer - database migrations become easier as you don't need to do a lot of work with API.
I can see how this would cause problems if you always used this in production after finding a fit for the data model - but for rapid prototyping and development - big fan.
The original idea was inspired by PostgREST, the obvious difference is Rest tries to support all SQL databases, and it results in some design principle that Rest prefers to use a universal method instead of bind to PG features(e.g. use PG role for user authorization). Generally PostgREST is more mature now if you are using PG.
Thanks for liking it, I also think it could be a good tool to help developers for rapid prototyping and development.
I find that this will wipe out a lot of Software Developers who are doing something that isn't really unique - and people will move on to more interesting work.
The internet wiped out travel agencies - but opened a new, more interesting world of better products (Expedia, Google flights, etc.) that made travel more accessible to everyone. Instead of travel agents - we hire software developers to benefit everyone
I'm pretty anti-TikTok - but shouldn't we have some evidence - or any knowledge of who this material came from - before trusting a reporter from Forbes?
I read through the article - but I couldn't find any details on the source this reporter is citing. Worryingly - the author "held policy positions at Facebook and Spotify." Instagram is a major competitor to TikTok - so conflict of interest is pretty strong.
As other posters pointed out - every major company tracks people. We've known about this type of behaviour for decades from big tech.
