Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112058
Return-Path: <brendt@stitcher.io>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 10493 invoked from network); 14 Oct 2020 12:19:14 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 14 Oct 2020 12:19:14 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 832761804B7
	for <internals@lists.php.net>; Wed, 14 Oct 2020 04:34:32 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,SPF_HELO_NONE,
	SPF_PASS autolearn=no autolearn_force=no version=3.4.2
X-Spam-Virus: No
X-Envelope-From: <brendt@stitcher.io>
Received: from srv015.mail.ichtushosting.com (srv015.mail.ichtushosting.com [159.69.182.195])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Wed, 14 Oct 2020 04:34:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=stitcher.io
	; s=default; h=Message-Id:In-Reply-To:To:References:Date:Subject:Mime-Version
	:Content-Type:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
	Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc
	:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
	List-Post:List-Owner:List-Archive;
	bh=IuEMw23p6S6+VOimVPJn1axfsY/p2Qmh2aK6E5YaCB8=; b=KVIYjD0ETSFv2uaFCZUSOMsuT9
	HAKeNE3OOFTWBaNarvIIqSO64Vf2aEAD31wWNspeWBn83SPozhQuO/rvEmUogXXgsM5b/INEuKQfG
	XfFP2bnKHi9wy55nCvhHfwp14KV1wDGrJwTaK1lqitA0Bli+/o7zsFThkTk0z98nuSl4PU2lsfVZh
	NA2DFj0uJ55n34qmdov6Neoojf/WDNmnzavYitGbu2DRz325VG+w5KFOyhogvgOqTY2bhZi5r1LH9
	AbX1HevJWSMy30ZefsqeVI5mbZ3X/tIV+nMZsNIg4U1x9u37cqkswwQslLlTEug0F+oRlFQZpDMvJ
	WByGYLvw==;
Received: from srv020.mail.ichtushosting.com ([78.46.213.219])
	by srv015.mail.ichtushosting.com stage1 with esmtp 
	(Exim MailCleaner) 
	id 1kSf36-0002ja-6j 
	for <internals@lists.php.net> 
	from <brendt@stitcher.io>; Wed, 14 Oct 2020 13:34:29 +0200
Received: from ptr-fq9pjpjf861ziupsdv2.18120a2.ip6.access.telenet.be (ptr-fq9pjpjf861ziupsdv2.18120a2.ip6.access.telenet.be [IPv6:2a02:1812:c3c:3a00:dcd0:b35d:e9df:62e])
	(Authenticated sender: brendt@stitcher.io)
	by srv020.mail.ichtushosting.com (Postfix) with ESMTPSA id 794F23EB3D
	for <internals@lists.php.net>; Wed, 14 Oct 2020 13:34:27 +0200 (CEST)
X-MailCleaner-return_path: brendt@stitcher.io
X-MailCleaner-sender_address: brendt@stitcher.io
X-MailCleaner-recipients: internals@lists.php.net
X-MailCleaner-SPF: pass
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C8D86218-EE26-4646-B42B-8EB0FB8FE958"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Wed, 14 Oct 2020 13:34:26 +0200
References: <CADZ9LSXePBHB6A5xEFGvW9MZ7pOpM0Hht10cjSkBXQnQGSP8dQ@mail.gmail.com>
 <CAKuGYLT8tqYpLOghCOUVhhTDx2tx5n6-RutxhK_04_JLZqT9FQ@mail.gmail.com>
 <DM6PR07MB6618064ECBE4089308D897E5F9040@DM6PR07MB6618.namprd07.prod.outlook.com>
 <d753e90c-9f2f-4d66-ae5a-d9e52e80e2d1@www.fastmail.com>
 <e1639ba5-9353-2f9f-f7c5-784f8cc12b88@gmail.com>
To: php internals <internals@lists.php.net>
In-Reply-To: <e1639ba5-9353-2f9f-f7c5-784f8cc12b88@gmail.com>
Message-ID: <8533A48B-C3EE-40C7-A4E6-A9914CBC3A23@stitcher.io>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-MailCleaner-TrustedIPs: Ok
Subject: Re: [PHP-DEV] PHP 8 release announcement page on php.net
From: brendt@stitcher.io (Brent Roose)

--Apple-Mail=_C8D86218-EE26-4646-B42B-8EB0FB8FE958
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi internals

Regarding the matter of a sandbox, one of my colleagues open sourced a =
Laravel sandbox that runs straight in the browser and uses docker =
containers, with a little work you can extract away the Laravel part and =
have it run plain PHP. Here's the source: =
https://github.com/spatie/tinker.app =
<https://github.com/spatie/tinker.app> and here's it running: =
https://tinker.app/ <https://tinker.app/>

On topic now, regarding the promo page: this kind of marketing is where =
PHP lacks a little bit, so I think it's a great initiative. A simple one =
pager just to promote PHP, one you can share with both PHP and non-PHP =
developers, and teases the right amount to get some people interested. A =
perfect page to share on hackernews, reddit, twitter and the likes. I =
think it's a great first step!

Kind regards
Brent

> On 14 Oct 2020, at 13:18, Dik Takken <dik.takken@gmail.com> wrote:
>=20
> On 14-10-2020 03:41, Larry Garfield wrote:
>> This sounds like a fantastic idea.  The inline-run capability of Go =
and Rust's documentation is a huge win.  Writing good sample code for =
the documentation would be an interesting challenge, but it's the sort =
of thing that can be done over time.
>=20
> I second this. However, then we should also make sure that the example
> code actually works, and on which PHP versions. As soon as examples =
can
> be run right from the documentation pages, the examples will be run =
far
> more frequently than they are now, simply because it is so much easier
> to do. Broken examples will cause more disappointing experiences.
>=20
> I don't know if example code is currently tested automatically. If =
not,
> adding a sandbox for running them may also offer an opportunity for
> automatic testing.
>=20
> Besides experimenting with example code, a sandbox may also be used to
> expose runtime information. Think of generated opcodes, the JIT =
compiled
> assembly, the AST.
>=20
> At some point I can imagine adding a documentation page about
> performance, optimization and JIT. That page could enable users to see
> how an example code snippet is compiled, optimized and how type
> inference is done. Change the code, change opcache settings and see =
what
> happens. It is interesting to toy around with and it helps to get more
> exposure to some impressive developments of recent years.
>=20
>> The interesting question would be how to configure it to ensure it =
doesn't become a security issue.  We'd probably need to lock down the =
environment's ini settings *hard* to make sure it can't do any outgoing =
communication at all.
>=20
> Trying to lock things down will also limit the example code that can =
be
> run. And we run the risk of overlooking things. Maybe we could learn
> from other languages, how they set up their sandbox environments.
>=20
>> If we need hosting for that, I work for a hosting company and we're =
happy to help.
>=20
> I think we all highly appreciate that offer.
>=20
> Regards,
> Dik Takken
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>=20


--Apple-Mail=_C8D86218-EE26-4646-B42B-8EB0FB8FE958--