3 ms·
1) php doesn't have to setup everything on every request - opcode caches, process pooling et al exist 2) the benefit of php over java is that php is going to r
by jjirsa 9y ago
1) php doesn't have to setup everything on every request - opcode caches, process pooling et al exist
2) the benefit of php over java is that php is going to run everywhere with no effort, and running that same java based website/service is going to start with some doc on installing tomcat or similar, which will devolve into chaos as you start working with ssl certs or shared servers
- cagataygurturk 9y agoBootstrapping a project with Spring Boot is 10x easier than dealing with some modern PHP framework's setup and nginx stuff.
- TomMarius 9y agoI usually just create a VM from a DO template and that's it, no NGINX stuff (although it's very easy, NGINX has good documentation and sane and working default configuration).
- jjirsa 9y agoFlat disagree. The php framework is going to run on every shared host in the world, and sprint boot isn't. I'm not saying PHP is better, I write java all day every day, but if I had to build a website for a random friend or family member, I'm writing it in PHP, because I know their hosting will run it.