You may use the camera application on a regular basis. Taking photos of family gatherings, of the scenery around you, or just a self-photo with you and your friends. But, as you may find out, pressing that picture button on the screen is not the easiest thing to do. You may not hit it when you attempt to press it, or you aren’t sure if you pressed it at all.

In a recent update by Apple, the iPhone can now take photos without the use of that button. Although you may continue to use it, an easier method to take photos would definitely be pressing your volume buttons. When you have everyone situated, and ready to take a picture, you don’t have to move your finger over to the camera button. Just put your finger on one of the volume keys on the left hand side of your phone, and press it, and your iPhone should take the picture! It’s just that easy.

When asked for my pearls of wisdom on this topic, I was tempted to respond with the excuse: "Sorry, can't comment. My asbestos underwear is out for dry-cleaning."

It seems both the emotions and mis-information surrounding HTML 5 run high.

And some information is just plain scary. Consider this direct quote from the W3C.

"The following elements are not in HTML5 because using them damages usability and accessibility:

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

As the cloud buzz is getting louder with every passing day you are tempted to take the big leap into the cloud but may have restrained yourself paranoid by ad infinitum cloud security discussions floating on the web. No one can deny the fact that your data is the lifeblood your business. So, undoubtedly its security is of paramount importance for survival of your business.  As cloud computing is a paradigm shift from the traditional ways of using computing resources, you must understand its practical security aspects.

Is Cloud Computing Safe?

There can’t be a binary answer (Yes or No) to this question. But with my experience and as an authority on the subject I can tell you that technologies enabling Cloud services are not in any way less secure than the traditional or on-premise hosting model.  Also, with the evolution of technology, the cloud providers are getting matured and almost all the providers are offering built-in security, privacy, data backups and risk management as a part of their core service.If you are not a big IT company then you must ask yourself:

·         Can an on-premise solution or a traditional hosting provider match the same level of standard security and privacy requirement as provided by the specialist cloud provider whose core competency lies in providing state of the art security and privacy?