We don't have a strong pairing culture, but we're trying to create one! It's a little harder to justify the price because we don't know how many people will use it yet. Besides, programmers are often not the ones who are in charge of approving expenses.
In any case, Tuple is really great. For us, I think it would become a no-brainer if it had a seat-based model. e.g., we pay for 4 pairing seats a month, and a max of 4 developer can use Tuple at any given time.
Other complaints aside, I just wanted to say that I quite like the "wall of text" approach. Thinking back to the article on API documentation from Parse (http://blog.parse.com/2012/01/11/designing-great-api-docs/) I'll agree that having everything on one page, quickly accessible, is a good way to do. By breaking up the page with relevant headings and sub-headings the docs can be made much less daunting (as they are here). I'd be much more annoyed with having to click between pages too often.
Not necessarily. Surface roughness that creates the most hydrophobic surfaces is around 0.1-1 microns which is much less than the width of a human hair.
In my experience, it worked the same way as sharing a room in University. Yes, your side of the room certainly has a "you" quality to it, but even with partitions and clever arrangements of closets and shelves, it's not the same.
When you have your own space, you're completely free to roam. You no longer need consent/approval from anyone else and you're free to customize things as much as you want. When you share a space with someone, you always partially depend on them in some capacity. When you're only sharing with people in your own company it's much easier to deal.
Also, in a co-working space, you could be sharing the conference call set-ups, the conference rooms, you have to arrange splitting the electricity/water bills, etc. All in all, it just results in more headaches.
I wasn't aware of the photo-catalyst properties of bulk TiO2, so I'll have to agree with you there, but I'll say two things in defence of the article. Firstly, it does mention that a key factor in the effectiveness of TiO2 as a catalyst is the exposed surface area, so nano-sized TiO2 may be necessary to get the efficiency to make this viable. Perhaps bulk TiO2 just isn't enough. Secondly, nano-sized TiO2 responds to light differently (for example, I just did a lab experiment where TiO2 particles in nano behaved very differently under XRD from bulk TiO2). There might be other benefits that nano TiO2 offers that weren't mentioned in the article.
In any case, Tuple is really great. For us, I think it would become a no-brainer if it had a seat-based model. e.g., we pay for 4 pairing seats a month, and a max of 4 developer can use Tuple at any given time.