Re: [PHP-DEV] Moving `php-src/docs` forward

[email protected] ("Weilin Du")
Newsgroups php.internals
Message-ID <[email protected]>
Hi Nick,


I don't object to the change, nor in favor of it.


However, since you've posted under the topic "Moving php‑src/docs forward",
I want to send you this email. I want to quote something here:&nbsp;


“the single worst strategic mistake that any software company can make: They
decided to rewrite the code from scratch”


Now, if the goal is to move the document forward, I don't see why we are
rewriting it from rst to md. I don't want to debate about whether rst if better
or md is, I would say that, famous doc hosters like readthedocs are rst users.
If you want to convince other that md&nbsp;is better than rst, in my honest opinion
your proposal is impossible to pass. To some extend, the statement is similar
to those crazy&nbsp;rust folks.


The point isn't rst is better, the point is if there are indeed benefits, is the
benefits&nbsp;worth the effort and time to put in, and worth to risk the break that
potentially exists? Note that you are basically adding new requirements here
to make your md file works.&nbsp;


In other words, if you and reviewers put the same effort into the content itself,
would it be&nbsp;more effective to the topic "Moving php‑src/docs forward" than
rewriting it in different language?


See?


I say I don't object to the change because I don't think I have a say on internal
doc, but I hope you can focus on the content itself instead of this if you want
to make the internal doc better. That is, update missing APIs through
UPGRAING.INTERNALS, building new chapters, writing articles for newcomers,
etc, etc.


That sounds way more better to me, and I am glad to see these contributions
happening


Cheers,
Weilin D.&nbsp;
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.