Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114413
MIME-Version: 1.0
References: <CAGBsUrePAey_fdAq0S_XtcnPhcXsB=tgnff0TUNfPo-AtTEheQ@mail.gmail.com>
 <CAJvSBVOeVrByc-VrEzpH0c0OecT78pCBzoG5b132gtq0wJ5zmA@mail.gmail.com>
In-Reply-To: <CAJvSBVOeVrByc-VrEzpH0c0OecT78pCBzoG5b132gtq0wJ5zmA@mail.gmail.com>
Date: Tue, 11 May 2021 17:58:06 +0100
Message-ID: <CAGBsUrcxoR+9-mH3TFwgAiLfwgnBBV_e8GRgs0DXt6fUdt_q5g@mail.gmail.com>
To: Peter Bowyer <phpmailinglists@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f91df005c210cc76"
Subject: Re: [PHP-DEV] Could we drop the bottom-posting rule?
From: tekiela246@gmail.com (Kamil Tekiela)

--000000000000f91df005c210cc76
Content-Type: text/plain; charset="UTF-8"

> I doubt "bottom posting" is a term people who started online in the last
10
years know - with today/yesterday's example, my takeaway was the original
poster didn't know what it meant.

Yeah, the first time I heard about it is on this mailing list. I didn't
know it was a thing before, and I admit I might still not understand why it
is a thing. All my life I have been used to "newest first". Whenever I
encountered a website or an email that asked me to scroll for the newer
content it upset me. Now I see that some developers prefer this style. It
could also be the fault of user agents that don't scroll/hide the old
content and force me to read it again.

--000000000000f91df005c210cc76--