News for hackers. Stuff that matters.
Re:PHP 8 to Add a JIT by kijin on Sunday March 31, 2019 @12:06PM (#19536291)
PHP was practically "serverless" before serverless was even a thing. You just deploy your code with ftp, rsync, git, or whatever. There's no step 2.
Re:PHP 8 to Add a JIT by black-tea on Monday April 01, 2019 @02:11AM (#19540930)
That's not a PHP thing, it's a CGI thing. You can use any scripting language to do it. Perl was popular but you could use Python or even bash.
Re:PHP 8 to Add a JIT by michaelmrose on Sunday March 31, 2019 @01:28PM (#19536851)
How is syncing your PHP code with the server serverless?
Re:PHP 8 to Add a JIT by ronsor on Sunday March 31, 2019 @01:37PM (#19536904)
and now you see why "serverless" is misleading.

"serverless" now means you don't run your own web server, you use someone else's.

Re:PHP 8 to Add a JIT by daeken on Sunday March 31, 2019 @03:19PM (#19537674)
That's not what serverless means. It means that your code isn't running on a specific server, and between requests it isn't in any kind of running state whatsoever. It's effectively in cold storage until it's needed, then it's pushed to a frontend/edge server and run. Serverless doesn't mean that there's no servers anywhere, but rather that you don't have a webserver or set of webservers that your code is on; it goes onto a webserver when it's needed, and not before.
Re:PHP 8 to Add a JIT by beberlei on Sunday March 31, 2019 @05:01PM (#19538356)
PHP hosters have been doing this for 20 years. You have 100s of customers on a single machine, running with a single Apache/PHP process (and child forks), and only if that Host+URL of a customer is requested that PHP code actually gets executed, then completely discarded from memory after its finished.

PHP is very much comparable to serverless. All that talk about bootstrapping costs in serverless is something PHP developers have been tackling forever.

Re:PHP 8 to Add a JIT by sk5t on Sunday March 31, 2019 @05:25PM (#19538499)
This is a very silly equivalence--you're just glorifying vhosts and method dispatch.
Re:PHP 8 to Add a JIT by wwweston on Monday April 01, 2019 @05:32PM (#19548511)
The mechanism isn't the point (and vhosts aren't really either). The point is what a developer (or ops) has to think about when deploying, and in this regard, the default PHP model has a lot in common with serverless.
Re:PHP 8 to Add a JIT by zaarn on Monday April 01, 2019 @03:22AM (#19541229)
I don't see a difference there, PHP code can run on any webserver your hoster operaters provided they route the request correctly (I've once used a web provider that would rsync your PHP code to a geolocated DC if they detected more traffic from your region). If this is via vhosts or other routing methods is almost irrelevant, PHP code behaves extremely similar to "serverless" code (except it's often much cheaper).
Re:PHP 8 to Add a JIT by jjeaff on Sunday March 31, 2019 @04:32PM (#19538176)
Which is what the earlier poster was alluding too. PHP code is stateless and sits there not taking up any resources until it is needed.
Re:PHP 8 to Add a JIT by captn3m0 on Sunday March 31, 2019 @04:32PM (#19538172)
serverless and compute-on-edge are different things.
Re:PHP 8 to Add a JIT by zbentley on Sunday March 31, 2019 @08:17PM (#19539381)
You still have to deploy to Lambdas.

I believe the post you're responding to was alluding to the degree to which a lot of single-file PHP/HTML is written in a very "serverless-esque" way: no dependencies on an outer framework, and likely scales quite far compared to other languages when run on any number of servers (with the required libraries).

Re:PHP 8 to Add a JIT by kijin on Monday April 01, 2019 @01:17AM (#19540688)
In addition to what you mentioned, with PHP there's no need to start, restart, monitor, or otherwise manage your own daemon. Apache and/or PHP-FPM does that for you.