Taking PHP Seriously • Hacker News Board

Re: Taking PHP Seriously

#671

Post by igouy » Tue, Oct 18, 2016, 7:08 PM UTC

jbergens wrote: post #509

ransom1538 wrote: post #496

Earlier quoted context omitted.

Performance? You need to update your act. PHP7 is 3x faster than python and now faster than Java 8 . The only people that can call php slow are masochistic c++ web hacks. https://blog.famzah.net/2016/02/09/cpp-vs-python-vs-perl-vs-...

Funny that people complain about js performance. In this benchmark it was 3 times as fast as php7 and about 7 times as fast as java 8. Have not checked the details of the benchmark yet.

> Have not checked the details of the benchmark yet. "Will your toy benchmark program be faster if you write it in a different programming language? It depends how you write it!" ;-)

Re: Taking PHP Seriously

#672

Post by igouy » Tue, Oct 18, 2016, 8:21 PM UTC

ransom1538 wrote: post #498

bartl wrote: post #430

Earlier quoted context omitted.

"fork" is not a major problem in PHP. In Drupal, every single request compiles a file "common.inc", of several thousands of lines of PHP code. That is what slows it down. It's remarkable that PHP still manages to do that in just 100ms. In Zend Framework it's slightly better because it includes an autoload option, which implies only PHP files that are actually used by athe request, get loaded. That way the overhead is…

Wow. Is this comment from 2003? Uh. Why don't turn on opcache [1]? PHP7 is fast. Real fast [2]. http://php.net/manual/en/intro.opcache.php https://blog.famzah.net/2016/02/09/cpp-vs-python-vs-perl-vs-...

> PHP7 is fast. Real fast [2]. You need a lot more than a "Sieve of Eratosthenes" code snippet to back that up :-)

Re: Taking PHP Seriously

#673

Post by ddw » Sat, Oct 22, 2016, 10:47 AM UTC

yxhuvud wrote: post #392

ddw wrote: post #353

Earlier quoted context omitted.

But program managers and CTOs and other non-engineers at a company care about scalability, performance, technical debt and quality, right? Let's not pretend that these don't matter once you've gone past the "users actually care about our app" phase, because they do and they affect the bottom line of a company. And IMHO PHP falters in these regards.

Managers caring about technical debt? You must live in a parallel universe. They may care about maintenance costs, but that is not really the same thing.

They don't until things break, your app can't handle the amount of requests coming in, can't insert and fetch data in a reasonable amount of time, etc.

It's at this point that shit falls apart and the manager starts to care about these technical choices and all of the time and money that will be needed to be spent to rewrite.

Call it maintenance costs if you want but those costs are directly affected by the technology decisions you make.