Permalink
Switch branches/tags
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
13 lines (11 sloc) 7.15 KB
---
layout: post
title: Open Source, NIH and the meaning of conversation
date: '2009-08-11T10:48:00.001+01:00'
tags: [oss]
modified_time: '2009-08-11T14:29:20.906+01:00'
blogger_id: tag:blogger.com,1999:blog-4015568221071268916.post-7230417435125571759
comments: true
blogger_orig_url: http://serialseb.blogspot.com/2009/08/open-source-nih-and-meaning-of.html
---
<p><em>[Update: Nate was kind enough to link so we could enter a conversation]</em></p> <p>Yesterday, I made a certain comment on a person’s decision to release something in open-source, and they made a certain comment, and I’m very disappointed…</p> <p>I could’ve started this entry like this, without providing you quite enough information to enter the conversation yourself. This is the way Nate decided to go about it in his entry last night entitled <a href="http://kohari.org/2009/08/10/open-source-is-not-a-zero-sum-game/">Open Source is not a Zero-Sum Game</a>.</p> <p>Let’s see what happened.</p> <p>Nate - [Announcing the release of Siesta] <br />Victor - <em>@nkohari seen snooze </em><a href="http://tr.im/wamQ"><em>http://tr.im/wamQ</em></a><em> ? why the need for siesta? <br /></em>Nate - <em>@vkornov Hadn't seen it. <br /></em>Victor - <em>@nkohari you need to ask on twitter before coding your own ;) <br /></em>Nate - <em>@vkornov Eh, nothing wrong with different approaches to the same problem. <br /></em>Me <em>-@nkohari if it was a different approach or a different problem, maybe. If it does the same as other REST frameworks, it's a waste of time and resources. <br /></em>Nate - <em>@serialseb Then don't use it. Sorry to bother you. <br /></em>Me - <em>@nkohari that's not the question that was raised by Victor, but fair enough, i won't use it. Meh.</em> <br />Nate - <em>I'm really disappointed to see people complaining that I open-sourced part of my commercial product. Sorry, next time I won't try to help.</em></p> <p>So now you have the background. I won’t go and bore everyone with the countless support messages Nate received telling him to ignore the <em>whiners</em> and <em>naysayers</em>, I’ll let you decide for yourself if this was worthy of such a long rant.</p> <h4>From the system builder: don’t build it</h4> <p>Leaving aside the non-conversational aspect of Nate’s entry and twitter messages, there’s a couple of points I think are worth discussing. As I intend on having a conversation about this stuff, comments are open, you can name me in your blog and leave links to your blogs in there, I’ll add them to this entry.</p> <p>When you require infrastructure code, you should always ask yourself this question: Is it worth me building? This is the <em>Not Invented Here</em> syndrome, and unless your business model is to reinvent the wheel for IP protection reasons, it’s an expensive process, as not only do you spend your time building it, you’ll have to maintain it.</p> <p>There are two reasons why you’d want to build something. First, there is no equivalent on the market that can solve your problem in the amount of time it’ll take you to build it yourself (or slightly more as, as seen before, you’ll have to add the maintenance cost). Secondly, if the existing solution is poor and there’s no easy or cheap way to make it better.</p> <p>If you’re building stuff for any other reason than the two above, you’re generating waste, spending time building code that is not going to give you a competitive advantage or serve your product / user.</p> <p>That’s the point I tried to make in my twitter conversation. <em>If</em> it’s a different problem or <em>if</em> the solution is innovative, <em>then</em> maybe there’s nothing wrong with a different approach. <em>If</em> it’s the same, with a new brand, then it <em>is</em> a lean:waste. And there, I agree with one of Nate’s sentences: <em>rolling your own is not <strong>always </strong>waste </em>(emphasis mine).</p> <h4>From the open-source maintainer: do as you wish</h4> <p>The second part of the conversation is about open-sourcing code. I think those are two different conversations to have, as one doesn’t usually have the same waste-eliminating concerns when dealing with open-source.</p> <p>Open sourcing code is great. I love doing it, so do others. And a myriad of frameworks pop-up, thanks to open source. Just in the ReST space, you have <a href="http://www.assembla.com/spaces/snooze">Snooze</a>, <a href="https://web.archive.org/web/*/bistroframework.org">BistroMVC</a>, <a href="http://code.google.com/p/restful-aspmvc/">Restful MVC</a>, now Nate’s <a href="http://github.com/enkari/siesta/tree/master">Siesta</a>, and of course <a href="http://www.openrasta.com">OpenRasta</a>. I’m pretty sure you could achieve some of the same results with <a href="http://code.google.com/p/fubumvc/">FubuMVC</a> too.</p> <p>The question is not if multiple projects are good, they foster innovation by providing new ways to think about a problem, and new best practices start to appear. I know I am taking in a lot of ideas from all of those frameworks for future versions of OpenRasta. Competition is good.</p> <p>I do still believe in eliminating waste in open source though. Call me idealist, but I don’t see why everybody would reinvent the infrastructure stuff. Pipeline models, asp.net integration, all those frameworks share some core infrastructure aspects. Why do we all reinvent the same problem over and over? Because we’ve not been collaborating to ensure we have communication in place.</p> <p>That’s why I told Chad Myers many times: It’s great to see another frameworks with really good ideas, it’s a shame we’re duplicating effort endlessly on parts that are not bringing much innovation or value.</p> <p>But I suppose that’s the state of things. The bazaar model requires that we’ll all come up and only the solution with the most market leverage will survive. Yes, we’ll have 250 ReST frameworks in a year time. And in two years, only two or three will probably see any usage at all. In the meantime, we’ll have wasted hundreds of hours of developers time.</p> <p>Maybe the innovation will be worth it, but I’m still unsure if we’ll ever reach even.</p> <h4>Final words</h4> <p>So there you go, here’s the core of the question. Fragmentation doesn’t always lead to innovation, collaboration and discussion can prevent people going in a direction where they don’t innovate but just recreate it their way <em>because it’s only 5 or 6 hours</em>. Allegedly, Nate’s solution is simple and small enough that he’s probably not affected by this.</p> <p>I don’t however believe that ignorance is a good reason to discard frameworks like snooze (which, by the way, is the one that was mentioned in the conversation, and the work of the ever excellent Andrew Davey).</p> <p>As a final word, I’d like to remind everyone that one of the constraints of ReST is hypermedia. If you design APIs without any links, and advertise how to build URIs, you’re not doing ReST, your <a href="http://serialseb.blogspot.com/2009/06/fighting-for-rest-or-tale-of-ice-cream.html">doing something else</a>. It doesn’t mean you’re doing something badly, just that you’re not actually doing ReST.</p>