3 ms·
I rather stick with PHP or JS, due to having a JIT in the box for such cases. Since I learnt Python starting in version 1.6, it has mostly been for OS scriptin
by pjmlp 1y ago
I rather stick with PHP or JS, due to having a JIT in the box for such cases.
Since I learnt Python starting in version 1.6, it has mostly been for OS scripting stuff.
Too many hard learnt lessons with using Tcl in Apache and IIS modules, continuously rewriting modules in C, back in 1999 - 2003.
- int0x29 1y agoI don't think the JIT will help that much as each request will need to be JITed again. Unless Node and PHP are caching JIT output
- ChocolateGod 1y agoYes, both do.
- int0x29 1y agoOn the file system? CGI is a whole new process per request edit: Looks like yes for Node JS. I can't tell for PHP as I keep getting results for optcache which is different and in memory.
- pjmlp 1y agoMy point wasn't using them with CGI, rather that they have JIT in the box, nodejs with V8, PHP has zend and its own JIT since Facebook efforts with HipHop and later Hack (HHVM), both with server support as well, no need for CGI approach.
- vanviegen 1y agoNot sure what the current situation is, but PHP used to ship with APC, a shared memory cache, that enables this exactly. Even without filesystem overhead! I still miss PHP's simple deployment, execution and parallelization model, in these over-engineered asyncy JavaScripty days.
- fulafel 1y agoPython got a JIT recently (an experimental / off by default feature in 3.13).
- pjmlp 1y agoFinally, are still far away from the competition. Also lets see the impact of Microsoft's Python team layoffs on it, given that CPython developers only started caring about performance due to Facebook and Microsoft, so far the JITs in Python have been largely ignored by the community.