On Thu, May 17, 2012 at 12:26 AM, Fabrizio Giudici < fabrizio.giud...@tidalwave.it> wrote:
> It's not open source. >> >> > So, why not releasing it to the open source? I can only speculate, but I can think of plenty of reasons, starting with 1) turning a closed source project into open source requires a lot (a lot!) more efforts than people think, 2) it would also mean exposing the API that the application uses, which means more support and 3) what does Google have to gain from such a move? (nothing) Contrary to what a lot of people think, open sourcing proprietary projects is not just difficult, it's expensive and creates a significant drag on the organization in charge of the effort (at least) and most likely, the entire company. More often than not, open sourcing is the *wrong* thing to do for a corporation. -- Cédric -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
