> Somehow this seems like an American thing or maybe people in other places make less of a spectacle of it?
I think there is more acceptance in certain cultures, for example, to skip lunch because it's a busy day. Having worked globally and in multiple industries, I don't believe it's an American only thing although probably more common there. I see it as more of an industry thing, and each industry seems to have it's own use case for a product like Soylent. i.e. the programmer 'in the zone' and not wanting to stop for dinner or the investment banker running on a few hours of sleep due to an upcoming pitch.
> Always having too little time, always working and being proud to plan every minute of every day
I'm not sure how that was implied, but that does not represent the typical American workforce in my view.
> entrepreneurs in Asia/Aus/EU they seem to be always eating elaborately
I would be surprised to hear these types of individuals don't deal with skipped meals or lack of time based on what's going on in there life/work like their counterparts in other countries do.
Your comment that San Diego, Orange County and LA should not have to pay for infrastructure work in San Francisco presupposes that the Bay Area is contributing less to state taxes then it's receiving. I'm interested to understand stats on geographic collection/distribution of taxes in CA, and how you know the Bay Area is a net beneficiary. I'd venture that the national trend of wealthy cities paying more state/federal taxes then they receive applies within CA.
Also, suggesting that state taxes should not be unevenly distributed among the state misses the point of state taxes. It's fine to argue where the funds should best be used, but not that a county should only get the proportion it contributed. Why not just have local governments be the primary collectors/distributors of taxes then?
BTW, I love southern CA and think you're awesome :)
I've used the iOS SDK for both in beta deployed apps, and prefer Flurry due to their more flexible custom events. With Google, a custom event has four fields (string, string, string, number), limiting how much you can capture for an event. Flurry allows up to ten, with data types of your choosing.