On Mi, 2017-07-19 at 21:34 +0200, Mathias Grimm wrote: > Thats a valid point but that can be addressed in some nice ways. > > The documentation can mention it somehow and that doesn't mean > somebody else should use that framework/lib for every project/case. > That would be similar to saying that we prefer Linux over Windows, > just because we use Linux hosting and better would be to instead > build our own operating system, just so that people don't get > inclined to one side or another > A bit of a stretch of an analogy but more or less the same idea. > > The fact that we use some well known framework/package would reduce > the barrier to get more people involved in the project, now and for > the future. Not using them is going back to 2005 when everybody had > their own framework. > > I am not suggesting any framework in specific but think there as some > good options out there. We would be quit well served with a micro- > framework as we basically need just some kind http stack + routing, > but that is deep down the execution plan discussion.
Mind that the php.net site except for the doc search actually is a static web page we could also generate completely as static HTML. This is not a complex system where any "business logic" does complex stuff, thus a framework doesn't help much, while bringing complexity. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
