However, I have multiple roles and tasks, only one of which is development.
I definitely get a lot of insight during the regular day from fellow coworkers, and tend to do more "operational" (not developing) work better when I'm alongside peers than when I'm there alone late. It's also the kind of work where multiple people looking at one thing really helps, since one person might miss something important and another might notice something important.
So I think it depends on the kind of work you're doing and how you like to work. And that is partially why letting employees work when they want, and even choose where they work, can lead to them being more productive in general, at least as long as you can trust them to choose a schedule that makes them productive instead of one that lets them be lazy.
So, sign me up for a 6 hour day and you'll get my full attention all day. I won't "need" to spend time on HN or twitter or whatever to kill time because I'll be fresh enough to work all day.
Also, because i believe there is a hell of a lot more to life than work, we'll work 4 days a week.
A guy can dream, can't he?
After about 7 hours of coding, I feel my code starts slipping off. Also, I code better at night. I know people who can't code for more than 6 hours a day or their work gets shitty.
I usually code 6 to 7 hours a day, and I take my friday afternoon (or part of it) and night off. This sometimes means working just the morning and the first half of the afternoon, and sometimes means working until 4am on the Thursday and then not working at all on Friday.
I think when you have great people on your team, that love their work (Not their jobs. Their work), it gets eaasier. This people will do their best, and that can't be measured in hours. That's why a fixed schedule actually sucks and many, many people don't like it.
But if you add a preparation, commute, lunch-time, etc... you easily end up with only 4-5 hours of "recreation".
Now imagine you have a wife, kids, friends, side projects, maybe want to watch SICP lectures, learn some Haskell...
4-5 hours is simply not enough.
http://en.wikipedia.org/wiki/Eight-hour_day
So after 100-110 years, maybe it's time to come up with even more efficient work day? (But keeping the right direction).
Personally I like to give it as much as a can for a solid, honest, 8 hours and call it a day. This way I can give it my all everyday, and still get the R&R I require.
I don't let other people's working longer hours than me affect me, though, because I know that my total productivity would decrease if I worked longer hours. If that's not the case for other people, or if they like work so much that they want to do more of it, or if they are bored in the evenings/weekends and want to dabble in something, that's great for them.
I think the factor that helps is that I don't have management that will say "yeah, but X worked 60 hours a week and you didn't", but I'm pretty up-front about that anyway, and just stand my ground.
All that having been said, I do find the US work ethic a bit crazy. Working crazy hours isn't good, and the amount of hours worked per week isn't usually proportional to productivity.