Comments on: Open vs Closed http://blog.figuringshitout.com/open-vs-closed/ Ideas, thoughts and my attempts to figure shit out Mon, 06 Feb 2012 14:30:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: cheap uggs outlet http://blog.figuringshitout.com/open-vs-closed/comment-page-1/#comment-9620 cheap uggs outlet Fri, 21 Oct 2011 09:57:00 +0000 http://blog.bumblebeelabs.com/?p=534#comment-9620 Thanks for your opinion. <a href="http://www.cheapuggsoutletau.com/" title="cheap uggs " rel="nofollow">cheap uggs</a> I totally like with it.I like <a href="http://www.cheapuggsoutletau.com/" title="cheap uggs outlet" rel="nofollow">cheap ugg outlet</a> as well and someone is looking for <a href="http://www.cheapuggsoutletau.com/" title="ugg boots outlet" rel="nofollow">ugg boots outlet</a> People usually prefer <a href="http://www.cheapuggsoutletau.com/" title="ugg boots sale" rel="nofollow">ugg boots sale</a> Thanks for your opinion. cheap uggs I totally like with it.I like cheap ugg outlet as well and someone is looking for ugg boots outlet People usually prefer ugg boots sale

]]> By: Chris Messina http://blog.figuringshitout.com/open-vs-closed/comment-page-1/#comment-3731 Chris Messina Thu, 23 Apr 2009 04:30:51 +0000 http://blog.bumblebeelabs.com/?p=534#comment-3731 This is certainly something that I'm personally sensitive to, and think that it'll take something of a generational shift to get towards better-design open platforms. One of the things that "open" tends towards is the "middle", since, in order to get more people to contribute, you've got to make political compromises in order to gain a wider following. Oftentimes this means adding more and more features rather than cutting (or, in writing terms, "editing"). I think a balance between app- and plugin-based platforms is necessary, so you need to find that sweet spot between meeting the baseline needs of a wide audience (motivating developers to want to build on your platform) and providing enough surface areas for devs to hook into that they can build satisfying extensions (see Firefox, Ubiquity and/or Adium). That said, design succeeds where there is a vision that is checked against a broad reality. I think Apple is succeeding here, and happens to provide a built-in income model as well (whereas the Mozilla community does not). Worth considering, for sure. This is certainly something that I’m personally sensitive to, and think that it’ll take something of a generational shift to get towards better-design open platforms. One of the things that “open” tends towards is the “middle”, since, in order to get more people to contribute, you’ve got to make political compromises in order to gain a wider following.

Oftentimes this means adding more and more features rather than cutting (or, in writing terms, “editing”). I think a balance between app- and plugin-based platforms is necessary, so you need to find that sweet spot between meeting the baseline needs of a wide audience (motivating developers to want to build on your platform) and providing enough surface areas for devs to hook into that they can build satisfying extensions (see Firefox, Ubiquity and/or Adium).

That said, design succeeds where there is a vision that is checked against a broad reality. I think Apple is succeeding here, and happens to provide a built-in income model as well (whereas the Mozilla community does not).

Worth considering, for sure.

]]> By: Chris Messina http://blog.figuringshitout.com/open-vs-closed/comment-page-1/#comment-9118 Chris Messina Thu, 23 Apr 2009 04:30:00 +0000 http://blog.bumblebeelabs.com/?p=534#comment-9118 This is certainly something that I'm personally sensitive to, and think that it'll take something of a generational shift to get towards better-design open platforms. One of the things that "open" tends towards is the "middle", since, in order to get more people to contribute, you've got to make political compromises in order to gain a wider following. Oftentimes this means adding more and more features rather than cutting (or, in writing terms, "editing"). I think a balance between app- and plugin-based platforms is necessary, so you need to find that sweet spot between meeting the baseline needs of a wide audience (motivating developers to want to build on your platform) and providing enough surface areas for devs to hook into that they can build satisfying extensions (see Firefox, Ubiquity and/or Adium). That said, design succeeds where there is a vision that is checked against a broad reality. I think Apple is succeeding here, and happens to provide a built-in income model as well (whereas the Mozilla community does not). Worth considering, for sure. This is certainly something that I’m personally sensitive to, and think that it’ll take something of a generational shift to get towards better-design open platforms. One of the things that “open” tends towards is the “middle”, since, in order to get more people to contribute, you’ve got to make political compromises in order to gain a wider following.

Oftentimes this means adding more and more features rather than cutting (or, in writing terms, “editing”). I think a balance between app- and plugin-based platforms is necessary, so you need to find that sweet spot between meeting the baseline needs of a wide audience (motivating developers to want to build on your platform) and providing enough surface areas for devs to hook into that they can build satisfying extensions (see Firefox, Ubiquity and/or Adium).

That said, design succeeds where there is a vision that is checked against a broad reality. I think Apple is succeeding here, and happens to provide a built-in income model as well (whereas the Mozilla community does not).

Worth considering, for sure.

]]>