3 ms·
Sorry, I assumed parent meant backend and web services, like REST, GraphQL or RPC APIs, and not server side HTML rendering, that's why I excluded certain langua
by didibus 7y ago
Sorry, I assumed parent meant backend and web services, like REST, GraphQL or RPC APIs, and not server side HTML rendering, that's why I excluded certain languages like PHP. I also skipped over interpreted languages like Python and Ruby since they mentioned compiled.
Also, that doesn't look like a great metric, since it's just the number of website using a particular technology. That's going to be massively skewed by prefab solutions like WordPress and all.
I liked that the StackOverFlow survey asked people what language they used professionally. I feel that's much more relevant.
- jimmaswell 7y agoPHP is used for REST and all that just fine. Why are you excluding it from "backend and web services"?
- didibus 7y agoWell, in all honesty, I've stopped using PHP at v5, when it was all running as CGI scripts. So I'm not sure I'm doing it justice since I'm pretty outdated on its development. I've never seen PHP being used for those usages. So I probably made an assumption here that it isn't, or rarely is. All the languages I listed generally run their own server, and can handle the full request, down to its connection. While I remember PHP only managing the payloads from an existing server, running as an embedded script which the server delegated too on the last step for final rendering of the response. So for example, it couldn't manage any type of long running in-memory process or anything like that. And it didn't have direct access to IO, as that's all managed by the containing server. Things like that, which not all REST APIs would need, but is generally something I'd expect to be able to do for more generic backend work. Don't know if there are now ways to do all this.