If you have room for just a little bit more frustration...
Lol. Okay, I'll bite.
Out of curiosity I looked back at your original benchmarks and was wondering what you would expect to be "good results"?
That is a discerning question since the meaning of "good results" is bound to be subjective without defining some criteria.
To me, that term means showing performance, productivity (RAD), or both. In regards to productivity, I was thinking primarily of doing more with less (ie. fewer lines of code); to a lesser extent, ease of library/extension management; and, minorly, a general feeling of compilation time.
Here's a little of my backstory for context. I've recently become interested in ActivityPub (World Wide Web Consortium protocol for decentralized social networking). While looking at the languages used for various implementations, I saw that most were written in scripting, or some form of JIT compiled scripting, languages. Only a few are written in truly compiled languages, including Golang and Rust.
I thought that creating an open-source project for ActivityPub in Free Pascal might be a great way to showcase FP, get some eyes on it, and perhaps garner some interest. The question I needed to answer first, though, is would FP produce comparatively "good (enough) results" to counter the undoubtedly forthcoming question, "Why should Free Pascal be used when we can have A and/or B with X language?"
So, I did a 'net search for, "simple multi-threaded http server example in X" where X = (Free Pascal | Golang | Rust). Simple examples were easily found on page one of the results for Golang and Rust. A simple FP example (from Rosetta Code) wasn't found until page two; which, I suppose, is understandable since the know-it-alls say that Pascal is a "dead" language.
My tests show Golang to be almost three times faster than FP. And, the example I found on Stack Overflow, which I adapted by removing just two lines related to timing, is only fifteen lines of code including whitespace.
It took just a bit more to adapt the multi-threaded (MT) server example in the Rust community's, "The Book". I ended up with 27 lines and performance, surprisingly, slightly worse than that of Golang.
Neither Golang nor Rust required me to exercise package installation contortions to implement a simple MT HTTP server. To be fair, neither did FP when using 'fphttpserver', but it seems that is not an acceptable solution.
Using the Apache HTTP server benchmarking tool to send a total of 500 concurrent requests, FP gives consistent total times in the low 200's of milliseconds. Golang is consistent at around 70-80ms, and Rust, 80-100ms.
So, it appeared to me that, comparatively speaking, both Golang and Rust have both A and B; Free Pascal, not so much. Hence, my disappointment.
I'd be glad to post the relative code and benchmark results if you're interested.
And, just BTW...
fpc takes some getting used to, but once you do it's a wonderful tool.
I don't doubt that at all which is why I keep taking yet another hopeful look. It's not getting used to the tool itself with which I have so much difficulty. It's trying to navigate its ecosystem.