Live data from Hacker News

Taking PHP Seriously (2016)

slack.engineering

1–10 of 150 posts

Re: Taking PHP Seriously (2016)

#6
So the entire argument is that PHP is single threaded and each request starts with no state? Am I missing anything else?

I’m trying so hard not to rant here, so I just wanted to confirm that those are the only positives he outlines about the language.

Re: Taking PHP Seriously (2016)

#8
> Slack uses PHP for most of its server-side application logic, which is an unusual choice these days. Why did we choose to build a new project in this language? Should you?

We already know the painfully obvious answer to this question even if it's not listed in the "reasons": because the technology decision makers were comfortable with PHP and they wanted to use it.

Re: Taking PHP Seriously (2016)

#9

> Slack uses PHP for most of its server-side application logic, which is an unusual choice these days. Why did we choose to build a new project in this language? Should you? We already know the painfully obvious answer to this question even if it's not listed in the "reasons": because the technology decision makers were comfortable with PHP and they wanted to use it.

is this terribly different from many other choices made by other companies?

"Whew... we're all totally psyched with node, and all have experience with it, know how to solve problems with it... but we're going to commit to Django. We don't want to, but we're going to."

Does that exchange ever happen? I've seen the opposite - almost every tech stack I've seen at small and medium sized companies was primarily the result of the few decision makers who had experiences (good or bad) with specific tech which influenced their decision to use X.

Re: Taking PHP Seriously (2016)

#10
This seems to be an unpopular opinion in the tech world, but I honestly enjoy working with PHP. It's such a simple, robust language, and you can use it in many different ways, depending on what you're building (OOP, scripting, microservices, etc).
Post reply on HN