why was Bitcoin written in C++?

[Zoomic]

But, and this is a huge BUT everybody in the office knows PHP everybody in the office can deal with any issues if they come up.

As I mentioned above, this is a bit of issue when you are working as a team. In my team, we have few new guys who are coming from the Vue library background but majority of us have been working with Angular. But then, we have to readjust to Vue because the framework is easy to learn.
The consequence was delay in task management as we depended on documentation for few days.
Choice of language is sometimes a problem when you are not a solo programmer. I read somewhere that people were helping Satoshi to write codes as he didn't do it all alone.

[1715524906]

1715524906

[1715524906]

1715524906

[1715524906]

1715524906

[so98nn]

I am not sure if this has any relevancy but I know one company named as 63 moons. It’s a multinational conglomerate and operates in various financial domains as well. Most recently they have started their own crypto currency exchange and they also have pre existing stock market exchanger.

The programming and full stack development has been done in C++ language itself. Most of the developers they are choosing has extensive knowledge of C programming. When asked to friend working at their firm named “Ticker Enterprise” they said it is both simple and hard language but it is most common in the field of information technology. This could mean that it’s just that it is most basic language, it is the language where everything starts really. That could be the reason for the same.

[Jerayer]

Modern CPUs have many cores. Some parts of blockchain applications parallelize perfectly (like checking digital signatures) while some parts don't parallelize at all (like executing transactions in order). Modern C++ has a very good mix of effective inter-thread communication and optimization of single-thread performance.

C++ doesn't have a run time that stops the world or manages memory, giving your application consistent control over this behavior. Move semantics allow you to get objects that behave like values (i=j; a+=1; does not change j) but perform like references (deep copies are avoided except where needed).