Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119298
MIME-Version: 1.0
Date: Tue, 17 Jan 2023 13:25:28 -0600
Message-ID: <CAFDBR4ZmckzW52tcJSGM=CyGNEXW=gLSY0qW1zW12SW8HKXGag@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000003bf2c005f27aaadd"
Subject: Measuring Proposal Reaction
From: donatj@gmail.com ("Jesse G. Donat")

--0000000000003bf2c005f27aaadd
Content-Type: text/plain; charset="UTF-8"

I'm looking to measure reaction to a proposal.

My proposal is to have the STDOUT and STDERR global constants always
defined rather than just when running via CLI.

The variability of their existence is a common cause of confusion for
younger inexperienced devs, and even something that slips the mind of more
experienced developers.

My team actually internally has a sniff forbidding STDOUT and STDERR due to
their unreliability in favor of fopenening php://stdout / php://stdout

I think removing the environment variability between CLI and Web
outweighs the potential problems of people writing to these in the wrong
contexts, especially given that you can already fopen and fwrite to
standard out and standard error from a web session.

This is only my second RFC I've purprosed so I'm pretty new to the process.
Let me know what you think and what I can do to help

Thanks,

Jesse G. Donat

--0000000000003bf2c005f27aaadd--