"Split views: Yes, I actually had this on the alpha milestone, I’m not overly excited about this feature myself, but I know it’s a very common request, so eventually it should find its way into the application."
When I want to view two files at the same time, I open two windows, and put them side by side.
Not everything needs to be fullscreen all-the-time. Let the OS manage windows. It's better at it!
Besides, having windows automatically become half-maximized is easy with the right tools, like BetterTouchTool (Do it with a gesture!), or Divvy.
I use and love the 3rd party tool SizeUp, but SublimeText2's integrated pane management (including moving tabs between them) is far better than plain windows.
Want to view two files? Ctrl-right on one, it's now on the right side of the screen.
Command-O, chose the new file, Ctrl-left on it, it's now on the left side.
I'm honestly very curious what Sublime/etc offer that is better than what you can do with the OS?
Do other windows start inheriting the project drawer if older windows are closed?
Each window has multiple tabs - how do you tear off and replant them using the keyboard?
Doh, now the temporary horizontal split panes like find-in-project, the python console, etc, must be attached to a specific narrow window.
And so on. I like a multi window desktop and am certainly not a maximise-everything guy. But relying on the OS for everything is not optimal.
Because there are so many benefits of having multiple buffers/files open within the same Vim instance it makes sense to have multiple buffers viewable at once, not to have only one viewable at a time. You lose a lot of editing power if buffers are not open in same Vim instance; it doesn't make sense to open a new file separately in different Vim instance. Moreover, many times split windows are useful to show two different views of the _same_ buffer at once.
Granted, I only know that from using VIM (and occasionally SublimeText), but it's been one of my "Dear GOD Give Me This in TM" requests for a while. I've got SizeUp and love it - truly one of my must-have apps - but to me it's a hack, not a solution.
I also happen to work on a project with 24k+ files, which even with an SSD TextMate does not do well with. I have a script to generate a tmproj file[1] that contains the files I want to make it manageable.
(or whatever your editor of choice calls its synchronized side-by-side diff mode)
New windows should be a part of the same project they were opened from.
In terms of split views, its not a big issue for me, but to publicly state that is your approach has me unsure about other parts of TM2 and his practices. I don't look at it thinking "yay!"
There's the obvious observer problem where you have two views of the same buffer and changing the text in one automatically updates the other. Isn't that harder to tack on later than to design into the app from the beginning?
The built-in notifications and delegate-relationships handle everything else (updates & synchronization) automatically. This is actually NeXTSTEP-level stuff that's been around for decades.
i don't understand this. how does he code only looking at one file at a time?
I've been programming for nearly thirty years now. For the bulk of that time, I had an editor which allowed me to do split screens, and I used it maybe once a year. I switched to TextMate in 2008, and have never once missed having a split screen.