Slashdot Mirror


IBM Locking Up Lots of Cloud Computing Patents

dkatana writes: In an article for InformationWeek Charles Babcock notes that IBM has been hoarding patents on every aspect of cloud computing. They've secured about 1,200 in the past 18 months, including ~400 so far this year. "For those who conceive of the cloud as an environment based on public standards with many shared elements, the grant of these patents isn't entirely reassuring." Babcock says, and he adds: "Whatever the intent, these patents illustrate how the cloud, even though it's conceived of as a shared environment following public standards, may be subject to some of the same intellectual property disputes and patent trolling as earlier, more directly proprietary environments."

2 of 70 comments (clear)

  1. This cloud by SirAudioMan · · Score: 4, Interesting

    ...will eventually crash and burn. Sure it's convenient, powerful and cheap, but inherent with major security risks. If I were a company, there is no way in hell I would ever deliberately host or put anything on the cloud. I don't care how 'secure' things are, there are way to many attack vectors and unknown vulnerabilities. It's only going to get worse before people start to see if for what it truly is - dangerous!

  2. Re:If you can't beat 'em... by bws111 · · Score: 5, Interesting

    So much wrong here it is hard to know where to start.

    Legacy? POWER 8 was released later year. Z13 was released 6 months ago. Z13 is a brand new design.

    As for that post you linked to, let's just say the writer is an idiot. First and foremost, you can not compare MIPS numbers between two different architectures. Ever. And you can't compare MIPS numbers between two different workloads. Ever. But this bozo attempted to do just that.

    Secondly, NOBODY buys the 26 MIPS model for production use. They buy it as a hot backup. By buying that model, they save a ton on both hardware and software costs, but can convert it to a full speed machine, about 150x faster, in seconds should they need to transfer workload from a primary machine. But this idiot tried to use it for productive use, and complained that it was slow. Duh.

    Lastly, he complains about the disk configuration, but doesn't seem to have a clue how to set it up. All current DASD that supports CKD mode (max 9GB disk size) also supports SCSI mode. But for some bizarre reason he configures it as CKD over FICON, then complains about it. If he had a brain he would configure it as SCSI over FCP, and have up to 2TB images, which work just fine with z/VM and Linux.