Thursday, June 18, 2009
We're talking about two orthogonal things here. One is open-source versus closed-source, and the other is whether we charge money for software licenses or not. As Mike points out, the former is about development methodology. The latter is about business model.
There ought to be nothing wrong with charging money for open-source software. In fact, there isn't -- even the GPL permits this. This is related to the origin of open-source in the Free Software movement. "Free software" to them is about what the user is licensed to do with that software, not whether they paid anything to license it. In fact, some companies package free software and charge for it (presumably with some added value).
The marketing interpretation of "free software" is the "free chips & salsa" concept Mike mentions. It's a way of encouraging the market to adopt this product. It's a loss leader, usually followed by upselling the customer with other products or services.
There's also a case for no-charge versions of closed-source software. Typically these have either limited features ("crippleware") or they expire after a limited time (e.g. "demo").
Few companies have found a way to use open source methods to develop full products they then charge money for. But this could simply be because it's hard to drive adoption of any software product, regardless of whether it's open-source or closed-source.
On the issue of hybrid licensing, I see this as no hypocrisy; I see it as more freedom. If I develop some code, offer it under the GPL license, and you use my code as part of your project, then you are obligated to license your project with a GPL-compatible license. This is termed the "viral" nature of the GPL license, and it's clearly intended to promote the free software movement.
What if you don't want to adopt a GPL-compatible license for your project? Well, no one is forcing you to use my code. But my code is really amazingly good, and you want it. You want it so much that you're willing to give me money if I grant you a license to use it under different terms. If I'm willing to do that, now you have more freedom -- you can choose to contribute your own code to the body of free software in the world, or you can choose not to. But the latter choice may have a different price tag associated with it.
This should still promote the principles of the free software movement. It would be wrong to charge someone for their freedom. But in the hybrid license model, you can avoid paying for a license simply by joining the movement, by spreading the freedom. If you want to stick to your closed-source model, you can pay for the privilege of using my code in that way.
I don't see any hypocrisy in a software maker using a hybrid licensing model, as long as they are consistent and honest about it.
Thursday, June 04, 2009
Early Registration has been extended to June 23. Save up to $250!
Enter my friends-of-speaker discount code "os09fos" when you register, and save an additional 20%! Just because you read my blog.
SQL is from Mars, Objects are from Venus.This talk is for software developers who know SQL but are stuck trying to implement common object-oriented structures in an SQL database. Mimicking polymorphism, extensibility, and hierarchical data in the relational database paradigm can be confusing and awkward, but they don't have to be.
- Polymorphism: Suppose your blog supports comments, but then your comments need to reference multiple types of content, for example news, blog articles, and videos. What then?
- Extensibility: We’ve all designed customizable software, allowing customers to extend a data model with new data attributes. See how to design flexible systems, while using efficient SQL queries.
- Hierarchies: Tree-structured data relationships are common, but working with trees in SQL usually implies recursive queries. There are a few solutions to solve this more cleanly.
- ActiveRecord Dos and Don'ts: Web development frameworks have popularized the use of design patterns, but when it comes to multi-table queries, complex views, and assignment of OO responsibilities, ActiveRecord falls short as a one-size-fits-all Domain Model.
Gather with published and upcoming authors of programming books from the industry favorite publisher, Pragmatic Bookshelf. Join this informal chat about programming, writing books, job hunting, and career development.Agenda:
- Author introductions, books, OSCON presentations.
- Experiences working with a publisher.
- How does authoring a book aid a tech career?
- What tech books would you like to see?
Pragmatic Bookshelf authors attending OSCON include:
- Ian Dees is presenting “Testing iPhone Apps with Ruby and Cucumber” at OSCON (Wednesday 10:45am). Ian authored the book “Scripted GUI Testing with Ruby.”
- Bill Karwin is presenting “Practical Object-Oriented Models in SQL” at OSCON (Wednesday 5:20pm). Bill is currently writing a book “SQL Antipatterns.”
- Other Prag authors are attending OSCON, and plan to be at this BoF.