sajidnizami

This is exactly what SOAP tried to do. I suggest sticking to HTTP Status codes.

Generally I despise comparisons as they tend to get overboard, however I agree with everything you've said.

I've only been on OSX for about four months but I can attest to one fact. OSX and Macbook hardware is so well integrated I get uptime of more than 30 days easy. Since I got my macbook, I've only restarted it handful of times. My work Macbook hasn't been restarted since it was bought a month ago too btw and I spend about 14 hours on it ever workday.

It is the type of performance I remember getting from Windows server OSes on very optimized hardware.

Anyway, Win7 is pretty rock solid. I never had problems with it and I've been using it since beta phase. Though I have to reboot the laptop after a day or two of working on it.

Imagine this scenario. Peak traffic time in the day and site goes down because of a deployment, an investor sees it and threatens to pull money out. Ad networks that you work with actually see a report where during peak hours their advertisements weren't served, causes of major trouble. I work for one of the biggest sites in my region and take my word for it, uptime is essential and not something left to chance or gods.

Continuous deployments ensure delivery of features and turn around time fast enough for a changing business model of startup and can't be stopped either.

So uptime and continuous deployment model has to happen at the same time.

Deployments should always be automated and revertable. If you think you can run a healthy startup with just about adequate mistakes perhaps you got an easier place to work at :)

TBH if you are a startup and have downtimes, people don't trust you. I know I won't go to a site if it failed on me on the second click because somebody was _adding features_.

Interesting stuff. I've been doing something similar with my sites for over two years now. Its more of an workflow than just a system really.

1. A staging server where the new changes are first tested 2. Production server which gets the updated and verified working code 3. In case of any trouble (which hasn't happened in quite sometime btw) the old solution backup is kept with a date and time and can be reverted just as easily as code is updated from staging server

You can actually use a load balancer to roll over the servers too while deployment and it takes the factor of downtime away to an extent. But this can't be done with a powershell or any shell script and a network admin has to be present at the time of deployment which makes it difficult.

I have had next to none downtime on my servers. Last I remember my sites going down was during a DNS shuffle well over 6 months ago, never because of some developer or sys admin screw up. Yes I do have more than ten deployments on a single site in a day.

What Bing did is very smart! It actually was, but not crediting Google there just makes it look like a cheap shot.

You won't quote someone without citing their name now would you?

Sadly you are right, they won't be able to push a lawsuit. Not enough grounds for it, however Bing should acknowledge what they did and are doing crediting Google.

If Google hadn't caught them, we would all be thinking Bing did it on its own, which really isn't the case.

First article I've read in a while that's taking Microsoft's side in the whole situation. Every paragraph of this screams publicity. I am just wondering here if this is a PR tactic. Here I would be happy to see a balanced review of both companies behavior but this is just one sided bashing.

<quote>Shame on your pretentious, obnoxious, indefensibly egregious double standard in the field of using public information to turn a profit.</quote> <<-- Ironically, Bing is doing the same and unlike content creators who can opt out by putting a robots.txt file Google cannot opt out of this because like it or not toolbar is always sending back information.

Google indexes public content but how it aggregates it and displays it is their deed. The ordering, etc is Google's work not content creators.Copying it is just like copying an IP. I would love to see this go to court and be fought.

Rep whoring? Q&A sites are there to help out not to give you points and stroke your ego.

I think if SO is hindering you into getting a good rep, probably you don't have enough domain knowledge.

PS: I've been there since the beginning and I still got 114 rep. I love the place because it has gotten me solutions at times without even asking.