Skip to main content

Diane Greene Interviewed: Co-operate and Compete?

Where Ms Greene differs from the old school of high-tech bosses is how she sees the interplay between competition and co-operation. “I grew up playing Monopoly and Risk,” she says. “You have to collaborate to win these games—and compete when it is time to compete. But if you compete and break somebody’s trust you are going to lose the next time.” Maintaining trust means always being clear about what you are doing, she says, particularly since many of her firm’s partners are also rivals. What is more, Ms Greene argues, “With the internet, you can compete more effectively by being open.” When Microsoft tried to restrict how VMware’s customers could use its software with Windows, for instance, customers complained publicly and helped VMware prepare a white paper about Microsoft’s licensing practices that was posted online—after which the software giant relented.

Sadly, being open and playing nice has often been a recipe for losing against Microsoft. Even within VMware, some people observe that the co-operative approach often boils down to waffling. Others worry that VMware has not yet decided what game it is playing. Ms Greene’s plans for VMware do not sound terribly ambitious. In a nutshell, the company wants to turn virtual machines into “containers” for software and data. Firms can assign quality-of-service and security requirements to these software containers, and have them run wherever they want, be it on their premises or out in a computing “cloud”.



One thing is for sure: It is time to do one or the other

The Economist

Comments

  1. "One thing is for sure: It is time to do one or the other" -

    really? what makes you think VMW has to go one way or another? just because things were "done that way"? maybe this hybrid approach could work. lets not come to any conclusion already.

    ReplyDelete
  2. Yeah really! You wanna know why?

    Because it just work work in VMW's case, maybe 10 years down the line, it might but as of now it won't. There have been good host-complementer relationships in the past, which have culminated in either acquisitions or cling-on scenarios.

    Eventually people buy from people and I can tell you, VMW must exercise a lot of caution of attempting to do both. In a case of a typically "moderate" firm, it may have worked. VMware is far from moderate in its approach and it will have to watch out before try do strike a co-operate and compete pose. Monopoly is a game, real world is different.

    This hybrid approach will not work if it comes to VMW and Microsoft. Their leadership, strategy and future directions are totally different.

    ReplyDelete

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op