> If they would only first explain what the heck is "routing in PHP"...

"Routing" is a common and well-understood term in application development: I'm sure you can appreciate the act of writing documentation for an intended audience. In the context of an application, a router interprets a request from a client and forwards it to the appropriate resource (a controller or some other business logic) which then produces a response.

Web application development. I'm sure plenty of programmers would think of the Layer-3 device that chooses paths to forward packets through nodes to a destination.

> Web application development.

I don't know if I'd make that distinction. Routing certainly gets a lot of use in web application development, but routing at the application level is not web-specific: examples of the pattern can be found in the Android SDK,[1] userland Android/iOS development,[2] and in a number of EIPs.[3]

> I'm sure plenty of programmers would think of the Layer-3 device that chooses paths to forward packets through nodes to a destination.

I don't discount this at all, but I do think it's pretty obvious from the context and the README which type of routing this library provides.

[1]: http://developer.android.com/reference/android/media/MediaRo...

[2]: https://usepropeller.com/blog/posts/routable/

[3]: http://www.eaipatterns.com/MessageRoutingIntro.html

> writing documentation for an intended audience

Yes, and web application developers are the intended audience.

A news item a short while ago had the similarly phrased "router in PHP" and for a moment I thought someone had actually used PHP to write a layer-3 networking device.

I agree ... many PHP devs seem to think that programming only exists between when the web server gives a request to a PHP process and when that process closes it's STDOUT handle to complete the response.

Why PHP devs? Aren't "routing" libraries also available in other popular languages with frameworks? Are those devs somehow beyond reproach?