Comments on: A Tale of Two Companies http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/ Socio-Economical Articles about the Second Life® world Sat, 13 Mar 2010 19:52:33 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ashcroft Burnham http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/comment-page-1/#comment-11865 Ashcroft Burnham Fri, 04 Jan 2008 22:44:31 +0000 http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/#comment-11865 That "worse is better" paper is appallingly misconceived. That “worse is better” paper is appallingly misconceived.

]]> By: Hiro Pendragon http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/comment-page-1/#comment-11857 Hiro Pendragon Fri, 04 Jan 2008 17:23:25 +0000 http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/#comment-11857 Dreamhost gave us crappy service, it was down far too frequently, and so we went to MediaTemple. :) Dreamhost gave us crappy service, it was down far too frequently, and so we went to MediaTemple. :)

]]> By: Melissa Yeuxdoux http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/comment-page-1/#comment-11820 Melissa Yeuxdoux Thu, 03 Jan 2008 17:58:15 +0000 http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/#comment-11820 I think Mr. Jones retraced the path taken by Richard Gabriel in his <a href="http://www.jwz.org/doc/worse-is-better.html" rel="nofollow">"Worse is Better" paper</a>. I think Mr. Jones retraced the path taken by Richard Gabriel in his “Worse is Better” paper.

]]> By: Ashcroft Burnham http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/comment-page-1/#comment-11776 Ashcroft Burnham Wed, 02 Jan 2008 21:38:48 +0000 http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/#comment-11776 Goodness, I didn't know that Cory had left. Of course, the other approach is to make one's own protocol/application set, but do it very thoroughly internally, carefully commenting all the code fully, then documenting it properly, *then*, once the application is popular enough and the code refined enough, open-source it. There's no reason why closed should equate to quick and dirty. Goodness, I didn’t know that Cory had left. Of course, the other approach is to make one’s own protocol/application set, but do it very thoroughly internally, carefully commenting all the code fully, then documenting it properly, *then*, once the application is popular enough and the code refined enough, open-source it. There’s no reason why closed should equate to quick and dirty.

]]> By: Gwyneth Llewelyn http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/comment-page-1/#comment-11769 Gwyneth Llewelyn Wed, 02 Jan 2008 18:36:54 +0000 http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/#comment-11769 Oh, I was mostly thinking of "OpenSim" as a very wide and far-reaching 'word' that encompasses a lot of different and separate technologies... which would indeed allow different teams to work on each of those in parallel. Oh, I was mostly thinking of “OpenSim” as a very wide and far-reaching ‘word’ that encompasses a lot of different and separate technologies… which would indeed allow different teams to work on each of those in parallel.

]]> By: http://silpol.livejournal.com/ http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/comment-page-1/#comment-11766 http://silpol.livejournal.com/ Wed, 02 Jan 2008 16:55:18 +0000 http://gwynethllewelyn.net/2008/01/01/a-tale-of-two-companies/#comment-11766 quote <i>it really depends on how many more people the project can attract</i> back to first edition of "mythical man-month", how many more pregnant women one need to add in order to achieve labor earlier? ;) quote it really depends on how many more people the project can attract

back to first edition of “mythical man-month”, how many more pregnant women one need to add in order to achieve labor earlier? ;)

]]>