I'm not using these routes. These were just made up examples to challenge the proposed new routes. Now I understand that new routes are not intend to be replacement for the old one, but rather a simplified alternative to handle the most common needs.
However, it looks still quite complicated for me. I never liked the fact that application specific routes are global. I think it would be much more clear if global routes would be used to map to applications only (both based on url paths and domains) and the app-specific local routes would be used to map paths to controllers/functions. I also support pbreit here saying it should be the default, that is web2py on installation should have welcome and example apps with local routes. This separation makes things easier to understand and manage. And answering your questions, I'm deploying my apps on GAE and I'm not using domains. I'm using routes.py to simplify urls so that it is easier to remember them or use in printed materials. For the rest I'm happy with the default /controller/function dispatching.
