Yup. Keep asking for this one; lack of virtual space is one of my biggest gripes with Sublime. If you've grown up with this freedom in your previous favourite editor(s), it's a bind to live without and a real workflow hindrance in certain situations.
While I'm a big fan of what's happening with ST3 by way of turbocharging extension development possibilities, there's some basic core functionality missing that can't be written as extensions. Virtual space and Definable tabstops are two examples; both can be "kludged" in extensions, but there are all kinds of caveats and gotchas with such approaches. Another example is code folding, which needs to support tmLanguage hints instead of just using indent level, and restrictive macros, which won't record a good deal of things in sublime including S&R. Such things are the "nuts and bolts" of a good editor.
I'm afraid that these kinds of basics are keeping a lot of people away from Sublime. Sublime is "nice for some jobs" at the moment, but not the "go-to tool for all". It's a shame that the author doesn't seem to recognise that, because in reality some of these basics probably require far less work than the overhaul of Sublime's extension system / python bridge, and these simple improvements would win him a lot of new customers.