"The economists Richard Lester and Michael Piore have studied the firms that sought to create the switching technology, finding that cooperation and collaboration within certain companies allowed them to make headway on the switching technology problem, whereas internal competition at other corporations diminished engineers’ efforts to improve the quality of the switches. Motorola, a success story, developed what it called a 'technology shelf,' created by a small group of engineers, on which were placed possible technical solutions that other teams might use in the future; rather than trying to solve the problem outright, it developed tools whose immediate value was not clear. Nokia grappled with the problem in another collaborative way, creating an open-ended conversation among its engineers in which salespeople and designers were often included. The boundaries among business units in Nokia were deliberately ambiguous, because more than technical information was needed to get a feeling for the problem; lateral thinking was required. Lester and Piore describe the process of communication this entailed as 'fluid, context-dependent, undetermined.'
By contrast, companies like Ericsson proceeded with more seeming clarity and discipline, dividing the problem into its parts. The birth of the new switch was intended to occur through 'the exchange of information' among offices 'rather than the cultivation of an interpretative community.' Rigidly organized, Ericsson fell away. It did eventually solve the switching technology problem, but with greater difficulty; different offices protected their turf. In any organization, individuals or teams that compete and are rewarded for doing better than others will hoard information. In technology firms, hoarding information particularly disables good work.
The corporations that succeeded through cooperation shared with the Linux community that experimental mark of technological craftsmanship, the intimate, fluid join between problem solving and problem finding. Within the framework of competition, by contrast, clear standards of achievement and closure are needed to measure performance and to dole out rewards.
 Richard K. Lester and Michael J. Piore, Innovation, the Missing Dimension (Cambridge, Mass.: Harvard University Press, 2004), 98.
 Ibid., 104."
(Richard Sennett, 2008, pp.32-33)
1). Sennett, R. (2008). "The Craftsman". New Haven & London, Yale University Press.
"Thomson [Thomson Reuters] makes the proprietary bibliography software EndNote, and claims that Zotero is causing its commercial business 'irreparable harm' and is wilfully and intentionally destroying Thomson's customer base. In particular, Thomson is demanding that GMU stop distributing the newer beta-version of Zotero that allegedly allows EndNote's proprietary data format for storing journal citation styles to be converted into an open-standard format readable by Zotero and other software. Thomson claims that Zotero 'reverse engineered or decompiled' not only the format, but also the EndNote software itself. ...
Litigation, which may go to a jury trial, is pending, so judging this case on its legal merits would be premature. But on a more general level, the virtues of interoperability and easy data-sharing among researchers are worth restating. Imagine if Microsoft Word or Excel files could be opened and saved only in these proprietary formats, for example. It would be impossible for OpenOffice and other such software to read and save these files using open standards - as they can legally do.
Competition between open-source and proprietary software is long-running, as personified by the struggle between Windows and Linux for desktop and server operating systems, but also in many branches of software used by scientists. Researchers tend to lean towards open sharing, but they will also pay for added-value features, and it's important that the playing field is level. Ultimately, the customer is king."
Nature Volume 455, p.708 (9 October 2008) | doi:10.1038/455708a; Published online 8 October 2008, Nature Publishing Group, a division of Macmillan Publishers Limited.
"I take representing digital culture in film very seriously in lieu of having grown up in a world of very badly researched user interface greeble. I cringed during the part in Hackers (1995) when a screen saver with extruded 'equations' is used to signify that the hacker has reached some sort of neural flow or ambiguous destination. I cringed for Swordfish and Jurassic Park as well. I cheered when Trinity in The Matrix used nmap and ssh (and so did you). Then I cringed again when I saw that inevitably, Hollywood had decided that nmap was the thing to use for all its hacker scenes (see Bourne Ultimatum, Die Hard 4, Girl with Dragon Tattoo, The Listening, 13: Game of Death, Battle Royale, Broken Saints, and on and on). In Tron, the hacker was not supposed to be snooping around on a network; he was supposed to kill a process. So we went with posix kill and also had him pipe ps into grep. I also ended up using emacs eshell to make the terminal more l33t. The team was delighted to see my emacs performance -- splitting the editor into nested panes and running different modes. I was tickled that I got emacs into a block buster movie. I actually do use emacs irl, and although I do not subscribe to alt.religion.emacs, I think that's all incredibly relevant to the world of Tron."
(Joshua T. Nimoy)
"Scribus is an Open Source program that brings professional page layout to Linux/UNIX, Mac OS X, OS/2 Warp 4/eComStation and Windows desktops with a combination of press-ready output and new approaches to page design."
"Openframeworks is a c++ library designed to assist the creative process by providing a simple and intuitive framework for experimentation.
The library is designed to work as a general purpose glue, and wraps together several commonly used libraries under a tidy interface: openGL for graphics, rtAudio for audio input and output, freeType for fonts,freeImage for image input and output, quicktime for video playing and sequence grabbing.
The code is written to be both cross platform (PC, Mac, Linux, iPhone) and cross compiler. The API is designed to be minimal and easy to grasp. There are very few classes, and inside of those classes, there are very few functions. The code has been implemented so that within the classes there are minimal cross-referening, making it quite easy to rip out and reuse, if you need, or to extend.
Simply put, openFrameworks is a tool that makes it much easier to make things via code. We find it super useful, and we hope you do too.
OpenFrameworks is actively developed by Zach Lieberman, Theodore Watson, and Arturo Castro, with help from the OF community. ofxIphone, is actively developed by Mehmet Akten and Zach Gage, with development help from Lee Byron and Damian Stewart. The OF website is designed and maintained by Chris O'shea.
OpenFrameworks is indebted to two significant precursors: the Processing development environment, created by Casey Reas, Ben Fry and the Processing community; and the ACU Toolkit, a privately distributed C++ library developed by Ben Fry and others in the MIT Media Lab's Aesthetics and Computation Group."