I have noticed that C/C++ developers that deal with backend server technologies are very much likely to resort to PHP for some reason. I have noticed it from serveral developer friends of mine or simply by noticing how the topic comes along sometimes on web discussion forums.

I believe this is the reason why certain extension codebases that deal with php are(for the most part) exclusively done in C++, take Phalcon, written as an extension in C or PHP Swoole, which is written in cpp iirc.

I wonder what attributes does the language, or the tech stack as a whole has that would make this particular kind of developers feel attracted to the platform. Is it that is easy and widely available and they just say "fuck it, I don't wanna spend too much time in this shit" <--- which is a very valid point really.

Or them just having an innate preference towards it?

The Psychology Behind Developers: By Dr AleCx04

My programming paradigms unit has decided to explore different teaching/learning environments by creating lecture/workshops. Imagine a massive room with big projector screens at the front and smaller screens lined up against the wall at the back. The lecture room seats are designed around tables that are gradually elevated so it’s similar to a lecture hall but you’re sitting at discussion tables.

There’s the usual lecture with all the slides up around everywhere, there’s nice wheelie chairs and dimmer lighting... can’t tell if we’re at a conference or some awards night. Then all of a sudden, we’re coding in teams (tables) and uploading our work on to forums to discuss with the rest of the lecture hall. WHAAAAAAAT

Really different and quite enjoyable experience, there’s more than one tutor walking around to help, there’s mics for people to present.

Just sharing my new experience of forward learning environments that didn’t cause feelings of anxiousness for once or boredom. It was kind of mind blowing, wish it was always like this.

I thought some days ago, what if there was a tool that, working also with the versioning system, offered kind of a "chat" or comment section to files, folders, even deleted ones?
So you can see the meta commentary without going through the actual versions of the code (unless necessary, hence the "working with the versioning system")?
Say there was a file, index.js, and this thing would look like this:
- COMMIT: Created file.
- COMMIT: Updated exports.
- Coder 1: This file was a pain when working with the dependency, be careful about that.
- COMMIT: Added new function.
- Coder 2: This file is also needed in project X.
- Coder 1: @Coder1 Can I know why? We already deprecated this tool.
- Coder 2: @Coder2 It was needed by a dependency that wasn't.
- COMMIT: Fixed typo.

Again, this would be accessed from the file itself, say a button on the IDE that said "Open comments" or something.
Things similar but that wouldn't be the same: Docs, forums, discussion "hubs"... wait, discussions, like Wikis have. What do you think? Does something like this exist?

Discussion forum software: what is the most stable and secure as well as regularly updated package out there?