I was curious. The best entries for D on physical hardware:

    JSON serialization:    144 of 366
    Single query:          152 of 404
    Multiple queries:      195 of 394
    Fortunes:              154 of 371
    Data updates:          99 of 365
    Plaintext:             81 of 352

I don't think anybody really cares about the Techempower benchmarks. Else we'd all be using Vert.x or so.

The most popular frameworks having the 90% of deployments, are at the middle to bottom of the Techempower benchmarks.

I think people thinking about using D care a lot about benchmarks. The reason "most popular frameworks" are in the middle to bottom of the list is becaue they are made with dynamic languages which are/were very popular for ease and speed of development, with a huge number of web-programming functions baked in.

On the other hand, you will note that go / rust and C frameworks (which are playing in the same field as D) are on the top of that list.

We actually do care about those benchmarks. At a certain scale it matters how many servers you need to run a website with millions of visitors. 90% of deployments do not have this problem, yet saying nobody cares is a bit silly.

At that scale do you use a stock framework though?

An advantage of D in that situation is how easy it is to change the internals of an API without those changes propagating to the surface, both by design (e.g. UFCS, no brackets) and how that design is used (e.g. Templates)

Yes you do. You do not want to write everything yourself.

Wow, Rust is a beast.

I think this is more of a measurement of how much effort people have spent implementing the benchmark, e.g. Based on a cursory look six months, a few of the rust ones seem to have been implemented with some parts from scratch rather than just hammering it together like the D implementation.

There was also one where dmd was faster than ldc, so something must be up somewhere