Yiddish or High German
- suffering from neurotic symptoms of fear about imaginary threats
- nervous or sweaty
- concerned and anxious
I always liked Mike Meyers schtik on SNL as the leader of a coffee klutch discussing the errata of the day. I stepped into a similar situation today on Twitter.
I try to keep up with the latest social media technology, social butterfly that I am, but at my age and diminished health, I am finding it more and more difficult to keep up.
First, who set the arbitrary limit of 140 characters on Twitter. I find that my thoughts fit much better in 300-500 words, with more profound truth requiring at least an 800 to 1000 word column. Too often, I find my posts to be inviting flames.
For example, I read a piece about VMware’s acquisition of Virsto by a prominent storage blogger that provided real insight into the acquisition — to accelerate I/O between server and storage. The piece seemed to suggest that Virsto was expediting read-write to disk by using a proprietary bit of technology for transferring bit patterns between memory components on the server and storage array. I couldn’t understand why you would want to do that in a proprietary way when IETF has come up with (last I checked) a fairly decent standards-based protocol called iWARP for that purpose already.
The key was to do it in a managed way. I get that. And maybe Virsto provided some capabilities for managing the transfers. But, then I thought about what X-IO had already done with it RESTful management on the Intelligent Storage Element, setting the stage, again using an open standard management protocol REST (part of the W3C protocol family), for profiling application access patterns and adjusting I/O interfaces to accommodate the special needs of specific workloads or apps.
Bottom line: my reaction to the reportage was a shrug. What was special about Virsto that merited its acquisition for some unknown sum? More to the point, why are we trying to fix I/O slowdown (symptomatic) instead of fixing the root cause of the problem (VMware hypervisor)?
I worded these observations badly, I guess, and received strangely worded responses.
I had no idea what that meant, until a follow-up post told me that I was using buzzwords to activate tags and SEOs, thereby playing buzzword bingo.
Ah hah. I had heard of SEOs (just below where I am typing this in WordPress is a location I never use for entering SEO — or search engine optimization — terms. I have been tagging posts with keywords to enable searching for a long time, but never understood the point of SEO stuff. Extra work that seemed unnecessary looking both at my traffic and at the top of search page results that accompany subjects about which I frequently write.
More to the point, I felt my stomach sinking. Faclempt, you know? Troubled that I was being construed to be criticizing the writer rather than the subject, which I don’t think I was.
I kept getting peppered with comments and couldn’t seem to right the situation. I withheld my view that Virsto struck me as a tinker-toy approach to I/O acceleration, figuring that that would be taken as more criticism of the author, who for some reason seemed inclined to defend VMware.
I noted with what I thought was wry amusement that VMware’s ecosystem of vendors seemed to exist to fix problems created by VMware. How weird is that?
Instead of a convivial response to my jocular assertion, I sensed heat in the defense offered by the writer: he asserted that VMware’s ecosystem was no different from any other industry ecosystem. That was an interesting assertion that I felt a need to address with a comparison between symbiotic ecosystems and parasitical ecosystems.
The basic difference between the two ecosystems is the goal of addressing consumer requirements with effective standards-based technology sporting architectural excellence embellished by partners with best of breed add-in components (symbiotic) versus the an ecosystem that approaches consumers in a predatory way with the goal of replacing flawed technology with a different sort of flawed technology, supported by pay-per-view analysts and pundits and massive, well-funded marketing campaigns — hoping to make a lot of money in the manner so well articulated by PT Barnum before being found out and ridden out of town on a rail.
This idea too was not well received: the writer described the nature of the VMware ecosystem as one of “opportunity” and suggested that I was abdicating my self-described role as “hard headed realist” for something approximating a California Avocado Dip Creamy Smooth Liberal Idealist — you know, all loving toward standards that reduce vendor differentiation and, ultimately, profitability.
I found myself breaking my anti-bullying rule and declaring that the literature from Virsto and EMC/VMware to which the fellow’s blog post linked was a poster child for propaganda. It gave me the same sick feeling I get when I read reports about GOP efforts to re-brand their party: instead of addressing issues that lack appeal among the majority of voters — present and future — they are instead trying to come up with new phraseology that will make bad ideas more palatable. So, it is with server hypervisor woo peddled around VMware generally — and this latest Virsto product acquisition in particular.
Concurrently, I was having a conversation with another tweeter about the meteor hits in Russian earlier today. He was getting very hostile about the fact that NASA and the media are so focused on a meteor expected to narrowly miss the planet (by 17K miles) tonight, but that Russia got virtually no heads up or media coverage for its meteor hit. I offered that we had sent them Bruce Willis (the latest Die Hard flick is based in Russia, I think), so that should be worth something. (Willis, Affleck and a few others are expert at blowing up meteors and comets while they are in space, I seem to recall.)
Miraculously, he got the joke and laughed in caps. HAHAHA
Or was that just a kind of buzzword bingo?