On Moving Toward Software Rentals
CowboyRobot writes "ACM Queue has an article about the emergence of a service-oriented model of software delivery, supported by the W3C, IBM, HP, and Microsoft.
They already have their acronyms down: WSDL (Web Services Description Language), UDDI (Universal Description, Discovery, and Integration), and WSFL (Web Services Flow Language).
The article primarily covers the three phases of negotiating, ending with actual service delivery."
How long before the said software gets "pirated" and publishers invokes DMCA?
will consist of deployment of a crappy too-thick-to-be-thin client, with poor response time, and broken widgets. The vendor will claim that it is due to either 1) client-side misconfigurations, or 2) unanticipated variations in the environment, both of which will be ironed out via a Professional Services contract accompanying the software "delivery". The end result will be the creation of numerous roles at the client's expense to "manage" and "coordinate" the software delivery, frustration at the end-user level, raises and kudos for the middle managers who jumped on the bandwagon, and fat wallets on the part of the shovelware designers.
I want to delete my account but Slashdot doesn't allow it.
I, for one, am terrified of this. In the first, if you are only renting the software, you do not really own it, so they can basically monitor you, or refuse access to the software if they want. Second, they have to have some way to monitor if the software is working or not, depending on your subscription time, which means either every (SUBSCRIPTION TIME) you'll have to reregister and reenter your code, or they will need to have access to your system (via the network, or in the real world) to reactivate it. Scary.
This sounds like a great idea. There have been times when I needed a piece of software just for a one or two time use, and the only things out there for my particular need had high license fees. However, what bothers me is that MS is involved with it. I am worried that they will make the technology OS specific, and finally get a foothold in the internet 'standards' (read MS standards) that they have been trying to do for so long.
My
Is there a need for a new Creative Commons license type that says "if you server services using this technology, I need to share the source"?
I think no existing license covers that need very well today.
>They already have their acronyms down: WSDL (Web >Services Description Language), UDDI (Universal >Description, Discovery, and Integration), and WSFL >(Web Services Flow Language). And WIM Who Ivited Microsort
Everything I want for computer use is pretty much existing in a state I already own (Office, Visual C), or is being developed by a more open/donaiton system (Firefox,Thunderbird,Filezilla,Sunbird). There's a limited amount of applications I would LIKE, and none that I NEED, that don't really exist yet. So why in hell would I pay a monthly service fee for word? When I believe Word 97 was just fine, and now instead prefer OpenOffice more(majority of the time I just use notepad.exe).
The only avenue I see that could possibly get away with rental systems is the game industry, but only if they're rental prices severally undercut store prices. (Halflife 2?). That's the only area where there's consitently a new killer app that is needed. Not exactly IBM's home turf. Mircosoft on the other hand...
Bah, screw the entire thing, just disrupte w/ Bittorrents and Coral, and ask for donations.
Read what they are saying:
The Service-Oriented Model
Sounds like a bunch of hooey to me.
And this one.
Wasn't it not long ago we have this ASP, which gave publishers a new way to sell and distribute software and software services? How is this ASP compared to the new Software Rentals scheme?
Uselessful technology (Air-Charged
I'm not terrified; but would be pleased if software rental were a common option. 90% of computer games I tire of after about 2 days. If the cost was reasonable, I'd be happy to rent most of them; and actually prefer that over buying them.
Can we rent using our Tivo?
But not this one.
"Never attribute to malice that which can be adequately explained by stupidity." -- Hanlon's Razor
and this one
I thought the market already rejected this idea!
Oh well, even if they didn't, I can't see this approach finding any more than a niche market because for commodity software, the price has to be low enough to outweigh the benefits of ownership.
Nobody is going to pay $150/year to rent MS Office Pro when OpenOffice is free to own. $30/year, maybe, but then MS has to make a decision about whether that price is too low to be worthwhile. Actually, at $30/year *I* have to wonder if it's worth it, but then I can't stand the last few version of office because of all the annoying "non-features" I have to turn off to get actual work done.
"Lawyers are for sucks."
- Doug McKenzie
I don't know what the hell this article is all about. Software as a service EXISTS ALREADY and has been around for years! Ever heard of web-applications? Like, say WEB MAIL?!?!
Thin client = web browser.
We run a subscription-based software service, over the web. As the net gets faster, latency goes down, and web-apps will become more and more like desktop apps. Sure desktop apps will always be a bit faster, but for many applications an HTML interface works just fine.
All these new acronyms are just a waste of time. The only thing it will achieve is a PhD for whoever the idiot is that worked on those specs.
This is a solution for the software provider, not a solution for the software consumer.
Without new products to produce, software companies are looking for ways to maintain revenue streams. The problem is, good software development companies do not always make quality service providers.
The ACM Queue is an interesting publication. Every month they turn it over to a vendor to promote their latest scheme. It's a brilliant advertising vehicle, where the magazine *is* the advertisement. For example, an article in the May issue on the benefits of TCP offload engines written by iReady, makers of TCP offload engines. In the same issue, an article on why text mining is replacing information retrieval, from a company who would like to sell you text mining software. And that's just me flipping through the first issue I could find laying about my home. I think everything between the covers of the ACM Queue should be ignored.
SOA refers to a method of software architecture that is en vouge- not just a sneaky business model as the post suggests. I'm sure some businesses will jump on the SOA bandwagon for the idea of subscriber-based income, but those that do so for that reason alone will fail.
.NET, C++, and many other languages.
Web Services, WSDL, etc., all parts of implementing SOA, are essentially ways to provide software services via some network transport (typically HTTP). This makes sense for alot of things. For example, integrating inventory systems in real time. In days gone by, Company A would provide some random way for Company B to access it's inventory/price sheet. Text files, spreadsheets, EDI, etc. All SOA does is apply a machine-readable contract to the process. It says "this server will answer requests that look like ABC with data that looks like XYZ." WSDL, Web Services, etc. are all just about defining that "contract" to cover things like security, data types, etc.
Ironically, this allows for more diversity in the actual implementations. It doesn't matter if your service is provided on a $20,000 HP/W2K3 box running IIS or a $200 Linux box running Apache- as long as it provides a description of it's service, others can consume it- again using whatever language they choose. There are already implementations for most of these standards for Java, PHP, Perl,
So, put up the tin foil, this isn't a massive conspiracy to get you to pay each time you open your "word processor service." It's just a better way to provide data services where they make sense.
...I don't actually "own" my copy of Windows anyway, even though I paid for it?
Isn't this whole "You don't actually own the software you just paid for" thing was old news?
I for one am all over this, please please please let the operational state of my crappy ISP's routers determine whether or not I can get any work done!
"Sorry boss, I can't get that report to you cuz some part of the internet's down."
Package anyway you want it comes down to my not owning something I paid for.
* Winners compare their achievements to their goals, losers compare theirs to that of others.
I think I would definitely pay microsoft $0.10 for every time I used M$ Word. Similar to website micropayment systems, I think that big company's as well as startups may benefit from per use charges. I know of many stock analysis sites that do something similar. ie: charge you $5 for each analysis you download, or $5 buys you 50 reloads of the site.
-------
artlu.net
There is this issue of proprietary formats, that only gets more serious now. OK you can keep your files, but how to read your .doc v9 document if Word v9 is only available on subscription, and you don't have a subscription?
Or what about you create a document, then switch to a totally different vendor (or stop using that very software) and a year or two later you want to read it again. Then you have to buy subscription only to read your own work??
Sure it can have some advantages, but without at least a freely downloadable reader for your own data it won't take off.
Wouter.
I have a hard time swallowing the marketing spin about the customer benefits of this service-oriented approach to software sales. This model is simply a steady revenue stream for software vendors, who will then no longer have to justify to people the advantages of upgrading to the latest version of their software - they simply switch off the software if discontinue payments. As a software developer, I admit this is a deal is fantastic, there's basically no downside, just an upside. As a customer, I much prefer the service oriented approach of the commercial open-source establishment - get the software free, and pay for training and support. Vertical market software developers have been coming up with these schemes for years. There's simply no way a vertical market software developer can survice if they sell software only, as their customer base is much narrower than off-the-shelf software.
What has UDDI, WSDL and WSFL to do with renting of software? .... ...
No I did not RTFA
The poster of the story should have made his story better to get me to RTFA
WSDL ^= CORBA IDL for XML RPC aka SOAP
UDDI ^= universal directory and discovery service, aka a phonebook or DNS for SOAP
WSFL ^= web sergvice flow language aka process or work flow definition for web services or web based applications
That all is TECHNIQUE,
renting is a BUSINESS MODEL.
Most of the poster to this article seem not to see that difference.
angel'o'sphere
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
The first step for the corporate elite in the 1870s-1930s was to try to remove the idea from the public consciousness that natural law is a legitimate basis for our legal system. Then it began to push for a steady expansion of intellectual property law into previously unacceptable domains. Originally patents were very hard to get, you had to produce something truly unique, now you can patent business models!
This is all part of a general push away from an ownership society to a corporatist renter society. Capitalism is not to blame here, fascism is, because it is capitalist doctrine that is directly at odds with copyright holders. Capitalism gave us the concept of a government protecting everyone's property rights and not regulating most aspects of the economy to ensure that no class of business had an advantage over another. It was fascism that gave birth to the idea of controlling the economy to "protect industry."
The software rental model is intended to be the final blow to the idea that customers should have a property right in software. Pseudo-capitalists can come out all they like about how "choice" is what really matters, but choice is utterly irrelevent in every respect when basic property rights are not an option anymore. When no one can own their software in any way, to any degree, the difference between competitors becomes inherently pathetic and trite, just like the major parties in 2000 and 2004.
So what happens? Software companies use patents to protect their business model where copyright law isn't enough, by going after upstarts offering an ownership-friendly model.
But what many geeks and nerds won't get out of this, is that this battle has been raging for not a few decades but for about 144, the first battle being the American Civil War. The public schools frequently gloss over three very curious facts about the Civil War, because that would make Abraham Lincoln look like the most fascist stooge in American history:
Now does it become clearer, when you consider the almost 1 and a half century history of this fight, why the federal government really is a government of the people, by the people and for the corporations? Look at the push for things like UCITA, the goal is to essentially in the long run whittle down and destroy the state contract laws and nationalize them, so that the states, the governments much closer to you and your wishes, and thus further from corporate control than the feds, cannot protect you from the monied interests.
There never has been a conspiracy, because the elite has always had the audacity to operate in the open. For the last several decades, they have unabashedly eschewed any pretense of being Adam Smith-style capitalists and their economic model draws upon a more sophisticated, and moderately liberal version of Mussolini's fascist doctrines. What do you think, "protecting and advancing American economic interests" really means? Adam Smith would call it that vile system of Mercantilism which was an influence on socialism and at odds with laisez faire capitalism.
People have asked me why I vote libertarian, it is because they are capitalists. The party was born and bred from an ideological pedigree concerned with the minimization of the elite's power and influence and the preservation of an ownership society
Click here or a puppy gets stomped!
I've found that in one particular area, bug tracking software which needs to be shared across many people, it makes sense for small development companies to go with 3rd party solutions on a month-to-month basis. It's a lot like webhosting in that respects, though unlike webhosting it can be terminated at any time.
Software rentals probably make the most sense for project-duration needs, especially when some form of remote hosting is involved.
The ______ Agenda
That's all we want to know...
You should be paying for service for a product, not for rental of a product.
IMO this concept is not new; the music industry regards music listeners in the same manner. Perhaps the computer industry is simply "maturing." I see it moving naturally to where the RIAA is right now (Ha, can you see MS suing pirates for using their software when this technology comes out? I sure can).
Another great thing is this will basically eliminate easy pirating. So MS won't get a free ride among those who can't pay the $200 or whatever it will be for longhorn. Those people will be forced to move towards OSS, due to simple economics.
If I "rent it", does that mean it will completely 100% uninstall from my system?
It would show incompetency on the other end much more quickly.
Not that I'd use it.
Please take off the tin foil hat; it is causing brain wave interference.
Do you think that this new model will automatically kill Open Source? You'll "read yourRead my blog: HansMast.com
I was really puzzled by the three acronyms used in the summary. WSDL, UDDI, and WSFL are related to web services, not software rentals. They refer to the protocol negotiation, server discovery, and work flow handling steps in a contract negotiation, respectively. WSFL, in particular, is of no use whatsoever in the software rental model.
Someday, maybe one of the editors will read the submissions before they post them? I'm paying for their services by accepting their ads -- keep this up, and I'm blocking the ads here.
You don't own it now - if you did, you could do whatever you wanted with it; modify it, sell it to someone else, etc.
The only thing this will do is "expire" your software rendering it unusable after a time - which is the part that I think really sucks ass.
- It's not the Macs I hate. It's Digg users. -
Slashdot just ran a story to the effect of "SOAP exists" complete with brand "new acronyms" that are several years old.
Finkployd
software companies are buying up or being bought out by internet service providers. Until that happens, the goals of each industry are at odds.
It is now in the best interests of ISPs to support OSS. Currently, Open Source has massive bandwidth requirements and ISPs stand as the only real barrier to access to free software. It is better for them to support OSS, through mirroring/etc, than to support software subscriptions, which have equal bandwidth requirements yet also take some proceeds from the consumer that could instead be going to the ISPs.
When consolidation starts to happen, though, the combined companies will be able to build-out network infrastructure as an investment in future software 'services' income.
"I assumed blithely that there were no elves out there in the darkness"
The problem is service/rental is that you become beholden to the service, thus you incur a hidden cost due to risk because you could run the risk of losing access to your own data or processes if you can't make the monthly payments. In the non-rental mode, s/w to control your data and processes become sunk cost at worst with ready substitution of the status quo in lieu of new purchases (expenses). There is no compensation for this added cost for the user in the rental model, while the producer is gaining a cashflow series that was originally a single transction - software rental == higher NPV for the seller and lower NPV for the buyer, making it a simple and audacious market power grab.
Rightly, buyers will expect some compensation (I've yet to hear a single argument s/w rentals that really holds water) to justify switching. Otherwise you can expect the creation of non-rental substitutes (Open Source?) or the creation of black markets.
JG
Except reverse engineering the ".doc v9" format will be a DMCA violation, because doing so will require circumventing Microsoft's document DRM. Producing an alternative to Word will be a criminal offense in the U.S.--even if it can be done without access to the Palladium keys in your PC.
One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
Vertical companies' clients are still going to need to service those clients even if the clients choose to rent so companies will get paid rent fees + service fees. For the customers, it would be more expensive, but they can afford to just buy "to own" the software for full price.
For people who buy off-the-shelf software, this is great. There isn't that many softwares that i can't live without except my browser. The first time, i may pick a software that has the newest features like Microsoft Office but later on after a few months discover other software out there that's better like Open Office, so it actually sounds better for me to RENT in the beginning with MS Word.
Open free softwares will still be out there, so they're not affected. There are still a lot of amateur programmers or programmers who want to try something out and put it out there free for people to try.
Let's face it, people will only rent or pay to "own" only if the software is any good.
* weedshare.com 50% to artists, webjay.org iuma.com CDBaby.com Epitonic.com ampcast.com
And now it's closer than ever. Riiight. The only company I've seen make a success of it is SalesForce.com. Siebel made noise with IBM about a year ago with a plan to offer hosted service...haven't heard anything more about that, either.
Part of the problem might be people really don't want to rent software. I think a certain segment of the market will find it to be an advantage, like the CRM market. But many will not, especially smaller companies.
There's also a trust issue to deal with. You can see how many people qued up to give MSFT their credit card numbers with Passport, how many are going to trust MSFT with all their client data?
That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
YUO FAIL IT!!1
English is easier said than done.
Remember that this *is* Slashdot. The fact that soap exists is probably (much needed) news to many of the readers...
How about I rent your software instead of paying one price for it once and owning it. This way I get to pay for it over and over, like an apartment and never get equity in it! Sounds great for me, you got me suckerd!
"If you are a dreamer, a wisher, a liar, A hope-er, a pray-er, a magic bean buyer
SOL.
That's what you'll be the first time you *really need* a rent-an-app, only to find out that your internet connection is down, or the licensing server is down, or any other link in the chain between you and the software.
...when you shell over your hard earned money for a copy of Windows or Office, once they've taken your money and given you the box you don't actually "own" the software, you have just purchased a license to use it (which may be revoked). You have also paid for the installation media, which is yours, however, the software upon it isn't, it remains the property of (in this case) Microsoft.
I am NaN
>And don't tell me that software vendors don't break backwards compatibility all the time, either.
Examples, please?
As opposed to the earlier versions, which were hacked within months of their release.
So it goes to show that if you can get decent encryption into your digital system, and afford to get decryption equipment to your customers, you can keep one step ahead of the hackers.
Unfortunatly.
"So, put up the tin foil, this isn't a massive conspiracy to get you to pay each time you open your "word processor service." It's just a better way to provide data services where they make sense."
Bingo! Someone in this place actually has a brain. There was an "Ask Slashdot" were Google and Amazon's API were given as examples. Praised actually. Now here we have an article that most didn't read (although the summary was read), and everyone's going all hyper-paranoid. Like I said before, and will say again. You all are your own worst enemies. All an enemy has to do is say BOO! and you all keel over from hypertension.
What comes after SOA?
SOL?
SOP?
Me too. Heh.
In fact, I'd be willing to pay them $100000.00 for every time I use MSWorm at home.
There's an easier way to bypass the GPL. You release the code, but make it rely on data files which are proprietary, copyrighted, and trademarked.
This is already done by everyone from id Software to the Mozilla project.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
beer? Or rent as in apartment?
rewriting history since 2109
I can see pros and cons to this.
On the one hand, I don't want to not "own" something I buy. Yes, I know about software licences etc., but until they're tested in court, I don't believe that I can be bound by a contract that:
- I don't sign
- is only presented to me after I've paid my money at the shop, gone home, unpacked the box, inserted the CD and started "setup.exe" or whatever
- seems to present me with no benefits for my requested compliance with a huge bunch of legalese that is beyond the scope for a non-legal person to understand. A contract is *not* a one-way street, and that *is* enshrined in law
On the other hand, I wouldn't mind the option of being able to pay a small amount of money for tools that I only use rarely e.g. MS Publisher. I'll never buy it and I couldn't be bothered even trying to pirate it, so I just track down someone who owns it and use it on their PC for a 1 hour session every year or so. Being able to licence it for that one session looks like a win-win to me.
However, the true showstopper issue is that systems that require me to validate my identity against a central system don't work when my Internet connection is unavailable for any reason. Unless/until Internet connectivity is truly universal and as reliable as my water supply, I can't see people bothering with it.
If I don't need to validate my identity against a central system, and the software only runs X times, then what's to stop me creating a VMware instance, installing the software, running it, then blowing away the VMware instance, creating a new one, installing the software again, etc.? Sure, not many people are going to do that, but being able to do it over and over again with little effort will let some kiddie crack the "encryption" scheme being used and publish a crack for it. Once the crack is published, the system is dead - everyone can pay once and use the software indefinitely.
Renting software, subscription based models, etc. will only be of value when that model provides an aspect of the software that could not be accessed on pure client based. For example, a model with all of the standard options but with ability to access new data from a variety of sources for a market or community. This would then provide much more data to work with, solve new problems, new value added.
Or at least the financial sections of businesses won't.
If the software is used frequently enough to be of use, there is currently no financial benefit to paying as you use it unless you are perhaps already paying a subscription fee for usage (mainframe software for example).
Additionally, how do you budget for this software. Companies typically like to make up a sheet saying we will spend X amount of dollars on this 'solution' and then expect you to stick to it. Have you ever tried to change or add on to a project after the initial purchase? It is always much easier to deal with the financial people when you do it up front.
Vermifax
Logout
And that in an environment where any business is able to choose between different Operating Systems, different middleware structures, different applications with sometimes radically different ways of providing a solution and lots of competition between vendors of various sizes who will do anything for you to get your work. That all might be hard to manage and is too difficult for most clueless managers to manage but do we really expect all that being replaced by one vendor and/or their basic structure to be more flexible.
Gee, by definition is can't be can it?
Maybe if you restate the problem as the inadequacy of current general business management models to achieve software flexibility then at least one other solution becomes obvious.
- A virus scanner without regular updates?
- Payroll software without the current tax formulas?
- Legal software without the latest laws and precedents?
- "Glass cockpit" avionics without current traffic info, frequencies, weather etc?
Anything that requires regular updates lends itself to a rental model. Doesn't mean you have to ASP the whole thing. And btw, what's new here? Who would want to rent an app like Excel that's used frequently but rarely changes? Whatever Microsoft might want, there's still enough competition from previous versions and OSS to stop that from happening.One of these days I'm moving to Theory - everything works there
If, as a customer, I buy some software, I'll stick to it even if it's not perfect and the seller is sure of the corresponding sale. However if I rent it once, find it inadequate or find something better or free, that's the end of the game. And if I use intensively the product, I'll try to buy it ( or even buy a concurrent product if the buying option is not offered), not only because of the direct cost but also for keeping the control of a tool I need for my business.
Actually I can imagine this solution very interesting for rarely used, large, expensive and specialized software that would not be bought otherwise. Typically, because I am a small user of a certain product, I'd be really interested in renting for $200 each time I use (once every two months) this $10000 analysis package that I would never buy otherwise.
If Microsoft does this for Windows or Office, whether for corporate or individual customers, it will rapidly loose its dominant position.
I have never needed more than Wordpad
offered. RTF has everything you want,
fonts/sizes,align left, align right,
padding, pictures bullets,
its got everything
and what if Word or whatever keeps crashing on you, and you have to pay 10 cents to M$ pr restart? That would add up!
I think we have the mysterious second step in our famous sequence:
1. Invent a free OS that works via HTTP.
2. Find some suckers to rent that OS.
3. Profit!
Okay, so some of the kinks have yet to be worked out.
RMS has always maintained that there should be no restrictions placed on using the software, and actually if your license contains such a clause you will have to make the user click through it, since starting a service using your software is allowed by default in copyright law.
If the WSDL file which is served up by the server has a GPL license attached to it, then no client software would be able to use this "code" without themselves being GPL software.
Right?
But I suppose a mechanism other than WSDL might be harder to protect in a similar fashion.
Karma: It's all a bunch of tree-huggin' hippy crap!
We have an article on "Negotiating in Service-Oriented Environments"
Someone posts this as "service-oriented model of software delivery"
People react to it on how software-service is the next biggest / worst / whatever thing.
If only some would realize, it is about negotiating to get to a software service that you can use...
There is so much fantastic Free Open Source software around these days, who the heck bothers *buying* software, let alone renting it...
Is this the last gasp of the proprietary software business, desperately looking for ways to fleece the customer for every last penny ?
Thanks, but you can keep your software "rentals".
And thus History will repeat itself. IBM apparently hasn't learned from its software-rental, mainframe days...
WSDL (Web Services Description Language), UDDI (Universal Description, Discovery, and Integration), and WSFL (Web Services Flow Language). The article primarily covers the three phases of negotiating, ending with actual service delivery.
yeah right, i can already see the heads of my fellow programmers exploding when trying to learn yet another protocol.
Could we make an effort to keep things simple. PLEASE !
You obviously don't work in the industry, or you work at some old-fashioned company with no decent vision. We've been working with web services with MANY of our suppliers for YEARS. And I know MANY companies that's selling software as a service RIGHT NOW and making a huge success.
We do that too. We give our clients the option: Buy the licence outright, or rent it. So far out of 700 sales we have not a single buyer.
Also I hear BS about how this is bad trusting a third party with your data. The truth is that these companies will take MUCH better care of your data than the average user will. I.e. continual backups, proper security and the like. Our clients can sleep easy knowing that a dedicated team of professionals are looking after their important data very carefully.
The commercial software industry has been pushing this wet dream for how many years now? Under how many different names? Dick-er-diskless workstations, thin clients, Web services, application service providers, this-that-and-the-other "open" licensing, Windows Update...oops!
It's never gonna fly. Even senior managers understand it's a gigantic juggernaut. Try and tell the COO of any major corporation how wonderful it's going to be that someone in Kuala Lumpur is going to push a button and install an "enhancement" to his bookkeeping system while they're figuring the quarterly dividend. Hell, what's a few hundred million one way or the other? How about the same thing happening while they're counting the votes in a Presidential elec....oh, yeah, I forgot...
Users will choose software as a service because of the benefit it has over traditional software. For a large section of the software market this will make traditional software pale into nothingness compared to what service-based software can provide:
- Access your data anywhere you want, from any PC that has a browser
- Don't worry about losing your data, since a team of professionals will make sure it's secure and backed up at all times
- Never worry about updating and upgrading - it will happen automatically.
- Connect your software with other systems in real-time, without you having to buy a server.
- Have more sex
- etc.
In a word: Duh! We already see web-mail services being better at filtering spam, easier to access if you're away from your normal PC and so on. Many users pay for this service. I know quite a few businesses that won't use their ISP's mail server, because of these reasons. They choose web-mail. This is expanding in many many different sections of the software market. The big players like MS will take longer to start doing this, because they have a significant investment in creating traditional software. But newer companies like Google will start to exploit the benefits they can provide with web-based software. In 10 years I'll bet that a large percentage of software systems will be service-based, probably over a browser or other thin client.
"How long before the said software gets "pirated" and publishers invokes DMCA?"
How long before all your "secrets" get "borrowed" and you invoke the privacy and "identity theft" laws?
of greed- they can't SELL it any more so they'll RENT it. This is reminiscent of CRM and the move to locking down mdeia files to a particular player. GREED. How much cash do the big boys want?
"even Karl Marx said that the tariff, not slavery, was the issue"
And if Karl Marx said it, it must be true, right?
Well, it's a nice change to see a libertarian quote Marx as an Infallible Authority, instead of Ayn Rand or Robert Heinlein.
(BTW, anyone who talks about "the" issue that caused the South to secede/started the Civil War reveals in one step that they don't know what they're talking about. As usual in history, more than one issue/cause was involved.)
http://everything2.org/?node=acronym
Escher was the first MC and Giger invented the HR department.
First, the example you talk about doesn't really apply here. It makes sense to pay every month for a mail server because electricity, a network connection, support, etc are recurrent charges to the mail provider. If you owned your own, you'd do exactly the same. You pay somebody else because you don't have the infrastructure or admins for it. There's no way a mail provider could charge a single fee without going bankrupt due to customers who use the service for too long.
Now, it makes no sense at all for software. When I buy MS Word, MS doesn't need to pay every month for the maintenance of that service. I'm the one who pays for the electricity for the computer it runs on, and the one who pays for the support.
Second, you present a kind of a renting 'Nirvana' where everything will go great and nothing will ever fail. In practice, outsourcing critical infrastructure is a *huge* mistake, because then it will be out of your control. If your company's business will grind to a halt without a working word processor, you don't buy a subscription that makes it possible to suddenly stop working.
Even if your data is all safely backed up, what happens when this company goes out of business? Are you sure they'll make an effort to contact you to send your data to you? Will you be able to do anything useful with it if they disappear?
Easy - use OpenOffice!
Sent from my ASR33 using ASCII
It says you can run your server with all OSS software (bsd, GPL, and other OSI certified license), or you pay for the closed-source version.
This means that OSS apps can use the framework for hosting their systems, but if you want to stay closed source, you need to pay. It's primarily that way for business reasons -to make companies who dont want OSS code to pay- but it's an interesting idea.
I must disagree, somewhat.
There is no direct linkage from the client to the server, simply an XML file that provides hints to the caller as to what structure to send messages. Hints that may or may not be ignored.
WSDL files that are hand-written may be released under a license, but what if the WSDL is machine generated by a runtime, such as the Apache one?
Nor is it mandatory to use WSDL to talk to a SOAP service. With any written documentation as to request structure I could perhaps rewrite my own WSDL/compose XML messages without any direct importing of the WSDL File. Or I could use the WSDL from a non GPL server and then rebind the client to a GPL instance. If they shared the same WSDL (and consistent behavour), I should not have to care what the licensing of the endpoint was.
-Steve Loughran, Apache Axis SOAP stack team.
Look at it this way:
Right now, I could take a program which accepts text input and gives text output, which is GPL, and attach to its standard input and output. There is no linkage from that program to mine, but most people would agree that my program constitutes a derivative work.
Now, put the program on the other end of a network connection. There is still no linkage from the program to mine, and the results of my program are still the same, so it is still a derivative work. If it isn't, then I can use this trick as a loophole for any GPL software which accepts standard input and output! I can just write a server, have it listen on localhost, and then everything will work just as before.
Now, make the network protocol XML over HTTP. Why is the client still not a derivative work here?
I say that in the end, the program author decides what a derivative work is. If I decide that connecting to my web service with a client makes that client a derivative work of the service, then it is a derivative work. Whether or not it technically stops users abusing the license is irrelevant, as people will abuse licenses forever.
Karma: It's all a bunch of tree-huggin' hippy crap!
kose ku tose
gawusi sep bot kal se
sep xi gugoc na
So, does this mean I can ask for renumeration for the bandwidth they use while I'm using their software? I do have to pay for the bandwidth & their software after all.
If my program is just using the input and output from program X, my program might require program X, but it's not really derived from program X. In my book, and using a strict definition, a "derivation" is something that is a modification of the entity. For instance, most of the 8-cylinder engines used by Ford are derivatives of each other (they share common components, common limitations, etc). However, a vehicle that uses that engine is NOT a derivative of the engine! (Of course, some cars themeselves are derivatives of each other - like the Lincoln Navigator and Ford Expedition). Something that uses a library should not be considered a "derivative" of that library - only other things that are a modification of that library should be considered a derivative. Other libraries that serve the same purpose as a given library should also not be considered derivatives (unless they are, of course, modifications of another library).
This probably sounds like I'm trying to take away ownership power from those folks who write core libraries, but that's not my intention. My goal is to point out that if you start broadening the definition of "derivative" then [greedy folks] will likely start to extend this into the physical realm - is a house a derivative work of a brick?
Sure, I'm beating the semantic horse here, but it's important to understand the implications of all proposals. The goal of GPL is to increase public knowledge by making source code available while affording the authors some appropriate protection to the ownership of their work. Another goal of the GPL (and similar licenses) is to discourage making a profit by people with no vested work in some resource (namely libraries, a tool, etc) without making those same resources available. (There is nothing against making a profit by using the resources - just against keeping a lid on those resources).
Another thing mentioned in a grandparent post brought up a tricky point: is output a derivative work of code? It's very dangerous to say that this is true in a general case because then you create precedent for saying things like "the sound waves produced by my speaker are a derivative work of this copyrighted song". If the output of a [piece of code] is some other similarly usable form of that [piece of code] then the output could be considered a derivative work, but output in general is not a derivative work of anything. (If the output of a picture-editing program is a modified other picture, is that a new picture entirely or a derivative of the first picture? This is a tricky thing in the print world - think about making a mosaic of pictures from magazines; that mosaic uses all copyrighted pictures, but itself is a new piece of art - does permission from each of the individual copyright holders of each little image need to be obtained to reproduce the mosaic? I don't know the answer to that one...It's trying to answer the question "how much do I have to modify a thing or things to make them no longer the original things or based on the original things?" - much more challenging with creative products rather than physical ones.)
Playing the "derivative works" card is powerful, but much care needs to be taken. I think I've only touched on a couple of the issues, but as you can see there's a lot at stake.
While I respect the view that it should be the "author's decision" if something is derivative or not, I'd rather have some objective measure defined - even if I might not agree with it.
"There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
Remember? In GITS1, she could always opt out of the system, provided she returned the company software operating her brain. Not Open Software, so no thanks.
``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
SOB, of course.
As in this POC is a SOB to actually use in reality due to its <machine-readable type="xsd:humn-unrdbl"/> self-describing format, that does nothing to eliminate the requirement for a human developer to understand the system they are connecting to and how to use it..
Openoffice.org should be a site which loads office applications into you browser
Then people would be female dogging even worse about "OpenOffice.org is slow". Currently, a Java platform run-time environment takes too long to start for these to compete with Microsoft Office. In addition, for those programs that aren't backed by Sun, a code signing certificate to allow web-based Java programs to save to your hard drive often costs too much for free software developers to deploy the programs.
What's the difference between renting and licensing, anyway? In terms of what you, the consumer, are entitled to--it's close to nothing.
The industry will never move into renting because the gig is too good with licensing. Consider this from the point of view of enforcement:
Violation of a rental agreement is a civil matter which requires the provider to retain their own legal counsel and make a case against the offender. Violation of a license agreement is a felony which the FBI will be happy to investigate and the US Attorney General will prosecute for you.
On the other hand, this could be a political push to broaden the powers of the provider for the violation of a rental agreement. Now your landlord can have your butt thrown in jail by the FBI if you're late with your rent.
+++ATHZ 99:5:80
How many people with valid licenses for Windows 3.1 are using those licenses? I would venture that many of those people who have multiple valid licenses for OS or other software products are using only the most recent versions.
Software rental is effectively a reality now.
It's just the time period of rental is longer than the software manufacturers would like.
Degradation into uselessness, upgrade treadmill, - whatever you want to call it - has already made temporary use of software a practical reality.
"Provided by the management for your protection."
It'd be nice if this guy had any chance of winning. But he doesn't.
If services are rendered without actually transferring a binary executable of the GPL'd software, then the GPL doesn't care. Otherwise there would already problems with any GPL'd server performing any kind of service. It's not about services performed; it's about copying the code.
More control for them, even less control for us.
Is this going to help the customer in any way, will it increase the quality of the software, will it be cheaper for the customer? My guess to all these questions is - NO.
On a long enough timeline, the survival rate for everyone drops to zero.