Redesigning the browser window

Regarding the use of horizontal space: This is what the Reading List feature of Safari 5 is for. (Example for comparison: http://i.imgur.com/x2tkl.png)

Tabs are really only supposed to be used for things you're actually looking at simultaneously; any time you're just middle-clicking everything on a page (e.g. the HN frontpage), in order to queue those pages up for reading after you close the index page, you should be putting them in the reading list instead. It's kind of sad that Apple hasn't made a larger push to get people to notice it; it's a much better solution for the bottom-80% of what people use tabs for today.

Things you might not know about the Reading List:

1. It has quite a bit of accelerator support (you can put any link into the reading list by Shift+Clicking it; you can put the page you're on into the reading list with Command+Shift+D; and Command+Alt+Down is "I'm done reading this; advance to the next thing in the list.")

2. The reading list (as part of your bookmarks menu) gets iCloud-synced. Your open tabs don't. That alone was worth consciously forcing myself to re-learn my "eh, later" behaviour, because now I can just forget what I had "open" and read the rest on my iPad/iPhone/etc. (I suppose this might be why it hasn't been advertised much as a feature; they might be waiting to use it as part of the iCloud release pitch.)

---

On a separate note/rant, regarding the use of "tab groups": it seems like the author simply wants to re-invent the Springboard/Launchpad-style application management paradigm within the browser. Why bother? I don't want to have two different ways of managing my applications, depending on whether they're "web" applications or not. I want my applications in Launchpad, and my running applications in the Dock, with notification badges on them. It shouldn't matter that Gmail requires Webkit-et-al, just like it shouldn't matter that an app requires Java.

Safari, just like Mobile Safari, should simply have an "Add To Home Screen" button and be done with it. Apps that have been added as such should perhaps be able to access extra resources. (Their HTML5 offline-browsing manifests should be automatically downloaded, for one; they should have accelerated WebGL enabled, with shader support, for another; and this would also be an obvious place to adopt something like Google's NaCl.) I'm guessing, though, that we sadly won't see any of this support, because anything that integrates with the OS well-enough as a web-app is something that doesn't have to make a Mac App Store app instead.

This article was not about laptop displays.

it's not about saving 10-20 pixels vertical screen. way more space is needed to make the adressbar readable on bigger screens.

I tried a ~22" screen vertical for a while, primarily for coding, for exactly the same arguments you made. I switched back because I found I was still only using about as much of the screen as I was when it was vertical - I'm much better about looking side to side than I am up and down - and because I'd rather have two or three windows open side-by-side than one on top and one on bottom.

I know nothing about the technical details of font rendering algorithms, but isn't that just an implementation detail? How hard would it be to write a font rendering algorithm that works when each RGB triplet is a vertical line? And having done that how hard would it be to implement a font renderer that switches between the two algorithms depending on screen orientation?