Bugs could be good thing as well. What the case with the bugs? For the php.net I think it could actually be worthy generating html. But as I said, the idea is to make the code readable again, be it with a framework or not. Having all that html mixed with php + globals is really bad. Even if we wanted to get a designer to help on the website it would be really hard. It can be a very static php and still be more organised. A basic MVC doesn't hurt
On 19 July 2017 at 22:21, Sara Golemon <poll...@php.net> wrote: > On Wed, Jul 19, 2017 at 4:02 PM, Andreas Heigl <andr...@heigl.org> wrote: > > I personally strongly disagree with that approach. Most of the pages on > > php.net are static pages. And those few that aren't can be well > addressed > > with their own script and within that vanillaPHP-script the task can be > > solved. IMO there is no need for routing or an HTTP-Stack. And it shows > that > > we - even in 2017 still know how to build a basic PHP-site. The entry > > barrier is absolutely low as no framework/library knowledge is necessary > and > > the scripts can be easily analysed from start to end. As there are - due > to > > the mirrored setup - no DB-queries or sessions or any other more complex > > stuff going on we should keep it simple and stupid. > > > > But thats - as I said - just my 0.02€ > > > And for my $0.02, I agree with Andreas. Caesar's wife must be beyond > reproach, and quite frankly there is plenty that can be done to > beautify/update the web-php codebase that doesn't involve frameworks. > *cough*globals*cough*. > > In fact, if you want to start with a more constrained problem space, > web-bugs has fewer variables and build steps and is in greater need of > updates (the main site having been revamped much more recently). > > -Sara >
