Jump to ContentJump to Main Navigation
The Comingled CodeOpen Source and Economic Development$
Users without a subscription are not able to see the full content.
The Comingled Code: Open Source and Economic Development

Josh Lerner and Mark Schankerman

Print publication date: 2010

Print ISBN-13: 9780262014632

Published to MIT Press Scholarship Online: August 2013

DOI: 10.7551/mitpress/9780262014632.001.0001

Show Summary Details
Page of

PRINTED FROM MIT PRESS SCHOLARSHIP ONLINE (www.mitpress.universitypressscholarship.com). (c) Copyright The MIT Press, 2021. All Rights Reserved. An individual user may print out a PDF of a single chapter of a monograph in MITSO for personal use.date: 24 July 2021

The Demand Side: Assessing Trade-offs and Making Choices

The Demand Side: Assessing Trade-offs and Making Choices

Chapter:
(p.103) 5 The Demand Side: Assessing Trade-offs and Making Choices
Source:
The Comingled Code
Author(s):

Josh Lerner

Mark Schankerman

Publisher:
The MIT Press
DOI:10.7551/mitpress/9780262014632.003.0005

This chapter examines how users of open source software make the decision between open code and proprietary software. It provides insights into the structure of demand for software and how it relates to the characteristics of users and their perceptions about various costs associated with adopting particular software. The analysis reveals that open source and proprietary software are often comingled and that firms that market proprietary code are also likely to contribute to or sell open source code as product.

Keywords:   open source software, software users, demand for software, proprietary software, characteristics of users

MIT Press Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.