
	Where results make sense

Topic: Vendor lockin

Related Topics

Vendor Managed Inventory

Street vendor

operating system vendor

In the News (Tue 15 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Vendor lock-in - Wikipedia, the free encyclopedia
		In economics, vendor lock-in, also known as proprietary lock-in, lock-in, or the Pottersville pattern, is a situation in which a customer is so dependent on a vendor for products and services that he or she cannot move to another vendor without substantial switching costs, real and/or perceived.
		Vendor lock-in is often used in the computer industry to describe the effects of a lack of compatibility between different systems.
		Vendor lock-in for higher-end cameras takes the form of incompatible systems of lens mountings: a photographer who has purchased lens and other equipment from one manufacturer may find switching to a rival brand prohibitively expensive.
	en.wikipedia.org /wiki/Vendor_lock-in (1080 words)

	Talk:Vendor lock-in - Wikipedia, the free encyclopedia
		The article seems to assume, or at least imply, that vendor lock-in is somehow bad, an evil tactic, a problem to be combated.
		It seems odd to me that at the end of a page giving an overview of Vendor Lock-in that there are 5 refeence links, 3 of which are by the same pair of economists, who basically disagree with everything on the page.
		If the links are to remain it would be better if there was a section for criticism of 'vendor lock-in' where the arguments against 'vendor lock-in' could be presented, and perhaps more than one pair of researchers can be found that argue this point.
	en.wikipedia.org /wiki/Talk:Vendor_lock-in (1016 words)

	Enterprise Java Community: Selecting a J2EE Vendor
		It is also recommended that your organisation shows the vendor your technical evaluation before the final decision is made - it is unfair to them and to your organisation if you withhold the evaluation, and it ensures that your impartiality and integrity is kept at its strongest level.
		Vendors who are quick with new technologies tend to leap frog each other in quick succession and then come into par for a while, and then play the leap frog game again.
		Vendors will want to work with the IT manager and business people, but they should also assign a technical person to be at your call when you need to know certain information - especially if you wish to prove certain things.
	www.theserverside.com /articles/article.tss?l=Selecting-a-J2EE-Vendor (5846 words)

	The Old Joel on Software Forum - Does "vendor lock-in" really exist?
		Although vendor lock-in is used to describe modern software lock-in, I think the term arose in the days when choice of departmental computer dictated application software and everything else.
		Anyway, the real point is that vendor lock in has to be taken seriously when Microsoft had enough problems porting an application to Windows that they ended up using an implementation of UNIX on top of Windows to do the job.
		Another lockin issue where Microsoft is a prime (but not unique) example: a lot of MS documents are undocumented binary formats which work with specific versions of software (e.g.
	discuss.fogcreek.com /joelonsoftware?cmd=show&ixPost=64525 (3244 words)

	Setting the traps of Vendor Lock-in
		Following on the theme of the Long and Short Term Techniques mantra, an oft-touted advantage of Linux is freedom from vendor lock-in.
		Vendor lock-in means by using the system your data is stored or dependant upon a proprietary format, preventing you from getting it out.
		Vendor lockin isn't when the documentation to software is in a format that's coupled with it's distribution, it's when a vendor erects a strong barrier against you switching to a competing product without starting all over.
	www.advogato.org /article/541.html (847 words)

	Vendor Lock-In
		The Vendor-Lock-In AntiPattern is acceptable when a single vendor's code makes up the majority of code needed in an application.
		Typically the Isolation Layer enables the vendor to provide a convenient language-specific interface to a lower-level technology.
		Vendor lock-in is often accepted with promises for future features that arrive later than expected, if ever.
	www.antipatterns.com /vendorlockin.htm (1544 words)

	Mark Little's Blog: When and why are interoperability fests useful?
		If you look at CORBA, it took 7 years or so for the OMG to address the shortcoming and things are still not perfect; and true heterogeneous JEE-to-JEE interoperability is a thing of the future.
		Both CORBA, JEE, DCE and (implicity) COM/DCOM, were dominated by vendors keen to maintain vendor-lockin.
		Fortunately (or unfortunately, depending on your perspective) this couldn't continue and even before the rise of Web Services we were beginning to see change: the "norm" of sites running homogeneous environments changed, with companies growing by acquisition or wanting to do real vendor-to-vendor (business-to-business) interactions.
	weblogs.java.net /blog/marklittle/archive/2006/02/when_and_why_ar_1.html (790 words)

	BEA purchases NitroX producer M7
		In this article, Jonas Bonér walks through a fairly generic but common distributed computing problem and shows how it can be simplified using clustering at the JVM level.
		The ultimate RIA solution is the one that works with an already existing framework, set of tools and team.
		The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
	www.theserverside.com /news/thread.tss?thread_id=36873 (3224 words)

	Ted Leung on the air
		Just because the JCP and the vendors are pushing the "standards" doesn't mean that we have to use them.
		Unless the multiple Smalltalk vendors are actually changing the language, then they are just competing on the tools.
		This is a lot like the source code licenses that vendors used to have in the past, except during those days, not that may people wanted access to the source, and the vendors that offered this type of license were mostly OS vendors.
	www.sauria.com /blog/2003/07/06 (1291 words)

	reddragdiva: One thing can hold us, one thing can break us. It's the same thing.
		They're not obligated to offer particular features, but I'm quite entitled to say that vendor lockin is unacceptable if they want me to use their service, put all my mail into it, be the eyeballs for their ads and so on.
		vendor lockin is unacceptable if they want me to use their service
		Your exchange policy example is not at all analogous to vendor lockin.
	reddragdiva.livejournal.com /142988.html (2863 words)

	Re: Zaurus discontinued in US -- vendor lockin or mitigating risk
		To me, the religion of it all is facinating, but I have to break it down to "mitigating risk." The discontinuation of any platform is a risk, even if the data can be extracted.
		Focus on risk, not religion, that is what keeps my, and the companies I consult for, data alive and usable.
		- Vendor lock-in is limited to Hostageware and some Commerceware The vendor lock-in is an excellent argument against Hostageware vendors (e.g., Microsoft, Autodesk, etc...), but it loses weight when you have a vendor who cares about their consumer.
	www.silug.org /lists/silug-discuss/200410/msg00084.html (861 words)

	webnetic.net: What’s really going on with Muni Wifi?
		The concept I am starting to see is that everyone realizes that the first round of WiFi transmitters won't and don’t work so well, but that the selected Vendor gets access to all the good light poles (many poles can’t...
		And by the way, two WiFi solutions unless very very carefully designed in advance will conflict, so that is still another reason why this is a monopoly in the making.
		And it gives bragging rights to a selected Vendor announcing that SF went with them - PR for all the other cities in the US - many which are following SF because of the Free WiFi Google offer.
	www.webnetic.net /2006/01/whats_really_going_on_with_mun_1.html (255 words)

	David Van Couvering 's Blog: Hello from OSCON 2005!
		His contention was that for many systems and applications, what is locks you into a vendor is the data and how it is stored in the database – the schema -- not the source code.
		You can't migrate from Vendor A to Vendor B if this migration involves reworking all your data into a new schema – you're locked in.
		This would allow open source projects and even proprietary vendors within a given domain to standardize on a single schema, delivering on the promise of flexibility and averting vendor lockin.
	weblogs.java.net /blog/davidvc/archive/2005/08/hello_from_osco.html (790 words)

	Open Source Software: Free and Open Source License Myths
		Proprietary commercial licenses, like those under which Microsoft and Oracle offer their packages, generally forbid customers from examining the source code or even decompiling executable files; users may not make copies or otherwise share the software with others; finally, users are not permitted to distribute any modifications to the licensed software.
		In other words, proprietary software vendors use licenses to maintain complete control over what goes into their software, who can use the software, who sees how it works, and who patches or improves it.
		Keeping the source code secret means the vendor might sneak in a backdoor for support or compliance checking; you've got to trust the vendor to be skillful enough to do that without exposing your systems to malicious third-parties.
	www.b-eye-network.com /view/2205?jsessionid=5750033371a735f1d2377e8caa05907c (2730 words)

	Mainframe Announcement Vendor LockIn - wMUsers
		One the biggest arguments against purchasing the traditional proprietary EAI toolsets such as webMethods, Tibco etc, is vendor lock-in.
		The argument being that the underlying enabling technology cannot be ported or used other than on the vendors own platform.
		Of course there are techniques for exposing the services in a standards based way, but the underlying technology is still proprietary.
	www.wmusers.com /forum/showthread.php?t=7445 (673 words)

	OSNews.com
		While IBM stated this week they had increased their market share over last year's, Sun also had its own press release this week claiming that it is the number one Unix platform server vendor in the world, in both revenue and unit shipments.
		So I think Mac OS X is as much UNIX as Linux, Solaris, AIX etc. since all of these OSes have their own kernel, extensions, incompabilities etc.
		Sharing good design ideas vs. vendor lockin on design differences (aka the old 'open UNIX').
	www.osnews.com /read_thread.php?news_id=11705&comment_id=24349 (633 words)

	[No title]
		The Origins of this Defect The MDA framework was initiated after the RFP for UML-2 was published, and beyond that, after the UML-2 Partners had begun their proposals.
		A Constructive Way to Rectify the Defect We call for a new RFP to be developed to begin the process of developing a new technology standard.
		The purpose will be to provide a standard to enable MDA products to work without vendor lockin.
	www.omg.org /docs/ad/02-11-18.txt (1537 words)

	GIS for Defense and Intelligence--Standards and Interoperability--Products
		This introduces an entirely new notion of openness, since data can be delivered to the client in that client's native format rather than in a compromised format that impacts performance, functionality, or both.
		Many popular CAD, GIS, and standards-based formats, such as GML, can be served directly into a client application—whether they are a different vendor's CAD, GIS package, or a thin-client browser.
		This capability is critical for defense and intelligence users who want to avoid vendor lockin and exclusionary standards.
	www.esri.com /industries/defense/business/std_interop_products.html (181 words)

	Well Bill Hilf was right
		Well, I consider when someone tells me what I can and cannot use and refuse to support their product on their own OS thats vendor lockin.
		This would keep number of versions to a minimum and allow vendor to actively support them all.
		Sat, Dec 10 2005 6:02 AM Vendors should support updates that they send to you (i.e.
	channel9.msdn.com /ShowPost.aspx?PostID=144371 (926 words)

	.NET Force :: Making Best Out Of Oracle Databases Using ODP.net - Part I (Site not responding. Last check: 2007-10-21)
		The issue of using generic oledb.net, odbc.net layers vs. vendor specific providers has always been a debate during the development of data access layers.
		While the generic code will avoid vendor lockin and improve portability it suffers in terms of performance and in using the advanced features of the particular database.
		Oracle provider for.net has many features which could be used while writing vendor specific code.
	www.dotnetforce.com /Content.aspx?t=a&n=240 (823 words)

	Hu Yoshida's Blog: Misunderstandings About Storage Virtualization (Site not responding. Last check: 2007-10-21)
		So to put it clearer, to get all the benefit of controller virtualization, you would be locked into a vendors controller until someone went through the arduous task of migrating away from it.
		From your perspective with HDS, I'm sure things are different, but from where I sit, both vendor lock-in and the narrow view of the SAN are real issues with controller-based storage virtualization.
		Our view is that the controller based approach has the least vendor lockin since, the state of LUN configuration is kept with the external storage.
	blogs.hds.com /hu/2006/04/myths_about_sto.html (2303 words)

	james strachan : Home Page (Site not responding. Last check: 2007-10-21)
		While chatting in Groovy IRC today the subject of the new Eclipse Forms came up (which looks awesome!) and the new groovy-swt library Christiaan has written for working with them easily in Groovy (which should arrive in Groovy's CVS real soon).
		So it should be really easy to add great.Net and Mono integration too (depending on the OS) which could then be the ultimate thick client for those unhappy to tie themselves to Microsoft.
		At the very least this should allow folks to minimise the MS lockin even if you're using quite a bit of.Net.
	james.weblogger.com /2004/03/11 (187 words)

	JBoss goes Closed Source!
		Ask yourself, is it possible for any open source vendor to take advantage of the hard work of the community and then make it closed source?
		If the vendor is funded by venture capital, ask for a statement directly from venture capitalists stating that they do not believe they own the intellectual property contained within the product
		For the record, I am of the firm belief that JBoss Group has extreme integrity above and beyond what is found in other open source ventures and would never think of such an act.
	blogs.ittoolbox.com /eai/leadership/archives/jboss-goes-closed-source-2033 (729 words)

	ActiveWin.com - The Most Activated Windows Resource
		If that's vendor lockin, then I love Linux.
		Vendor specific XML makes about as much sense a as vendor specific binary number system.
		JWM, not sure if you've seen Office 2k3 yet, but I remember we chatted a while back about XML support in Office and specifically in Word.
	www.activewin.com /awin/comments.asp?HeadlineIndex=16824 (516 words)

	Re: [LUG] SuSE 9.3
		Linux is based on open-standards software, and like most other open-standards applications/protocols, the inherent design properties need to be maintained across various platforms, but (de)finite implementation may differ as per vendor wishes.
		We need to be a little realistic, if all Linux vendors distribute the (fundamentally) same base systems, then why would one be better than the other?
		I think that would be anti-competitive, and go on to kill innovation.
	www.mail-archive.com /lug@linux.or.ug/msg03085.html (247 words)

	Paul Wilson's .NET Blog : What Exactly is the Point of O/R Mappers ? (Site not responding. Last check: 2007-10-21)
		I think all this additional freedom is well worth it -- as long as the O/R Mapper does not itself take away too much of your freedom by forcing you into its framework any more than necessary.
		Some “vendor lockin” is to be expected with any library, and O/R Mappers are certainly no different, but it should be as minimal as possible.
		In other words, yes you do need to realize that you are creating entities that are going to be persisted, but you shouldn't have to worry too much about the how your particular mapper accomplishes that persistence.
	weblogs.asp.net /pwilson/archive/2004/05/01/124594.aspx (1361 words)

	jGuru: EJB-JNI-Legacy Integration(C++ API) We have exisitng System in C++.We want to use Existing in the ...
		In my opinion, in-process integration is not a good option and we always recommend using MessageBeans in the EJB server and JMS C++ bindings in the external C++ process.
		Some JMS providers have proprietary C++ bindings, for all the others (or if you don't want to lock yourself into a specific JMS vendor) you can use JMS Courier.
		The first alternative might actually not be too bad if all you need to do can be wrapped up in one or two method calls.
	www.jguru.com /faq/view.jsp?EID=577956 (1088 words)

	Erwin's StarOffice Tango
		Using the fire hose coupler example, without open standards, a fire hydrant maker with a lot of money could force out smaller vendors, patent their fire hose coupler, and start making the only fire hoses that work with their fire hydrant, creating a monopoly.
		If the pattern for the fire hose coupler was freely available to anyone, it would allow competing companies to create fire hoses that would work with the hydrants, ensuring a free market.
		Second, if the bill is successful, the Minnesota CIO will be required to enforce a law requiring the use of open formats, rather than be forced to justify his or her authority to do so.
	blogs.sun.com /roller/page/dancer/Weblog/20060411?catname=/StarOffice (1198 words)

Try your search on: Qwika (all wikis)