Add URI Language Identifier to core?

One of the reasons you wouldn't necessarily build this convention into CI as an option is that many of the companies you reference probably do this at a level above whatever framework they are using for their website. For example, if you go to http://www.apple.com/hk/ipad/compare/, you might be internally routed to a completely different server from the one which serves http://www.apple.com/sg/ipad/compare/

Since there could be differences in product lines and launch dates (in addition to the language differences), each country or region could have different requirements for load balancing at different times, and you may have more servers available near a particular region to serve that region's content.

For a small site, obviously, this wouldn't be the case, so it's nice to be able to handle it within the framework. However, there are a number of different ways to handle this problem, and almost all of them would require some amount of extra configuration for the sites that need it, and would not only be useless overhead for the sites that don't, but may needlessly restrict what they can do.

Bonfire

Practical CodeIgniter 3
CodeIgniter Testing Guide