Fascinating. A corollary would be: be careful what you read and be critical of what you read. There is danger of manipulation, particularly by others. The plus is that you could manipulate yourself, change personal perceptions and mode of thinking.
As an aside, I think TN status is great if you can get it. The only real problem is that you lose it as soon as you step off of US soil and have to re-apply when you try to re-enter. This makes for increasingly stressful trips home to Canada (or Mexico) since the longer you are in the US, the less likely you'll be given a new one when you return. Granting the TN is totally arbitrary and depends on the mood of the border agent and the quality of your paperwork. Make absolutely sure your job title and description is identical to one of the TN-permitted ones. Lawyer-up if necessary. The cost of getting lawyer to prepare you is more than offset by the increased salary available in the US.
I've talked to people who've done it, but you can't leave the country when you start the process. It's better to use an H1/L1/etc. As a Canadian, I wouldn't really suggest US citizenship although.
Which isn't that bad. If your company is keen on having you stick around they can do the TN1->H1B->Greencard juggle in under a year. Otherwise, just sticking with your TN really isn't that different from being on a Greencard. Yes, you have to renew it yearly and the immigration folks can be surly about it, but you pay your $50 fee and you get another year. I did it for 10+ years without issues.
I'm so very sorry to hear this story. It reminds me of another one about Indian engineers looking for brides back home - I heard on NPR a few years back. It was heart breaking to hear that the order of preference for the potential brides was citizen, h1b applying for green card, green card holders. You see, if you are on h1b your spouse can stay with you (but cannot work), and if you get a green card while already married, she gets one too. But, if you already have a green card, you are in worst possible case from family point of view, as explained above. It really, really sucks.
In short: It's the typekit fonts. I had experimental iPad/iPhone support enabled, which works fine with iOS 4 Mobile Safari but likes crashing previous Mobile Safari versions. I just disabled it.
Long version: we have a dedicated mobile version of the site but we never got around to updating that before the launch so we disabled it.. had some other issues too and the content was all outdated. So a mobile friendly version of the site will be built soonish. I just wish jQuery Mobile was here already so I could build it with that. :)
