Practically all my meditation training has been in disciplines of opening the attention to admit all available phenomena, in order to learn to be present with them. But as someone easily irritated by sensation, it’s incredibly therapeutic to me to close my attention to outside phenomena, especially if I’m trying to concentrate.
Even though it’s the opposite of my meditation instructions, I can’t shake the feeling that I’m still practicing when I’m doing this.
Often I can’t achieve this state of closed concentration without a pair of noise-canceling headphones and a good myNoise setting. But once I’ve got the world well and truly blocked out, deeply interesting things begin to arise.
For one thing, my mind quiets itself. I get a clear sense that the thinking part of my mind is like the surface of a pond, and the world is chucking rocks into it all the time, creating unending turbulence. When I artificially put a force field around the pond, it quickly goes still. Only slight perturbations from below the surface ripple out, and they dissipate without a trace.
An emotion of relief arises, too, and that quickly gives way to compassion. All beings are having rocks tossed into their ponds, and even the best force fields are impermanent. My gratitude for a brief respite is powerful enough to reorient me towards the outside with an attitude of leaving no trace, tossing no rocks, even a desire to protect others from disturbance.
Doesn’t that sound super Buddhist? Yet no Buddhist-trained person has ever told me to block out sensations. Maybe I just haven’t asked the right question yet.
"An attacker sends an infected packet to a fitness tracker nearby at bluetooth distance then the rest of the attack occurs by itself, without any special need for the attacker being near," Apvrille says.
"[When] the victim wishes to synchronise his or her fitness data with FitBit servers to update their profile ... the fitness tracker responds to the query, but in addition to the standard message, the response is tainted with the infected code.
"From there, it can deliver a specific malicious payload on the laptop, that is, start a backdoor, or have the machine crash [and] can propagate the infection to other trackers (Fitbits)."
Either way, the disparity is enough to motivate an Occupy Amazon crowd. The problem for detractors and competitors, though, is that Amazon doesn't seem to be in the mood to misstep. The only thing that will cut into its lead is someone else catering to developers as well as AWS has, and that doesn't look likely.
Public Cloud: Big And Getting Bigger
It's becoming increasingly important to get out in front of AWS. The problem, as noted by Leong, is that the delta between AWS and everyone else is so huge, however you measure it:
Such "scale" advantage isn't really a matter of data center build-out, she goes on to note, but really is a matter of software. AWS has such an impressive array of developer-centric software infrastructure, which translates into developer services, that closing the gap will be brutally hard.
Why? Because AWS benefits disproportionately, as network effects drive vendors to focus their cloud attentions on AWS. If you're a vendor choosing where to host your new service, AWS will nearly always be the first choice. If you're a student, AWS will be the first cloud you learn, and possibly the only one. And so on.
Early on, while most cloud vendors were fixated on IT, Amazon devoted itself to developers, and has become the default for most developers.
Competing With The Amazon Beast
Competitors have taken notice, and are actively trying to market against perceived AWS weaknesses.
And from public cloud peers, we get much the same, with Google and Microsoft lobbing price reductions at AWS. They haven't worked. Pulling up stakes on one platform to move to another is more than a matter of saving a few dollars. It's a hassle, one that can only be justified by making the alternative cloud more convenient.
GigaOm's Barb Darrow asked which one vendor had a shot at displacing AWS, with a broad array of responses. I can't help but think that most of them are wishful thinking.
Microsoft actually can serve as a role model for would-be Amazon usurpers. When you strike at the Amazon king, you must kill him with developer convenience, not with price reductions or stories of better performance, security, etc. Convenience sells developers.
AWS took a dominant lead with a strong developer story, and Microsoft may well be closing that lead through a differentiated, developer-focused story of its own. Game on.