4 ms·
What specifically about php enabled the team to move faster than if you’d used used something like Rails, Django, or Node. (Assuming this was some kind of web-b
by jmknoll 6y ago
What specifically about php enabled the team to move faster than if you’d used used something like Rails, Django, or Node. (Assuming this was some kind of web-based internal app, since you were using php)
- conradfr 6y agoI would expect the same as with Rails or Django if they use Symfony or Laravel, but with cheaper developers.
- oatmealsnap 6y agoYea, far more web developers know PHP than Ruby or Python. Python devs don't necessarily know web development, and Ruby is pretty old-school (I don't mean that in a bad way, it's just not what they teach these days and not as applicable outside of web development).
- sroussey 6y agoNo memory leaks is always a benefit.
- digianarchist 6y agoWhy do you think PHP doesn't have memory leaks?
- derision 6y agoEvery request gets it's own process and memory space which tears down after the request is complete. Unless there's leaks in the runtime itself, you're pretty much unable to create memory leaks in your application code
- digianarchist 6y agoThat's fine for request/response cycles. What about long running background jobs?