Douglas Wilson

Getting rid of these `app.*` stuff in 5.x will let us get rid of `req.next` as well (horray!)

> Tbh I can't even find app.render in the codebase.. https://github.com/strongloop/express/blob/master/lib/application.js#L477

The problem is we cannot easily deprecate this, because `res.render` calls this and there is no real good way to make `res.render` not yell and yet make `app.render` yell while...

Also, I didn't say there was _no way_, because it's possible using some `Object.defineProperty` tricks, but it's just not really worth the complexity to just show a deprecation.

@ilanbiala what apps use req.next() ? They should be calling the next() function passed as the argument to the middleware.

Hi @ilanbiala you can look at #2237 to see what has been checked off. The answer for this is no, especially since there is not hard date for 5.0 yet.

There is nothing in express that is adding something called `_locals` that I am aware of. Can you provide a reproducible example of the issue you are having? Does it...

It may seem different from the outside, but in fact is very different in the internal structure it creates. We can look into the consequences of changing this as part...

Actually it changes the outside behavior as well; right now app.all only responds to known verbs. This change will make it also respond to unknown verbs.

Right, you are not wrong. But app.all doesn't, so it would be a change of behavior for app.all