Sandia Releases DAKOTA Toolkit under GPL 131
Consul writes " DAKOTA, a powerful toolkit for doing engineering analysis, has now been released under the GPL. Space Daily has the details about the tookkit."
"Gravitation cannot be held responsible for people falling in love." -- Albert Einstein
Groovy, baby (Score:3, Insightful)
Can this be exported? (Score:4, Insightful)
....not quite under the GPL? (Score:2, Insightful)
Isn't that contrary to the terms of the GPL? As long as the source is provided, and the resultant code is released under the GPL, isn't modification and resale legal? Just something that caught my eye in the article.
your tax dollars at work (Score:2, Insightful)
Re:Isn't GPL a step *backward*? (Score:4, Insightful)
Re:Addendum to the article post (Score:3, Insightful)
Note the use of the terms "utilizes" and "optional" in the snippage from the DAKOTA website below. I interpret this to mean that they offer optional features (the non-linear kind) that DAKOTA will use if available, but is not a requirement.
****snippage below********
DAKOTA utilizes the following external optimization libraries:
* DOT (nonlinear programming algorithms from Vanderplaats Research and Development; optional extension requiring a separate commercial license)
* NPSOL (nonlinear programming algorithms from Stanford Business Software; optional extension requiring a separate commercial license)
* CONMIN (public domain nonlinear programming algorithms; no license required for inclusion in DAKOTA distribution)
GPL is a good choice (Score:4, Insightful)
Re:GPL is a good choice (Score:3, Insightful)
Why can't they use that research code in proprietary work? The original is still there. And the original can still be improved if need be. Any duplication of work would just be
The public work may actually reduce the cost of the proprietary product since the company can only charge for the value that they add. Any educated consumer can way the pros and cons of using the public version or the proprietary version.
Maybe even, the product has nothing to do with engineering but the algorithms and/or code works in a completely different domain -- with some tinkering. So now the company must either grow their own solution or give away their jewels. Even though their tax dollars have paid for a solution that is there today.
Re:Isn't GPL a step *backward*? (Score:3, Insightful)
In 1989 I worked for Inference. Inference sold a well regarded LISP based expert system shell (ART). It cost a lot of money and ran on very expensive workstations. NASA came along and cloned it with a C application (CLIPS) that was released into the public domain (if I recall correctly.). In many ways, CLIPS was the death of ART, and various competitors came along that incorporated CLIPS and competed in sales against ART. So in similar ways, NASA and taxpayer dollars killed off the main product of the privately held company that developed the initial technology.
Was it "fair" for NASA to clone ART in that manner? I dunno. It wasn't kind to our paychecks, but that may be irrelevant.
If CLIPS has been released with a GPL, I think both taxpayer and Inference's private investors would have been served. Inference would not have to worry about competitors being given taxpayer software that allowed them to so quickly catch up with our efforts, and the taxpayers would have been able to benefit by having the code released in a way that brought the high tech ART into schools, research institutes, and to anyone willing to comply with the GPL.
why was this modded as flamebait? (Score:3, Insightful)
So tell me how that was flamebait so I can better post in the future.
Re:Groovy, baby (Score:2, Insightful)