When you work on a code, you usually work on 3/4 spots at the same time. You tweak, then you go to the next part, and you tweak, then you go back to the previous part. Then you click on another tab to check something. You scroll. You then go back, etc.
Having some 'back' and 'forward' arrows like in a browser would really ease this process. Every time you click on some part of a text file, it's like when you enter a URL in the web browser: you change location, and the location get added to the history.
The history should go across tabs of course, as you usually edit several files at the same time.
This is where the web browser analogy dies: URL are not supposed to change while your are browsing, while your code does.
The best I can think of is to save the last line number that lost focus and consider it "good enough". It will be a time saver 99% of the cases since like in every history, the first and the second entry would be the most used. In the other cases, you will arrive far away from the edit and have to scroll as usual. It's not a big deal, you just have to be aware of the limitation.
Yes, Open Komodo is full of useful, well tested, maintained code... The license for it, however, is MPL and GPL, which makes it impossible for Jon to bundle stuff from it into the ST2 official distribution... but we can always have plugins!