scyber

from an iphone users perspective there is no problem that requires a solution. Since iMessage is installed by the default, and there is no need for another app. And with iOS being pretty dominant in the US, no other app is going to get the traction it needs on iOS to be a successful cross platform communications.

Google could create the greatest messaging app on the planet, but the carriers have more control on Android. They would just not install it on their phones by default. Which means it would not get the traction needed to succeed. Heck most US carriers don't even install one of googles current messaging apps, they install their own customized one.

I think the biggest question is how long do you want to commute? If you are willing to do the 70-90m daily commute then their are plenty of areas on central nj and pa that are commutable to NYC.

and 300k a year will buy you a large homestead in those areas.

If the Server rendered page is not user specific and is generic for all users then it can be cached and served quickly. Then only potentially one user would experience a slowdown and you can serve much faster.

Of course then you get into the fun of cache management and invalidation.

Hindsight is 20/20. It may see predictable now, but this all took place 10 years ago. It was a much different market.

Clients on TVs? Not even the iphone had "apps" when this decision was made. I doubt they had considered TV "apps" at the time (if anything they were thinking of stbs).

175 grams of carbs. Each gram of carbs has 4 calories. 175 grams of carbs = 700 calories.