The House has passed an amendment to a larger bill that will streamline federal IT and finally empower CIOs - those able to keep their jobs as CIOs. Federal CIOs have long felt powerless and this bill, as this fedscoop story says, only restates their duties.
If passsed, the amendment, according to the story, would call for seriously denting the ranks of an estimated 250 federal CIOs. But with government, mandating and doing are two different things.
You raise some great points, but the public cloud ship has sailed. Companies have woven the public cloud into their business models. Some companies IT is solely the public cloud. So I think the idea that PRISM will kill the public cloud is not valid...at least until there's some incident, botched government snooping or compromised data. I also point out that the U.S. government (not sure about Canada where you reside) can come after your data no matter where it is. The public cloud might make it easier to snoop without the data's owner knowing it, though.
In my last blog post I pointed out you can never actually avoid vendor or technology lock-in. This is particularly applicable to the main orchestration tool you use. You have to choose one orchestrator and will want to stay with that choice for quite some time. So, making the right choice is key.
As I mentioned previously, I’m privileged to meet with companies on a regular basis. And I don’t know how often I’ve had a discussion around the subject of vendor lock-in. I clearly understand the fears companies have to hook themselves with a vendor and not be able to take advantage of innovations coming from other sources.