On Wed, Apr 2, 2014 at 10:29 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:
>
> They will not sit equally. If someone buys a PHP 6 book and finds out that
> half the code in there doesn't actually work on PHP 6, it's going to get a
> 1 star review on Amazon and the issue takes care of itself.
>
Hi everyone,
As part of the writing part of the community, I would much rather have a
PHP 7 than a "revised PHP 6" version. Speak of article maintenance... And
like Eli said, there actually is a PHP6 already: it's a dead branch. Just
flag it on the php.net website, maybe in the downloads section and the docs
with a nice announcement link, and everyone will be happy.
As a reader, I wouldn't expect any PHP 6 material to be outdated (should I
find it by chance, or should I look for it). And why would I automatically
jump on a PHP 6 book to learn PHP 7?
Also, that next version is still to come and authors still have time to
properly write on this next version. These books have time to get famous,
etc. Not to mention online articles.
As for the reviews of existing books, might I suggest you take a look at
some of them? They have had much time to get lots of stars, and I am not
convinced that ratings are negatively affected by age (maybe even the
reverse?).
Now, why is this so much of a deal? As Eli rightly pointed out, that's not
a big deal for the core dev community (you) and for the writers out there.
However, it would avoid much campaigning and confusion, neither of which I
am convinced can solve anything or be solved.
Best regards,
--
Guillaume Rossolini