An integer history.index < history.length would be a big simplification for many history-based routers. Currently, many of these push/replace a "fake" first state when the app starts up only to record such an index. There might be some privacy/security concerns, but I can't think of any negatives that are not already possible with history.length, history.back(), etc. History state is used often fo