While I appreciate the functional approach outlined in the article, there are alternative and, in my opinion, more practical ways to write composable and functional SQL queries embedded in a host programming language using query builders. For example: https://news.ycombinator.com/item?id=42265668

We've been using a multi-TB PostgreSQL database on ZFS for quite a few years in production and have encountered zero problems so far, including no bit flips. In case anyone is interested, our experience is documented here:

https://lackofimagination.org/2022/04/our-experience-with-po...

You don't actually need a dedicated ZFS backup program. A simple cron script will handle incremental backups just fine. If anyone is interested, the script we use to backup our multi-TB PostgreSQL database can be found here: https://lackofimagination.org/2022/04/our-experience-with-po...

The 1-min compile time for TP5 doesn't sound right to me. I used Turbo Pascal versions from 3 to 7 back in the day, and all of them were quite fast (one-pass compiler). Turbo C++ was another matter though. The same example programs compiled drastically slower (seconds vs minutes).

That is one thing I really miss. TP was defacto language to teach in exUSSR.

In many cases,TP or later Delphi followed as IDE for real apps. Pascal had its issues, but compilation speed was insane. When most people switched to java or c#, we lost this. Authors of both could have not used language so similar to C, but it happened.

I dunno, maybe I need to adjust and think before compiling, or switch to Go.

No foreign keys are used. A separate database table is used to track relationships.

You've guessed it right :) An entry in the relationship table looks something like this:

  {
    "id": 6,
    "sourceComp": "user",
    "sourceId": 2,
    "targetComp": "post",
    "targetId": 3,
    "type": "author",
    "createdAt": "2024-03-28T13:28:59.175Z",
    "updatedAt": "2024-03-28T13:28:59.175Z"
  }