Thursday, December 15, 2011

Dravid's powerful speech in Oz gets standing ovation

Thank you for inviting me to deliver the Bradman Oration; the respect and the regard that came with the invitation to speak tonight, is deeply appreciated. (WatchDravid's speech at Bradman Oration)

I realise a very distinguished list of gentlemen have preceded me in the ten years that the Bradman Oration has been held. I know that this Oration is held every year to appreciate the life and career of Sir Don Bradman, a great Australian and a great cricketer. I understand that I am supposed to speak about cricket and issues in the game - and I will.(Also see: The importance of being Rahul Dravid)

Yet, but first before all else, I must say that I find myself humbled by the venue we find ourselves in. Even though there is neither a pitch in sight, nor stumps or bat and balls, as a cricketer, I feel I stand on very sacred ground tonight. When I was told that I would be speaking at the National War Memorial, I thought of how often and how meaninglessly, the words 'war', 'battle', 'fight' are used to describe cricket matches.

Yes, we cricketers devote the better part of our adult lives to being prepared to perform for our countries, to persist and compete as intensely as we can - and more. This building, however, recognises the men and women who lived out the words - war, battle, fight - for real and then gave it all up for their country, their lives left incomplete, futures extinguished.

The people of both our countries are often told that cricket is the one thing that brings Indians and Australians together. That cricket is our single common denominator.

India's first Test series as a free country was played against Australia in November 1947, three months after our independence. Yet the histories of our countries are linked together far more deeply than we think and further back in time than 1947.

We share something else other than cricket. Before they played the first Test match against each other, Indians and Australians fought wars together, on the same side. In Gallipoli, where, along with the thousands of Australians, over 1300 Indians also lost their lives. In World War II, there were Indian and Australian soldiers in El Alamein, North Africa, in the Syria-Lebanon campaign, in Burma, in the battle for Singapore.

Before we were competitors, Indians and Australians were comrades. So it is only appropriate that we are here this evening at the Australian War Memorial, where along with celebrating cricket and cricketers, we remember the unknown soldiers of both nations.

It is however, incongruous, that I, an Indian, happen to be the first cricketer from outside Australia, invited to deliver the the Bradman Oration. I don't say that only because Sir Don once scored a hundred before lunch at Lord's and my 100 at Lord's this year took almost an entire day.

But more seriously, Sir Don played just five Tests against India; that was in the first India-Australia series in 1947-48, which was to be his last season at home. He didn't even play in India, and remains the most venerated cricketer in India not to have played there.

We know that he set foot in India though, in May 1953, when on his way to England to report on the Ashes for an English newspaper, his plane stopped in Calcutta airport. There were said to be close to a 1000 people waiting to greet him; as you know, he was a very private person and so got into an army jeep and rushed into a barricaded building, annoyed with the airline for having 'breached confidentiality.' That was all Indians of the time saw of Bradman who remains a mythical figure.

For one generation of fans in my country, those who grew up in the 1930s, when India was still under British rule, Bradman represented a cricketing excellence that belonged to somewhere outside England. To a country taking its first steps in Test cricket, that meant something. His success against England at that time was thought of as our personal success. He was striking one for all of us ruled by the common enemy. Or as your country has so poetically called them, the Poms.

There are two stories that I thought I should bring to your notice. On June 28, 1930, the day Bradman scored 254 at Lord's against England, was also the day Jawaharlal Nehru was arrested by the police. Nehru was, at the time, one of the most prominent leaders of the Indian independence movement and later, independent India's first Prime Minister. The coincidence of the two events, was noted by a young boy KN Prabhu, who was both nationalist, cricket fan and later became independent India's foremost cricket writer. In the 30s, as Nehru went in and out of jail, Bradman went after the England bowling and, for KN Prabhu, became a kind of avenging angel.

There's another story I've heard about the day in 1933, when the news reached India that Bradman's record for the highest Test score of 334 had been broken by Wally Hammond. As much as we love our records, they say some Indian fans at the time were not exactly happy. Now, there's a tale that a few even wanted to wear black bands to mourn the fact that this precious record that belonged to Australia - and by extension, us - had gone back. To an Englishman. We will never know if this is true, if black bands were ever worn, but as journalists sometimes tell me, why let facts get in the way of a good story.

My own link with Bradman was much like that of most other Indians - through history books, some old video footage and his wise words. About leaving the game better than you found it. About playing it positively, as Bradman, then a selector, told Richie Benaud before the 1960-61 West Indies tour of Australia. Of sending a right message out from cricket to its public. Of players being temporary trustees of a great game.

While there may be very little similarity in our records or our strike-rates or our fielding - and I can say this only today in front of all of you - I am actually pleased that I share something very important with Sir Don.

He was, primarily, like me, a No.3 batsman. It is a tough, tough job.

We're the ones who make life easier for the kings of batting, the middle order that follows us. Bradman did that with a bit more success and style than I did. He dominated bowling attacks and put bums on seats, if i bat for any length of time I am more likely to bore people to sleep. Still, it is nice to have batted for a long time in a position, whose benchmark is, in fact, the benchmark for batsmanship itself.

Before he retired from public life in his 80s, I do know that Bradman watched Sunil Gavaskar's generation play a series in Australia. I remember the excitement that went through Indian cricket when we heard the news that Bradman had seen Sachin Tendulkar bat on TV and thought he batted like him. It was more than mere approval, it was as if the great Don had finally, passed on his torch. Not to an Aussie or an Englishman or a West Indian. But to one of our own.

One of the things, Bradman said has stayed in my mind. That the finest of athletes had, along with skill, a few more essential qualities: to conduct their life with dignity, with integrity, with courage and modesty. All this he believed, were totally compatible with pride, ambition, determination and competitiveness. Maybe those words should be put up in cricket dressing rooms all over the world.

As all of you know, Don Bradman passed away on February 25, 2001, two days before the India v Australia series was to begin in Mumbai.

Whenever an important figure in cricket leaves us, cricket's global community pauses in the midst of contests and debates, to remember what he represented of us, what he stood for, and Bradman was the pinnacle. The standard against which all Test batsmen must take guard.

The series that followed two days after Bradman's death later went on to become what many believe was one of the greatest in cricket. It is a series, I'd like to believe, he would have enjoyed following.

A fierce contest between bat and ball went down to the final session of the final day of the final Test. Between an Australian team who had risen to their most imposing powers and a young Indian team determined to rewrite some chapters of its own history.

The 2001 series contained high-quality cricket from both sides and had a deep impact on the careers of those who played a part in it. The Australians were near unbeatable in the first half of the new decade, both home and away. As others floundered against them, India became the only team that competed with them on even terms.

India kept answering questions put to them by the Australians and asking a few themselves. The quality demanded of those contests, sometimes acrimonious, sometimes uplifting, made us, the Indian team, grow and rise. As individuals, we were asked to play to the absolute outer limits of our capabilities and we often extended them.

Now, whenever India and Australia meet, there is expectation and anticipation - and as we get into the next two months of the Border-Gavaskar Trophy, players on both sides will want to deliver their best.

When we toured in 2007-08, I thought it was going to be my last tour of Australia. The Australians thought it was going to be the last time they would be seeing Sachin Tendulkar on their shores. He received warm standing ovations from wonderful crowds all around the country.

Well, like a few, creaking Terminators, we're back. Older, wiser and I hope improved.

The Australian public will want to stand up to send Sachin off all over again this time. But I must warn you, given how he's been playing these days, there are no guarantees about final goodbyes.

In all seriousness, though, the cricket world is going to stop and watch Australia and India. It is Australia's first chance to defend their supremacy at home following defeat in the 2010 Ashes and a drawn series against New Zealand. It is India's opportunity to prove that the defeat to England in the summer was an aberration that we will bounce back from.

If both teams look back to their last 2007-08 series in Australia, they will know that they should have done things a little differently in the Sydney Test. But I think both sides have moved on from there; we've played each other twice in India already and relations between the two teams are much better than they have been as far as I can remember.

Thanks to the IPL, Indians and Australians have even shared dressing rooms. Shane Watson's involvement in Rajasthan, Mike Hussey's role with Chennai to mention a few, are greatly appreciated back home. And even Shane Warne likes India now. I really enjoyed playing alongside him at Rajasthan last season and can confidently report to you that he is not eating imported baked beans any more.

In fact, looking at him, it seems, he is not eating anything.

It is often said that cricketers are ambassadors for their country; when there's a match to be won, sometimes we think that is an unreasonable demand. After all, what would career diplomats do if the result of a Test series depended on them, say, walking? But, as ties between India and Australia have strengthened and our contests have become more frequent, we realise that as Indian players, we stand for a vast, varied, often unfathomable and endlessly fascinating country.

At the moment, to much of the outside world, Indian cricket represents only two things - money and power. Yes, that aspect of Indian cricket is a part of the whole, but it is not the complete picture. As a player, as a proud and privileged member of the Indian cricket team, I want to say that, this one-dimensional, often cliched image relentlessly repeated is not what Indian cricket is really all about.

I cannot take all of you into the towns and villages our players come from, and introduce you to their families, teachers, coaches, mentors and team-mates who made them international cricketers. I cannot take all of you here to India to show you the belief, struggle, effort and sacrifice from hundreds of people that runs through our game.

As I stand here today, it is important for me to bring Indian cricket and its own remarkable story to you. I believe it is very necessary that cricketing nations try to find out about each other, try to understand each other and the different role cricket plays in different countries, because ours is, eventually, a very small world.

In India, cricket is a buzzing, humming, living entity going through a most remarkable time, like no other in our cricketing history. In this last decade, the Indian team represents more than ever before, the country we come from - of people from vastly different cultures, who speak different languages, follow different religions, belong to all classes of society. I went around our dressing room to work out how many languages could be spoken in there and the number I have arrived at is: 15, including Shona and Afrikaans.

Most foreign captains, I think, would baulk at the idea. But, when I led India, I enjoyed it, I marvelled at the range of difference and the ability of people from so many different backgrounds to share a dressing room, to accept, accommodate and respect that difference. In a world growing more insular, that is a precious quality to acquire, because it stays for life and helps you understand people better, understand the significance of the other.

Let me tell you one of my favourite stories from my Under-19 days, when the India Under-19 team played a match against the New Zealand junior team. We had two bowlers in the team, one from the north Indian state of Uttar Pradesh - he spoke only Hindi, which is usually a link language for players from all over India, ahead even of English. It should have been all right, except the other bowler came from Kerala, in the deep south, and he spoke only the state's regional language, Malayalam. Now even that should have been okay as they were both bowlers and could bowl simultaneous spells.

Yet in one game, they happened to come together at the crease. In the dressing room, we were in splits, wondering how they were going to manage the business of a partnership, calling for runs or sharing the strike. Neither man could understand a word of what the other was saying and they were batting together. This could only happen in Indian cricket. Except that these two guys came up with a 100-run partnership. Their common language was cricket and that worked out just fine.

The everyday richness of Indian cricket lies right there, not in the news you hear about million-dollar deals and television rights. When I look back over the 25 years I've spent in cricket, I realise two things. First, rather alarmingly, that I am the oldest man in the game, older to even Sachin by three months. More importantly, I realise that Indian cricket actually reflects our country's own growth story during this time. Cricket is so much a part of our national fabric that as India - its economy, society and popular culture - transformed itself, so did our most-loved sport.

As players we are appreciative beneficiaries of the financial strength of Indian cricket, but we are more than just mascots of that economic power. The caricature often made of Indian cricket and its cricketers in the rest of the world is that we are pampered superstars. Overpaid, underworked, treated like a cross between royalty and rock stars.

Yes, the Indian team has an enormous, emotional following and we do need security when we get around the country as a group. It is also why we make it a point to always try and conduct ourselves with composure and dignity. On tour, I must point out, we don't attack fans or do drugs or get into drunken theatrics. And at home, despite what some of you may have heard, we don't live in mansions with swimming pools.

The news about the money may well overpower all else, but along with it, our cricket is full of stories the outside world does not see. Television rights generated around Indian cricket, are much talked about. Let me tell you what the television - around those much sought-after rights - has done to our game.

A sport that was largely played and patronised by princes and businessmen in traditional urban centres, cities like Bombay, Bangalore, Chennai, Baroda, Hyderabad, Delhi - has begun to pull in cricketers from everywhere.

As the earnings from Indian cricket have grown in the past 2 decades, mainly through television, the BCCI has spread revenues to various pockets in the country and improved where we play. The field is now spread wider than it ever has been, the ground covered by Indian cricket, has shifted.

Twenty seven teams compete in our national championship, the Ranji Trophy. Last season Rajasthan, a state best known for its palaces, fortresses and tourism won the Ranji Trophy title for the first time in its history. The national one-day championship also had a first-time winner in the newly formed state of Jharkand, where our captain MS Dhoni comes from.

The growth and scale of cricket on our television was the engine of this population shift. Like Bradman was the boy from Bowral, a stream of Indian cricketers now come from what you could call India's outback.

Zaheer Khan belongs to the Maharashtra heartland, from a town that didn't have even one proper turf wicket. He could have been an instrumentation engineer but was drawn to cricket through TV and modelled his bowling by practising in front of the mirror on his cupboard at home, and first bowled with a proper cricket ball at the age of 17.

One day out of nowhere, a boy from a village in Gujarat turned up as India's fastest bowler. After Munaf Patel made his debut for India, the road from the nearest railway station to his village had to be improved because journalists and TV crews from the cities kept landing up there.

We are delighted that Umesh Yadav didn't become a policeman like he was planning and turned to cricket instead. He is the first cricketer from the central Indian first-class team of Vidarbha to play Test cricket.

Virender Sehwag, it shouldn't surprise you, belongs to the wild west just outside Delhi. He had to be enrolled in a college which had a good cricket programme and travelled 84kms every day by bus to get to practice and matches.

Every player in this room wearing an India blazer has a story like this. Here, ladies and gentlemen, is the heart and soul of Indian cricket.

Playing for India completely changes our lives. The game has given us a chance to pay back our debt to all those who gave their time, energy and resources for us to be better cricketers: we can build new homes for our parents, get our siblings married off in style, give our families very comfortable lives.

The Indian cricket team is in fact, India itself, in microcosm. A sport that was played first by princes, then their subordinates, then the urban elite, is now a sport played by all of India. Cricket, as my two under-19 team-mates proved, is India's most widely-spoken language. Even Indian cinema has its regional favourites; a movie star in the south may not be popular in the north. But a cricketer? Loved everywhere.

It is also a very tough environment to grow up in - criticism can be severe, responses to victory and defeat extreme. There are invasions of privacy and stones have been thrown at our homes after some defeats.

It takes time getting used to, extreme reactions can fill us with anger. But every cricketer realises at some stage of his career, that the Indian cricket fan is best understood by remembering the sentiment of the majority, not the actions of a minority.

One of the things that has always lifted me as a player is looking out of the team bus when we travelled somewhere in India. When people see the Indian bus going by, see some of us sitting with our curtains drawn back, it always amazes me how much they light up. There is an instantaneous smile, directed not just at the player they see - but at the game we play that, for whatever reason, means something to people's lives. Win or lose, the man on the street will smile and give you a wave.

After India won the World Cup this year, our players were not congratulated as much as they were thanked by people they ran into. "You have given us everything," they were told, "all of us have won." Cricket in India now stands not just for sport, but possibility, hope, opportunities.

On our way to the Indian team, we know of so many of our team-mates, some of whom may have been equally or more talented than those sitting here, who missed out. When I started out, for a young Indian, cricket was the ultimate gamble - all or nothing, no safety nets. No second chances for those without an education or a college degree or second careers. Indian cricket's wealth now means a wider pool of well paid cricketers even at first-class level.

For those of us who make it to the Indian team, cricket is not merely our livelihood, it is a gift we have been given. Without the game, we would just be average people leading average lives. As Indian cricketers, our sport has given us the chance do something worthwhile with our lives. How many people could say that?

This is the time Indian cricket should be flowering; we are the world champions in the short game, and over the space of the next 12 months should be involved in a tight contest with Australia, South Africa and England to determine which one of us is the world's strongest Test team.

Yet I believe this is also a time for introspection within our game, not only in india, but all over the world. We have been given some alerts and responding to them quickly is the smart thing to do.

I was surprised a few months ago to see the lack of crowds in an ODI series featuring India. By that I don't mean the lack of full houses, I think it was the sight of empty stands I found somewhat alarming.

India played its first one-day international at home in November 1981, when I was nine. Between then and now India have played 227 ODIs at home; the October five-match series against England was the first time that the grounds have not been full for an ODI featuring the Indian team.

In the summer of 1998, I played in a one-dayer against Kenya in Kolkata and the Eden Gardens was full. Our next game was held in the 48-degree heat of Gwalior and the stands were heaving.

The October series against England was the first one at home after India's World Cup win. It was called the 'revenge' series meant to wipe away the memory of a forgettable tour of England. India kept winning every game, and yet the stands did not fill up. Five days after a 5-0 victory 95,000 turned up to watch the India's first Formula One race.

A few weeks later I played in a Test match against West Indies in Calcutta, in front of what was the lowest turn out in Eden Gardens' history. Yes we still wanted to win and our intensity did not dip. But at the end of the day, we are performers, entertainers and we love an audience. The audience amplifies everything you are doing, the bigger the crowd the bigger the occasion, its magnitude, its emotion. When I think about the Eden Gardens crowds this year, I wonder what the famous Calcutta Test of 2001 would have felt like with 50,000 people less watching us.

Australia and South Africa played an exciting and thrilling Test series recently and two great Test matches produced some fantastic performances from players of both teams, but were sadly played in front of sparse crowds.

It is not the numbers that Test players need, it is the atmosphere of a Test that every player wants to revel in and draw energy from. My first reaction to the lack of crowds for cricket was that there had been a lot of cricket and so perhaps, a certain amount of spectator-fatigue. That is too simplistic a view; it's the easy thing to say but might not be the only thing.

The India v England ODI series had no context, because the two countries had played each other in four Tests and five ODIs just a few weeks before. When India and West Indies played ODIs a month after that the grounds were full, but this time the matches were played in smaller venues that didn't host too much international cricket. Maybe our clues are all there and we must remain vigilant.

Unlike Australia or England, Indian cricket has never had to compete with other sports for a share of revenues, mind space or crowd attendance at international matches. The lack of crowds may not directly impact on revenues or how important the sport is to Indians, but we do need to accept that there has definitely been a change in temperature over, I think, the last two years.

Whatever the reasons are - maybe it is too much cricket or too little by way of comfort for spectators - the fan has sent us a message and we must listen. This is not mere sentimentality. Empty stands do not make for good television. Bad television can lead to a fall in ratings, the fall in ratings will be felt by media planners and advertisers looking elsewhere.

If that happens, it is hard to see television rights around cricket being as sought after as they have always been in the last 15 years. And where does that leave everyone? I'm not trying to be an economist or doomsday prophet - this is just how I see it.

Let us not be so satisfied with the present, with deals and finances in hand that we get blindsided. Everything that has given cricket its power and influence in the world of sports has started from that fan in the stadium. They deserve our respect and let us not take them for granted. Disrespecting fans is disrespecting the game. The fans have stood by our game through everything. When we play, we need to think of them. As players, the balance between competitiveness and fairness can be tough but it must be found.

If we stand up for the game's basic decencies, it will be far easier to tackle its bigger dangers - whether it is finding short cuts to easy money or being lured by the scourge of spot-fixing and contemplating any involvement with the betting industry.

Cricket's financial success means it will face threats from outside the game and keep facing them. The last two decades have proved this over and over again. The internet and modern technology may just end up being a step ahead of every anti-corruption regulation in place in the game. As players, the one way we can stay ahead for the game, is if we are willing to be monitored and regulated closely.

Even if it means giving up a little bit of freedom of movement and privacy. If it means undergoing dope tests, let us never say no. If it means undergoing lie-detector tests, let us understand the technology, what purpose it serves and accept it. Now lie-detectors are by no means perfect but they could actually help the innocent clear their names. Similarly, we should not object to having our finances scrutinised if that is what is required.

When the first anti-corruption measures were put into place, we did moan a little bit about being accredited and depositing our cell phones with the manager. But now we must treat it like we do airport security because we know it is for our own good and our own security.

Players should be ready to give up a little personal space and personal comfort for this game, which has given us so much. If you have nothing to hide, you have nothing to fear.

Other sports have borrowed from cricket's anti-corruption measures to set up their own ethical governance programmes and we must take pride in belonging to a sport that is professional and progressive.

One of the biggest challenges that the game must respond to today, I believe, is charting out a clear road map for the three formats. We now realise that the sport's three formats cannot be played in equal numbers - that will only throw scheduling and the true development of players completely off gear.

There is a place for all three formats, though, we are the only sport I can think of which has three versions. Cricket must treasure this originality. These three versions require different skills, skills that have evolved, grown, changed over the last four decades, one impacting on the other.

Test cricket is the gold standard, it is the form the players want to play. The 50-over game is the one that has kept cricket's revenues alive for more than three decades now. Twenty20 has come upon us and it is the format people, the fans want to see.

Cricket must find a middle path, it must scale down this mad merry-go-round that teams and players find themselves in: heading off for two-Test tours and seven-match ODI series with a few Twenty20s thrown in.

Test cricket deserves to be protected, it is what the world's best know they will be judged by. Where I come from, nation versus nation is what got people interested in cricket in the first place. When I hear the news that a country is playing without some of its best players, I always wonder, what do their fans think?

People may not be able to turn up to watch Test cricket but everyone follows the scores. We may not fill 65,000 capacity stadiums for Test matches, but we must actively fight to get as many as we can in, to create a Test match environment that the players and the fans feed off. Anything but the sight of Tests played on empty grounds. For that, we have got to play Test cricket that people can watch.

I don't think day-night Tests or a Test championship should be dismissed.

In March of last year I played a day-night first-class game in Abu Dhabi for the MCC and my experience from that was that day-night Tests is an idea seriously worth exploring. There may be some challenges in places where there is dew but the visibility and durability of the pink cricket ball was not an issue.

Similarly, a Test championship, with every team and player driving themselves to be winners of a sought after title, seems like it would have a context to every game.

Keeping Tests alive may mean different innovations in different countries - maybe taking it to smaller cities, playing it in grounds with smaller capacities like New Zealand has thought of doing, maybe reviving some old venues in the West Indies, like the old Recreation Ground in Antigua.

When I was around seven years old, I remember my father taking a Friday off so that we could watch three days of Test cricket together. On occasions he couldn't, I would accompany one of his friends, just to soak in a day of Test cricket and watch the drama slowly unfold.

What we have to do is find a way to ensure that Test matches fit into 21st century life, through timing, environments and the venues they are held in. I am still convinced it can be done, even in our fast-moving world with a short attention span. We will often get told that Test matches don't make financial sense, but no one ever fell in love with Test cricket because they wanted to be a businessman. Not everything of value comes at a price.

There is a proposal doing the rounds about scrapping the 50-over game completely. I am not sure I agree with that - I certainly know that the 50-over game helped us innovate strokes in our batting which we were then able to take into Test matches. We all know that the 50-over game has been responsible for improving fielding standards all over the world.

The future may well lie in playing one-day internationals centered around ICC events, like the Champions Trophy and the World Cups. This would ensure that all 50-over matches would build up for those tournaments.

That will cut back the number of one-day internationals played every year but at least those matches will have context. Since about I think 1985, people have been saying that there is too much meaningless one-day cricket. Maybe it's finally time to do something about it.

The Twenty20 game as we know has as many critics as it has supporters in the public. Given that an acceptable strike rate in T20 these days is about 120, I should probably complain about it the most. The crowd and revenue numbers, though, tell us that if we don't handle Twenty20 correctly, we may well have more and more private players stepping in to offer not just slices of pie, but maybe even bigger pies themselves.

So I'll re-iterate what I've just said very quickly because balancing three formats is important:

We have Test cricket like we have always had, nation versus nation, but carefully scheduled to attract crowds and planned fairly so that every Test playing country gets its fair share of Tests. And playing for a championship or a cup, not just a ranking.

The 50-overs format focused around fewer, significant multi-nation ICC events like the Champions Trophy and the World Cup. In the four-year cycle between World Cups, plan the ODI calendar and devise rankings around these few important events. Anything makes more sense than seven-match ODI series.

The best role for Twenty20 is as a domestic competition through official leagues, which will make it financially attractive for cricketers. That could also keep cricket viable in countries where it fights for space and attention.

Because the game is bigger than us all, we must think way ahead of how it stands today. Where do we want it to be in the year 2020? Or say in 2027, when it will be 150 years since the first Test match was played. If you think about it, cricket has been with us longer than the modern motor car, it existed before modern air travel took off.

As much as cricket's revenues are important to its growth, its traditions and its vibrancy are a necessary part of its progress in the future. We shouldn't let either go because we played too much of one format and too little of the other.

Professionalism has given cricketers of my generation privileged lives and we know it, even though you may often hear us whining about burn-out, travel and the lack of recovery time.

Whenever we begin to get into that mindset, it's good to remember a piece of Sachin's conversation with Bradman. Sachin told us that he had asked Sir Don how he had mentally prepared for big games, what his routines were. Sir Don said, that well, before a game he would go to work and after the game go back to work. Whenever a cricketer feels a whinge coming on, that would be good to remember.

Before I conclude, I also want to talk briefly about an experience I have often had over the course of my career. It is not to do with individuals or incidents, but one I believe is important to share. I have sometimes found myself in the middle of a big game, standing at slip or even at the non-strikers end and suddenly realised that everything else has vanished. At that moment, all that exists is the contest and the very real sense of the joy that comes from playing the game.

It is an almost meditative experience, where you reconnect with the game just like you did years ago, when you first began, when you hit your first boundary, took the first catch, scored your first century, or were involved in a big victory. It lasts for a very fleeting passage of time, but it is a very precious instant and every cricketer should hang on to it.

I know it is utterly fanciful to expect professional cricketers to play the game like amateurs; but the trick, I believe, is taking the spirit of the amateur - of discovery, of learning, of pure joy, of playing by the rules - into our profession. Taking it to practice or play, even when there's an epidemic of white-line fever breaking out all over the field.

In every cricketer there lies a competitor who hates losing, and yes, winning matters. But it is not the only thing that matters when you play cricket. How it is played is as important for every member of every team because every game we play leaves a footprint in cricket's history. We must never forget that.

What we do as professionals is easily carried over into the amateur game, in every way - batting, bowling, fielding, appealing, celebration, dissent, argument. In the players of 2027, we will see a reflection of this time and of ourselves and it had better not annoy or anguish us 50-year-olds.

As the game's custodians, it is important we are not tempted by the short-term gains of the backward step. We can be remembered for being the generation that could take the giant stride.

Thank you for the invitation to address all of you tonight, and your attention.

Thursday, September 22, 2011

The 47 Types of Hangover


1. The Upper Peninsula
Night of: Attempting to finish a keg that needs to be returned. Throughout the session, one of your huskier friends will insist on performing the “lift test” every few minutes, and will repeatedly tell you you’re “getting close.”
Symptoms: Renal failure.
Cure: A single slice of cold pizza.
2. The Spray Tan
Night of: Beer and tiki drinks after many hours of direct sun.
Symptoms: Mild nausea, dehydration, melanoma.
Cure: A smoothie of fruit, aloe vera, and raw egg.
3. The Secret Shopper
Night of: Consumption of products bought after alcohol sales cease for the night (cooking wine, vanilla extract, etc.)
Symptoms: Memory loss, nausea, rosemary poisoning.
Cure: Pancakes and pork chops.
4. The Colonel Sanders
Night of: Various “classy” Southern drinks (mint juleps, Southern Comfort, etc.).
Symptoms: headache lasting two or more days, duel commitments.
Cure: Sweating into a linen suit for an entire afternoon.
5. The General Lee
Night of: Moonshine.
Symptoms: Blindness, hollerin’.
Cure: Mama Jessup’s Pine Creek Possum Stew (Stu’s Backwoods BBQ, page 57).
6. The Missouri Compromise
Night of: Beer and fortified wine.
Symptoms: Headache, mullet.
Cure: One full-strength dose of Don’t Give a Damn.
7. The Dean Martin
Night of: 15-30 martinis with limited food.
Symptoms: Laryngitis, “Escort Rash”.
Cure: 15-30 Bloody Marys with limited food.
8. The Stooge
Night of: Hard alcohol near broken glass or other sharp objects.
Symptoms: Blood loss, influence on later bands.
Cure: Cipro.
9. The Lion in Winter
Night of: Ale in tandem with “pub food” (pies not involving fruit, potatoes in inconvenient shapes, etc).
Symptoms: Semi-permanent weight gain of 10-15% of previous body mass.
Cure: Military service in India or Rhodesia.
10. The Hogarth
Night of: Home-brewed gin and strong English ale.
Symptoms: Madness, loss of consonants.
Cure: “Throw upon ye smoten a medleye… of hollyhock, ground ewe, and Turk’s Ear. Proceed until the Demon departeth through the mouthe, or killeth him asunder” (Cadwallader’s Variouse Cures, p. 62).

11. The Himmler in Argentina
Night of: Beer and peppermint schnapps.
Symptoms: nausea, monocles, persistent fresh breath.
Cure: Malaria.

12. The Forbes 500
Night of: Martinis and alcoholic punch at an office party or convention.
Symptoms: Headache, embarrassing letters to The Economist.
Cure: 8-10 hours of sleep on the floor of an executive washroom.

13. The Sommelier
Night of: Wine tasting that eventually becomes just drinking.
Symptoms: Headache, false sense of culture.
Cure: Anything from Dairy Queen.
14. The Joseph Smith
Night of: Copious amounts of 3.2% beer.
Symptoms: light nausea, sore kidneys.
Cure: High-altitude hiking, polygamy.
15. The Mr. Boston Strangler
Night of: Forcing a mixer to work with an inappropriate liquor, i.e. margarita mix with Jagermeister.
Symptoms: Shakiness, hernia.
Cure: A drop of morning dew from a single white rose.
16. The Frat Paddle
Night of: Keg beer and marijuana.
Symptoms: Dizziness, “bro voice.”
Cure: Raw cookie dough and microwaved bacon.
17. The Willie N.
Night of: Whiskey and marijuana.
Symptoms: “Lot lizard voice,” persistent cough, nausea.
Cure: Scrambled eggs, and more whiskey and marijuana.
18. The Jerry G.
Night of: Beer in tandem with multiple hallucinogenics.
Symptoms: Disorientation, headache.
Cure: Recording yourself jamming with friends; talking about how “awesome” it sounds between each song.
19. The Janis J.
Night of: Variant of the Dancing Bear that also includes any hard alcohol.
Symptoms: Auditory and visual hallucinations, disorientation.
Cure: Writing, directing, and starring in a short experimental film, which should be destroyed immediately.
20. The Lizard King
Night of: Southern Comfort and peyote.
Symptoms: Dizziness, tinnitis.
Cure: Ask your spirit animal.
21. The Hollywood Bowl
Night of: Alcohol and powder drugs.
Symptoms: Suicidal thoughts, dehydration, five-record deals with Sony.
Cure: Yoga, cheeseburgers.
22. The Great White North
Night of: Labatt’s and Seagram’s 7.
Symptoms: Headache, Canadian accent.
Cure: Anything from Tim Horton’s.
23. The Chemistry Set
Night of: non-food products containing alcohol (Binaca, rubbing alcohol).
Symptoms: memory loss, insanity, superpowers.
Cure: Standing near high-voltage power lines.
24. The Crunk ‘n Disorderly
Night of: Cough syrup and alcohol.
Symptoms: Apocalyptic headache, disorientation.
Cure: Platinum teeth, fried food.
25. The Great Pumpkin
Night of: Beer and candy, but no food.
Symptoms: Giggling.
Cure: Diabetic shock.
26. The Czech Mate
Night of: Strong pilsner and absinthe.
Symptoms: Nausea, symbolist poetry.
Cure: Roast duck, “Absinthe-tinis.”
27. The Candiru
Night of: Caipirinhas and fried food.
Symptoms: Nausea, DTs.
Cure: Samba dancing, or, if unattractive, watching people samba dance.
28. The Ice Pirate
Night of: Generally occurs when attempting to “break in” a new blender, which involves blending even those drinks that are not generally blended (Manhattans, Martinis, etc.)
Symptoms: Debilitating sailboat docking fees, lost saltshakers.
Cure: Scrambled eggs and bitters.
29. The Spice Pirate
Night of: Bacardi 151.
Symptoms: Burnt curtains from late-night firebreathing, splitting headache behind eyeballs.
Cure: Conscription by a Dutch merchant fleet, constant whipping with Indonesian birch.
30. The East Egg
Night of: A large number of different drinks, all of which involve gin.
Symptoms: Juniper poisoning, partial drowning.
Cure: Wealth.
31. The False Idol
Night of: Any combination of sweet drinks consumed from a tiki-head glass.
Symptoms: Nausea, persistent sand.
Cure: Throwing someone, or something valuable, into a volcano.
32. The Pineapple Express
Night of: Any combination of “fun” tiki drinks (Mai Tais, Beachcombers, etc.).
Symptoms: Light nausea, diabetes.
Cure: Dried seaweed.
33. The Press Gang
Night of: Variant of the False Idol resulting from imbibing only tiki drinks with dark/violent names (Zombie, Shrunken Head, Suffering Bastard, etc).
Symptoms: Crushing headache, dizziness, neck tattoos.
Cure: Keel-hauling, followed by a Denver omelette.
34. The Blue Hawaiian
Night of: Drinks involving huge amounts of food coloring.
Symptoms: Light nausea, uvula cancer.
Cure: Saltwater and cherry pie.
35. The Dead Soul
Night of: Vodka interspersed throughout any number of other drinks.
Symptoms: Nausea, acceptance of serfdom.
Cure: “In proportion as the exploitation of one individual by another is put an end to, the exploitation of one nation by another will also be put an end to. In proportion as the antagonism between classes within the nation vanishes, the hostility of one nation to another will come to an end.”
36. The Glasnost
Night of: Consumption of vodka for more than 12 hours.
Symptoms: Potato-like appearance and personality.
Cure: Potatoes.
37. The Gulag
Night of: A clear, odorless spirit, provided by someone you only later realize was not a friend of anyone in attendance.
Symptoms: Semi-permanent blindness, hand tattoos.
Cure: Bathing in filtered vodka.
38. The Chinaski
Night of: Beer, followed by several varieties of cooking wine; often an attempt to stifle writer’s block.
Symptoms: Will often produce no usable work, and instead require cleaning vomit out of a typewriter.
Cure: “She was built like a ’52 Chrysler and swore like a sailor… a good hard ride.”
39. The Cuban Missile Crisis
Night of: Alcohol in tandem with cigar smoking; occurs with greatest frequency at bachelor parties.
Symptoms: In severe cases, symptoms include “cometing,” (coughing and vomiting simultaneously).
Cure: A foot-long sandwich of ham, turkey, pickles, cheese, and mustard (AKA “The Cuban Sandwich Crisis”).
40. The Borgnine
Night of: Consuming all alcoholic drinks, non-alcoholic drinks, and food in a refrigerator.
Symptoms: Nausea, fearful notes from roommates.
Cure: Transcendental meditation.
41. The Personal Best
Night of: A post-workout drinking session that becomes intimate.
Symptoms: Headache, awkwardness.
Cure: Orange juice, rhythmic high-fiving.
42. The Venus in Furs
Night of: Near-death from inhalants, vodka, and autoerotic asphyxiation.
Symptoms: Apocalyptic headache.
Cure: Doing it again right now.
43. The Michael Phelps
Night of: Marijuana and Coors.
Symptoms: Headache, prolonged loss of endorsements.
Cure: Carrie Prejean.
44. The Mile High Club
Night of: Drinking throughout a long-distance flight.
Symptoms: Dehydration, jet lag.
Cure: Being slapped by a flight attendant.
45. The Sherpa
Night of: Drinking at high altitude.
Symptoms: Dehydration, severe headache.
Cure: Pancakes with yak butter.
46. The Jack Tripper
Night of: Going on two or more dates involving drinking in one night.
Symptoms: Exhaustion, memory loss.
Cure: None needed.
47. The Jack Palance
Night of: Drinking during robust exercise.
Symptoms: Muscle spasm, testosterone poisoning.
Cure: The Lifetime Movie Network.


- College humor

Wednesday, September 21, 2011

The Cloud's Potentially huge Liability


For all intents and purposes, the cloud has been an overwhelming hit. For most people with readily available high speed internet, it has taken a lot of the pain and cost away from the storage and management of digital content. Adoption of cloud services have hit the point where many people now integrate them into their daily habits. Under normal circumstances, I would consider this to be a good thing, but as things stand, I feel as though this trend is going to blow up in our face. The impending problems have nothing to do with cloud services or the cloud in general. The problem is with the policies placed around how we access it, specifically data caps from our broadband and wireless data providers.
Interacting with the cloud makes bandwidth all the more transparent. Simple interactions with computing, most notably mobile devices that in prior years would have had no bandwidth footprint now do. Our data use now resembles a steady stream rather than spurts. This unconscious background stream will make our bandwidth use all the more indiscernible. However, the advantages of the cloud start to break down pretty quickly without the premise of free bandwidth. As the average household's bandwidth use increases and begins to run up against established data caps, the impending sticker shock coming from overage charges will lead to bandwidth anxiety. This bandwidth anxiety will create a general fear of using any service that is a perceived bandwidth consumer and could end up setting back cloud-based products and services for years to come.
AT&T says the caps will only impact 2% of their customers, but that argument is myopic at best. CNet goes into the details of AT&T's data cap policy:
“Now AT&T DSL subscribers will be limited to 150 gigabytes of uploads and downloads per month for regular DSL customers and 250GB of broadband usage per month for U-Verse subscribers. AT&T's U-Verse service is its upgraded and enhanced broadband service with fiber deployed closer to individual homes. The U-Verse can handle more data traffic than AT&T's traditional DSL network. ... If customers exceed the monthly data caps for either the DSL or U-Verse broadband services three times, they will be charged $10 for every 50GB above the cap.”
Comcast has a similar policy with a 250 GB cap. AT&T and. Comcast represent the #1 and #2 US broadband providers. If a 250 Gb cap seems reasonable, consider this:
In 2009, the average American watched more than 151 hours of video from TV, computers and mobile devices. Increasingly, people are turning to cloud-based services such as Netflix, Hulu, Amazon Instant Video or iTunes for media consumption because it often represents a much better deal for the consumer. Netflix recently shared that their HD video is 4800 Kbps, equaling 600 kilobytes per second or a bit above 2 GB an hour. If an individual wished to forgo a cable subscription and watch their average 151 hours of video online, they will have used over 300 Gb of bandwidth — 50 Gb over current caps. Keep in mind this is just by watching video. This does nit take into account any other online usage.
To people's benefit, the cloud has become quite transparent in most popular services. People watch movies, listen to music, or work on documents the same way they always have, with “magic” happening behind the scenes. People have had no need to change their habits or expectations. Those habits could soon be very problematic for people where they end up paying both to own the content and then to access it. Many will likely opt out of using the it rather than change how they consume content.
These data caps from telecoms risk stifling advancements in cloud adoption and evolution. More importantly, it is putting a huge roadblock in an obvious path society is headed. At this point you may ask, what does this have to do with user experience? From my perspective, a lot. The cloud may have sprung up from technology-minded individuals, but UX designers have been championing the benefits of the cloud and finding new ways to utilize it for the sake of a simpler experience. Under normal circumstances, this would be absolutely fine. However, in this new reality, I wonder how responsible it is for us to continually drive more experiences into the cloud. It would be easy to remain neutral in this situation and argue that these types of issues are not our problem; that our job is simply to design the best possible experience and let the things out of our control fall where they may. A narrow view on the impact of our work would make that argument reasonable. However, an over-reliance on cloud services opens people up to the possibility of ungodly bills or forces them into expensive unlimited bandwidth plans. Neither are good options for the average person this economy. There is a responsibility to design solutions that will ultimately not let people down (in this case, through unforeseen bandwidth overage charges). If our work does not deliver on that tenet, it is not providing a beneficial user experience.
I am not suggesting that the cloud is some pariah that should be avoided at all cost. However, these caps present new experience challenges that need to be proactively addressed. There needs to be greater emphasis on how to make cloud connectivity smarter and, at times, optional. There needs to be clear and detailed information provided as to the amount of bandwidth being used by a service, app or device so people can make better choices as to how to use their bandwidth wisely. People will need to have a much greater idea of how they use data than ever before. It is not only appropriate but ethical to make that a high priority when designing for the cloud in the years to come, otherwise we risk people avoiding it all together.
- Adaptive Path

Saturday, September 3, 2011

What to Expect from Cloud Computing

Cloud Computing: Hot Air or Killer App?


Cloud computing has become a huge ‘buzz-phrase’ in last few years, but you’d be forgiven for not knowing what the term actually means indeed. Different people interpret “cloud computing” in different ways. That’s the dilemma because computing “in the cloud” may be important for you and your organization, but if it’s not clear what it actually means, how will you know?

The chairman of the Cloud Summit Executive 2009 conference started the event by a witty comment that when he asked 20 people to define cloud computing, and he got 22 different answers. The term came into vogue a few years ago and has generated its share of controversy since then. Here are some descriptions for cloud computing:
“Reliance on the Internet for satisfying the computing needs of the users.” (Wikipedia),
“The next step in the evolution of software-as-a-service (SaaS) technology.” (Knowledge@W.P. Carey, Arizona State University’s online business publication),
“We’ve redefined cloud computing to include everything that we already do. I can’t think of anything that isn’t cloud computing with all of these announcements.” (Larry Ellison, Oracle).
There is an obvious ambiguity on what cloud computing is, and what it isn’t, whether it’s a seachange or just another technology fad. Let’s not to get hung up on definitions focusing whether ‘something’ is cloud computing or ‘Software as a Service’ (SaaS), instead let’s focus on the changing IT equation.


Cloud computing disarrays the traditional IT model where one keep buying servers, PC’s and software licenses as ones business grows, to offering a new Information technological path for small –to-mid size business: ‘Clouds’ of computing power , accessed over the internet, become your server and your data center. Also, amidst the clouds are inexpensive applications for use on demand from any location and through various devices.

Many people indeed confuse ‘Cloud computing’ with ‘Grid computing’.Both implies data centers filled with computing resources available over the network, so are they, in fact, the same thing? Actually, no. Grid computing implies the provision of computing resources as a utility that can be turned on or off as required. Computing on tap, so to speak. You pay for what you consume, without worrying about how where it comes from or how much is available. A good example of this is Amazon’s Elastic Compute Cloud (EC2) offering. Customers create their own Amazon Machine Images (AMIs) containing an operating system, applications and data, and they control how many instances of each AMI run at any given time. They pay for the instance-hours (and bandwidth) they use, adding computing resources at peak times and removing them when they are no longer required. Amazon calls this a cloud, but really it’s a grid. The cost of this utility? 10 cents an hour for 1.7 GB of memory, one virtual core, and 160 GB of instance storage, plus data transfer costs.

Cloud computing is slightly different. It implies the supply of applications to end users, rather than just computer cycles. “Cloud-based computing is a type of IT service usually delivered over the Internet, but the defining characteristic is scale — the ability to service millions of users,” said Matt Cain, a research vice president at Gartner. Cloud computing also implies quick and easy provisioning and a simple cost

structure, generally on a per-user, per-month basis, if it is billed at all, he said. Microsoft’s Live Hotmail is a perfect example of an application run in the cloud: It is supplied over the Internet from one or more data centers who-knows-where; it has millions of users; easy self-provisioning; and a very simple cost structure (of no charge per month). So by now most of you would have updated their definitions in your sagacious cerebrum for not to get confused in between them.

When considered is it all really that new to us, I would say,”Ahh! I have heard it somewhere” If some of this sounds familiar, it’s because, excluding the scale, it is an almost perfect description of the Application Service Provider (ASP) model that was in vogue briefly eight or nine years ago ASPs managed data centers and used their expertise to run and maintain all sorts of applications for customers, who accessed these applications down the wire. New applications were written or existing applications were “ASP-enabled,” and these were either shared by multiple customers or hosted on a separate server for each customer. The problem was that very few ASPs managed to get many, and in some cases any, customers. Most disappeared as quickly as they arrived. There were a few successes like Hosted Exchange was a popular offering, and Salesforce.com successfully promoted the idea of software as a service — a low-cost solution to fill a particular need, a commodity rather than a differentiator.

So now definitely one would like to counter the difference between the ASP model and computing in the clouds? You could argue that the cloud is just a fancy 21st-century way of talking about back-end systems that supply software as a service. “The difference is scale,” said Cain. “ASPs never got millions of customers.” It’s interesting to note that just as ASPs discovered hosted Exchange was one of the few things for which customers were willing to pay, it’s also an application that runs well in the cloud. E-mail being the poster child of cloud computing.

"A move towards clouds signals a fundamental shift in how we handle information," writes Stephen Baker in Business Week. "At the most basic level, it's the computing equivalent of the evolution in electricity a century ago when farms and businesses shut down their own generators and bought power instead from efficient industrial utilities." Moreover it ultimately helps CIOs rationalize their legacy systems and get their “arthritic IT” in order, so who would say ‘No’ to it?

Coming back to Cloud computing, there are many advantages of the approach Low Start up cost makes cloud computing attractive to small businesses. One time use applications and business services like Google apps need not be purchased which is a blessing for sporadic users. There isn’t a need to buy additional licenses and hardware as corporates can expand up to n number of users and locations at modest cost. Cloud computing also gives location & accessing independence. A significant advantage being regular upgraded application versions are available to users with changing requirements.

Cloud computing releases sizeable portions of handcuffed IT budgets for corporates. Instead of purchasing additional licenses and hardware, firms can simply open new accounts with cloud based services providers to expand computing capacity.

Also, Users would be more receptive to the idea since the knee-jerks about security and third parties access to applications are less prevalent these days. And let’s be practical — Google is not likely to run out of money any time soon and is probably far more likely to be around in 10 years time than many of its potential cloud computing customers. When put like that, cloud computing starts to make sense. After all, e-mail and productivity apps are commodities everyone uses. They are not strategic apps that give a firm the competitive advantage apps, therefore, why not let a handful of mega-corporations like Google run and maintain them from data centers built near hydro-electric facilities offering unlimited free power for a fraction of the price now spent to license, install and maintain these applications independently. It may not give you the competitive advantage but definitely gives you a cost edge over others.. In Joseph Heller’s words classic novel Catch-22, “if everyone else is getting their apps from the cloud, you’d certainly be a damned fool to get yours any other way ...”

Snapshot of Gooooogle's Massiveness...

Why Microsoft did the right thing ditching XP for IE9


A "modern browser" needs a "modern operating system," and Windows XP doesn't qualify. Much to my surprise (well, not really, I know that XP is still used and, apparently, loved by many), many doubted my characterization of XP as "obsolete," and they questioned my lack of surprise at this decision.
Simple things first. Windows XP is not a new operating system. Windows XP was released in 2001, and it has been succeeded by not one, but two newer operating systems: Windows Vista, and Windows 7. The other major desktop platform vendor—Apple—doesn't even begin to support anything that old, and the company routinely restricts its software compatibility to only the most recent version or two of its operating system.
Now, it's true that software is not like physical goods; while the ravages of time may make hardware break down, Windows XP works as well today as it did when it was new. Better, if you consider the extensive capabilities added in Service Packs and free downloads. But the computing world does not stand still; working as well as it did when it was new means that Windows XP hasn't kept up with computing's advances. The next generation of hard disks (or indeed, current generation, for Western Digital users), for example, are at risk of suffering severe performance penalties on XP systems. To get the best from the technology that for many has replaced spinning disks—the solid state drive—requires support for the TRIM command, found natively only in Windows 7. XP similarly lacks any built-in support for Blu-ray discs.
But what of Web browsers? A Web browser doesn't much care about, say, disk technology, so although it's undoubtable that XP requires more effort to use on modern hardware, this alone shouldn't be a reason for a Web browser to skip the platform. Do Windows Vista and Windows 7 offer capabilities that XP lacks that are relevant to IE9?
I think a pretty compelling case can be made that yes, in fact, they do. IPv6 is—fingers crossed—a technology that will become far more prevalent in the coming years, as the IPv4 address space finally starts to run out. XP does support IPv6 in a limited way, but it can only be configured using arcane command-line syntax. Windows Vista added GUI configuration and made IPv6 a first-class citizen on the network, and Windows 7 rounds out IPv6 support by including support for ancilary technology such as DHCPv6. XP is simply ill-prepared for an IPv6 world.

Web browser security is a problem

Web browser security is a notorious problem, as the recent pwn2own event has once again demonstrated. Windows Vista and Windows 7 have much greater systematic protections against security flaws than Windows XP does. The Address Space Layout Randomization feature makes existing flaws harder to exploit by making systems less predictable to attackers. This protection is not perfect, and there are indeed techniques that allow its circumvention, but every obstacle makes would-be hackers' jobs harder. The protection ASLR offers is also boosted by the use of a 64-bit operating system, another area where XP falls behind (64-bit XP is a bastard hybrid of Windows XP and Windows Server 2003, with the result that much 64-bit software that works properly on Vista and 7 fails to work properly or at all on XP 64).
More substantial protection is provided by the Mandatory Integrity Control feature of the two modern OSes. By marking a process as "Low Integrity," Windows prevents that process from being able to write to the majority of the hard disk and registry. The result is that even if the Web browser is compromised, the attacker is greatly restricted. Though an attacker can read most data (though this too can be restricted), he can't install rootkits, trojans, spyware, or anything else, because he cannot write to the parts of the file system required to do this.
Importantly, this protection has no real means of circumvention. Features like ASLR (and DEP, which is found in XP) are designed to make hackers' jobs harder, but do not erect any hard, kernel-enforced barriers, which is why, with skill, they can be bypassed. MIC erects a much harder barrier; to bypass MIC a hacker would have to find and use an exploit that allowed a process to elevate its privileges to strip itself of the "Low Integrity" label. If the attacker cannot do this, then he is forever trapped in the Low Integrity sandbox, unable to install his malicious software.
Privilege escalation vulnerabilities—software flaws that trick the kernel into giving a process more rights than it should have—do exist, so even MIC is no panacea. But they're substantially rarer than common browser flaws, and they are more likely to be fixed more quickly, because of their scope. Most important is that they can be fixed—they're a result of bugs in the kernel. DEP and ASLR can't be fixed as such; the circumvention mechanisms are to an extent inevitable.

The browser itself is a problem

The track record of Web browsers is pretty lousy. Actually, it's not just Web browsers; the track record of computer software is pretty lousy. Bugs are absolutely rife. But Web browsers are particularly important here, because Web browsers are exposed to potentially hostile code all day long. An exploitable bug in my MP3 player or word processor is bad, sure—it's something that I would prefer not to be there—but with these programs the main thing I'm going to use is my own MP3s and documents that I (or my colleagues) have written. And these files are going to be harmless. But the main thing I do in my browser, practically the only thing I do, is to look at webpages that were put up by other people. Other people who may or may not have good intentions; people who may or may not secure their servers properly, audit their code, or virus-scan their machines.
The result is that my Web browser is exposed to potentially hostile code like no other program on my PC. My e-mail client comes in second, and it's a distant second; even when I get hundreds of e-mails a day, most of these are from colleagues rather than spammers/phishers/other miscreants and ne'er-do-wells. As such, isolating the browser with MIC isn't just something that's a good idea—it's something that you would have to have a really good reason not to do. And frankly, no such reason exists. The Web is unfortunately a dangerous place.
Of the big five, only two browsers currently use this protection on Windows; Internet Explorer (7 and 8), and Chrome. For this reason alone, I'd be hesitant to use Safari, Opera, or Firefox. Their security track record isn't really any better than Microsoft's, and the consequent exploitability of these browsers is much greater.
This advantage is not one that is merely hypothetical, either. In common with other vendors, Microsoft assigns a risk rating to every security flaw, and Internet Explorer flaws on Windows Vista and Windows 7 have quite consistently had lower risk ratings than those same flaws on Windows XP. Why? Because the flaws are greatly restricted by the MIC barrier. Microsoft might be biased, but there are security researchers who concur; Charlie Miller, so successful at pwn2own, regards Chrome and IE 8 on Windows 7 as arguably the safest Web browsing platform. It's no coincidence that these are the browsers that use MIC sandboxing. The protection works.
Windows XP supports none of this protection, nor will it ever. Denying XP users access to its latest and greatest browser isn't a bad thing: Windows XP users should be strongly discouraged from using their machines in any hostile environment. Far from saying that IE9 should be supported on XP, we should be demanding that the other three browsers start supporting these security features and dropping XP support, too. These really are features that everybody should be using.

Graphically speaking

The biggest single reason for dropping XP is not, however, security; it's graphics. Internet Explorer 9 already boasts high-performance, hardware-accelerated graphical capabilities. In particular, Microsoft has shown off IE9's SVG capabilities. (SVG is a W3C standard that enables vector graphics to be embedded into webpages.) These graphics can be manipulated using JavaScript, opening up a whole new world of possibilities for standards-compliant webpages—widespread support for SVG might very well allow standard pages to start doing the kinds of tasks that hitherto have required plugins like Flash or Silverlight to accomplish.
SVG support is found in a number of other browsers, but it's not without its problems. One particular issue is performance. SVGs are mostly pretty slow; static images work fine, but even simple animations suffer poor frame rates. The result is that currently, SVG is only really good for static graphics. That's still useful, but there's a world of difference between a static graphics format and a moving, programmable graphics format. To use SVG for Flash-type tasks requires strong animation support.
The way that Microsoft has decided to achieve this is to use Direct2D for all of IE9's rendering. Direct2D is a 2D vector graphics API that's layed on top of Direct3D, and Direct3D is, of course, fully hardware accelerated. Direct2D is in many ways a pretty good match for HTML, CSS, and SVG rendering; unlike Windows' old graphics API, GDI, Direct2D is vector-based (so allows for easy, high-quality scaling and animation), but unlike OpenGL or Direct3D, it offers a simple programmatic interface that's tailored towards 2D graphics, without the complexity that 3D entails.
Similarly, for text, Microsoft is using DirectWrite. Again, the technology is high-performance, hardware-accelerated, and it integrates cleanly with Direct2D.
Is this the only way to do it? Well, no. An enterprising developer could certainly develop a Direct2D-like API (that is, a 2D API that simplified use of, and was accelerated by, OpenGL or Direct3D) by hand for XP, such that it could be used with, say, Direct3D 9c. DirectWrite is a bit trickier, as hardware acceleration of DirectWrite is dependent on some Direct3D 10-level features, but a reasonable approximation could probably be achieved.
But the thing is, Microsoft has already done the development for these APIs, and they're already shipped, supported, and available to third-party developers. They just require an OS that's been released in the past three and a half years (they're built in to Windows 7, and available as a free download for Windows Vista). It's ridiculous to expect the company to just ignore that it's done all this work, and then do it all again (and this time, to do it as something built in to IE, rather than as a general-purpose library available to any developer).
The other compatible option—abandoning 3D acceleration completely—seems even less palatable. It might be possible to create a high-performance, high-quality SVG implementation using nothing other than GDI, but no vendor has managed to do so thus far. It's certainly not clear that it's worth the development effort, given that an effective solution already exists: use Direct2D. Giving up entirely—throwing performance concerns out the window—leaves you with an SVG browser that's useless for animations, and as such, is severely restricted when compared to one that's a workable animation platform.
As large a company as Microsoft is, its resources are nonetheless finite. Moreover, the lack of scalability of software projects is well-known; getting more productivity by throwing more developers at a project is possible, but it takes considerable care, and can't be done willy-nilly. As such, the company absolutely has to choose where it spends its development time. Re-creating Direct2D, or writing a high-performance GDI-based graphics layer just isn't a good use of its resources. Most significantly, it's duplicating work that's already been done on a more modern platform.

Conclusions

Microsoft wants IE9 to be a first-rate browser, and to achieve that, the company is exploiting modern operating system features. That's precisely what Microsoft should be doing—these features have been developed so that developers can use them, and that includes Redmond. XP can't do the things that the new OSes can do. Kernel-enforced protected mode would be essentially impossible to provide on XP; a Direct2D equivalent would be doable (though DirectWrite might not be), but would require substantial effort, and in any case, an application simply shouldn't have to do such things. These are jobs the OS should be doing—jobs that Windows Vista and Windows 7 do, in fact, do. And not it's not just XP and Vista that support these capabilities. 
Courtesy of Compiz and Cairo, Linux has 3D-accelerated desktop composition, and a 3D accelerated 2D vector API; Quartz Extreme and QuartzGL offer the same for Mac OS X. Mac OS X 10.6 also incorporates a security framework offering similar capabilities to Windows' Mandatory Integrity Control, and SELinux has long given Linux equivalent protection. This is not to say that these features are necessarily as widely used as they are in Windows Vista or Windows 7, but these abilities are clearly part of modern operating systems.
The new graphics APIs, coupled with the security advantages of Windows Vista and Windows 7—advantages that all Web users should be demanding that their browsers support, because they're really that good—make it clear that the new OSes have indeed advanced beyond the capabilities of Windows XP. Yes, I acknowledge that XP still does all that it does just as well today as it did when it was new . But I would also say that people should be demanding more of their OS. A 2001 feature set isn't good enough any more. I know it's also popular to claim that Windows Vista, in particular, really offers nothing new. But it does offer new features; it has just taken a while for software to exploit these new abilities. In sum, there are modern operating systems out there, operating systems that are ideal platforms for modern browsers. XP really isn't one of them: it's obsolete.


The Science of Sipping Coffee... The Art of Making Mugs...


How Good Design Gets Coffee Down Your Gullet on the Go

How Good Design Gets Coffee Down Your Gullet on the GoModern humans make the simple task of drinking a hot morning beverage a challenge for industrial designers.
You want our morning beverage hot, and you want it to stay that way for much longer than is reasonable to expect. You need to drink it with one hand because the other is steering the car, hailing a cab, or holding on while the train whips you into another passenger. Meanwhile, you want to sip your brain-jogging juice without spilling it down the front of your work shirt. Why are you so demanding?
It's O.K. Good design makes it all doable.
Let's start from the mega important top of your travel coffee mug. A good lid will create a seal between the cap and the cup that remains sealed against jostling as well as being tipped horizontal. Approaches vary, but a lid with silicone gaskets usually does the trick.
The next concern is the vent. Without one, a drinking hole turns into a blowhole. "If it's sealed properly but it doesn't have a vent, it could end up spraying someone in the face," explains Francoise Vielot, a senior product manager at OXO. Like with a pressure cooker, steam with nowhere to go will build up in the cup. When there's only one hole, the steam escapes, sometimes violently taking the coffee with it. In addition to an outlet that delivers liquid (which we'll get to later), the cup needs to have a place to let off steam-but not too much, because it's also a gateway for outside air.
If you don't get sprayed in the face, just one hole makes the liquid hiccup on the way out because the cup is attempting to purge its contents and suck up air simultaneously. With two, the liquid and gas work together.
So now, you have a place to drink from, but getting liquid down your throat while swinging a bag, an iPad, and yourself around a corner without burns or stains demands even more of your portable mug.
The liquid needs to be regulated as it pours, or you could end up with a majorly burnt tongue (or a spill). You chug a beer, but you do not chug nearly boiling English Breakfast. There are a couple of ways your mug on the go helps deliver your coffee safely. First, the opening is typically recessed. This creates a landing where liquid gets a momentary shot of air before it reaches your mouth. As Thermos marketing manager Kim Flanagan explains, "How the liquid comes through the lid matters."
A properly sized drinking hole plays a big part in regulating liquid as well. Before launching their line of travel mugs, OXO did a lot of research into the "optimal sipping volume" for piping hot beverages. They found that plastic tear away lids let in more liquid than people preferred. "The length more than the width was not ideal," explains OXO's Vielot. Eventually they determined the perfect sized exit, which was smaller than the tear-aways but a bit rounder than the average Starbucks to-go variety.
The hope, of course, is that once you finally get the coffee where it needs to go, it's still hot when it gets there. Double walled mugs help achieve this by creating a gap between the outside air and the stuff inside the cup. But air between the interior and exterior walls will still conduct the hot or cold. So if you're really serious about temperature, you'll go with vacuum-sealed stainless steel - the removal of that air between walls blocks the transfer of heat across the divide.
That leaves the lid as the main culprit behind a temperature change. The smaller the top, especially for vacuum-sealed varieties, the less opportunity heat has to escape. So, sure, you want a mug that will fit snugly your car's cup holder, but, as Thermos' Flanagan explains, "having the mug tall and thin will allow it to actually hold the temperature longer." The shape also makes coffee-slinging doable with one hand-an absolute necessity for commuters.
When the design is good, the whole experience should be easy to swallow.

By Rachel Swaby