Comments on: Horses For Courses 2 (or Tools for Fools) http://blog.markturansky.com/archives/52 software architecture & engineering, code hints, sometimes philosophy, photography, life, etc. Thu, 19 Jan 2012 14:26:50 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Steve http://blog.markturansky.com/archives/52/comment-page-1#comment-1052 Steve Fri, 22 May 2009 22:56:05 +0000 http://blog.markturansky.com/archives/52#comment-1052 Gosh, for one thing there's cpubar on Solaris, and another, why doesn't your "ops center" have any automated monitoring tools, like.. hobbit/xymon at least. This is a silly, silly argument. Gosh, for one thing there’s cpubar on Solaris, and another, why doesn’t your “ops center” have any automated monitoring tools, like.. hobbit/xymon at least. This is a silly, silly argument.

]]> By: Tel http://blog.markturansky.com/archives/52/comment-page-1#comment-287 Tel Sat, 01 Mar 2008 23:43:38 +0000 http://blog.markturansky.com/archives/52#comment-287 Sun pretty much killed Solaris themselves with their license. Developers don't want to run to a lawyer every time there's a new project they might get interested in. There's so much mass of GPL code out there that every Open Source developer at least has a good understanding of what the GPL is about, even if they might use a BSD license or MPL for their own work. Sun produced their own license (a difficult one with many special caveats) and they made sure it was non-GPL compatible just to ensure that the Linux kernel didn't benefit from any Sun code. Worse, they released it in iterations under a bunch of variations of the same license. The result, is that a developer working closely with Open Solaris might be in a position where GPL-based projects will be at a legal risk to take contributions from the same developer. Sun have not rabidly hunted down minor suspected IP violations in the past, but there's always a first time. It doesn't take much to put the fear of legal pain into developers who are working on a project for their own interest and don't have corporate backing, so both Solaris and CDDL fall into the "too hard" basket after about 5 minutes research. Sun pretty much killed Solaris themselves with their license. Developers don’t want to run to a lawyer every time there’s a new project they might get interested in.

There’s so much mass of GPL code out there that every Open Source developer at least has a good understanding of what the GPL is about, even if they might use a BSD license or MPL for their own work. Sun produced their own license (a difficult one with many special caveats) and they made sure it was non-GPL compatible just to ensure that the Linux kernel didn’t benefit from any Sun code. Worse, they released it in iterations under a bunch of variations of the same license.

The result, is that a developer working closely with Open Solaris might be in a position where GPL-based projects will be at a legal risk to take contributions from the same developer. Sun have not rabidly hunted down minor suspected IP violations in the past, but there’s always a first time. It doesn’t take much to put the fear of legal pain into developers who are working on a project for their own interest and don’t have corporate backing, so both Solaris and CDDL fall into the “too hard” basket after about 5 minutes research.

]]>