The only problem with that is the follow-up statement(1) from Google indicating that the re-direct was not something that was recently added and that it has always been in place when that has not been the case.
The fact that they made a couple different statements (first it was that Google Maps only works with Webkit-based browsers, and now the re-direct nonsense) that are not completely truthful makes me doubtful.
To all those that are doing/have done startups on .NET, do you guys mind doing a few blog posts on the subject? What was working with .NET like? What worked for you? What didn't? What's the story when it comes to licensing, hosting, deployment, scalability, etc.?
I know StackOverflow has a few posts on the topic but I wouldn't mind hearing from some of the other startups.
Yes, C# is definitely the way to go. VB is still supported but C# is now the primary language if you are doing .NET development.
What functionality do the current ASP pages provide? Is this for a website or are these custom applications? Either way, I would recommend switching to MVC but depending on the use, your approach will vary.
Lots of forms. like registration and updating user info etc.
Lots of pages that list data using tables. Different logic for changing what gets displayed on the pages. For example, showing something based on a user being logged in or not.
This is unfortunately my main issue with FF. I am type of person that has multiple tabs open in multiple windows for days at a time and FF tends to choke in that scenario after a few days. I was hoping the 64-bit version might fix the issue but it's even worse.
It's still my main browser but this one issue just kills the entire experience.
Given that carriers are only limited to 5 apps and can't make any changes to the Windows Phone OS, I would doubt that there are any Windows Phone devices with Carrier IQ.
I thought carriers were limited to 0 apps and couldn't make changes to iOS. However, that appears to be completely incorrect. Windows Phone may be safe or it may not be. But the argument that carriers couldn't touch WP7 doesn't hold any water given what seems to be happening with iOS.
Did you switch your GV number to AT&T? Or did you use a new number?
I have been considering switching my GV number back to a cell carrier for a while, but I have heard/read that there might be issue doing that. Primarily with SMS/texting receipts, incoming calls from other GV numbers, etc.
While I like the improvements, I am a little disappointed that they are not implementing parallel/multi-threaded copying. It might not be something that a majority of users would need, but it feels like it should be something that should be natively supported by the OS.
What do you mean? It showed two batches being copied in parallel. If anything, they should do less in parallel and rather queue up jobs between same disks.
Yes, you can have multiple copy operating running in parallel but the way Windows works, the files themselves are copied in serial order (within an individual copy operation). Whereas with tools like RichCopy, you are actually copying multiple files in parallel.
I'd be interested in seeing benchmarks that demonstrate an improvement when doing this. I'd expect that the average case is slower due to increased disk contention.
