http://www.codexon.com/posts/why-arent-functional-languages-...
Short version: Haskell is harder than C while being slower and uses more memory. The main implementation GHC, comes with GPL concerns.
http://www.codexon.com/posts/why-arent-functional-languages-...
Short version: Haskell is harder than C while being slower and uses more memory. The main implementation GHC, comes with GPL concerns.
And as pointed out at the time, commercial users already funded the -dynamic flag, along with the ability to swap out libgmp.
So that's FUD. As was pointed out in this forum at the time: http://news.ycombinator.com/item?id=847120
These days you can just run "cabal license-check" (IIRC) which will type check all the libraries you use for compliance.
Have a nice day.
You and your supporters succeeded in bombarding every article that even mentions Haskell the wrong way with snide comments, and probably won over a few hobbyists. At the end of the day though, the managers making the decisions will not think "Don Stewart said so, it must be true". They will find the same conclusions that Jon Harrop, myself, and other people you have ostracized have found. And this will continue until it even if you succeed in suppressing all negative feedback on Haskell.
Have a nice day.
"Don Stewart said so, it must be true" actually isn't such a bad heuristic (as far as Haskell is concerned). From what I've seen, Don is quite cautious.
This is not surprising coming from someone involved with Haskell. Do I really need to point to you the bug ticket that it was only 8 months ago that you could use something other than GMP? http://hackage.haskell.org/trac/ghc/ticket/601
Even with the option to dynamically link, it still doesn't change the fact that it was the __default__. And what a scary default that was. Company lawyers don't like to touch anything related to GPL with a 10-foot pole, for the reason that it is really up to the jury to decide what is a "derivative work" even if you only link dynamically! Maybe if you live in France, or have a 5 person company, this is an acceptable state.
Anyway I am done, you and Dons win, are you happy? I simply have no ulterior motive or incentive to defend my findings against organized groups who have their livelihoods and PhDs based on Haskell.
Now it's a pity that companies are scared of the GPL. As far as I know, most software is custom or private, is never released[1], and thus can't possibly infringe the GPL.
I think the real problem here is corporate culture. No company would object using the glibc in a proprietary program. So why would they be scared of any other LGPL library? When they don't even release the software? That's plainly irrational.
Now our choice is hard, but simple: get rid of the "GPL == we can't use it" line of thinking, or get rid of restrictive licences.
[1]: Many custom software actually belong to the company that wrote it, rather than to the company (or government) that purchased it. In this case GPL infringement could happen. But really, I can't fathom why some customers still don't demand complete ownership (including source code) for their custom software. That strikes me as either wildly misinformed or incredibly silly.
You aren't really an outsider considering your participation in the Haskell Cafe mailing list and being credited in Real World Haskell.
And companies do object to using glibc in a proprietary program obviously. You are probably thinking of the GCC runtime which has an explicit exception for commercial programs that prevents them from turning GPL.
http://www.gnu.org/licenses/gcc-exception.html
You also don't have any proof that most software is custom or private. Even if it is the majority, you cannot deny that the shrink-wrap industry is huge, especially during most of Haskell's existence. The answer is to avoid GPL code in the language which is what I was saying the whole time. You don't put the foundation of your business at risk just so you can use a cool new language.
Interestingly, I saw it happen almost everywhere. It looks like people are more likely to down-vote comments which are contradicted by a recognized authority. This is of course not a good thing.
> You aren't really an outsider considering your participation in the Haskell Cafe mailing list and being credited in Real World Haskell.
I didn't post more than a few messages, 2 years ago, and I posted about 3 minor comments in Real World Haskell. I've read a few papers, but seldom have written anything (except http://www.loup-vaillant.fr/articles/assignment of course). I'm not an outsider, but hardly what I consider to be an Insider.
> You also don't have any proof that most software is custom or private.
I don't. But in this (huge) niche, my point still stand: being afraid of the GPL is silly. Corporations that are should stop being.
> you cannot deny that the shrink-wrap industry is huge
I cannot and I won't.
> The answer is to avoid GPL code in the language […]
Yes, assuming you want the (proprietary) shrink-wrap industry to use Haskell. I want it gone. Therefore, I see the GPL as the solution.
That you cannot see this is because you also have the same bias as Dons.
Haskell may not be the perfect language for your generic FFT library to be distributed with your OS, but it's a great choice for building applications that would otherwise be C++ or Java. Java and C++ had no trouble catching on, despite being slower than C, and Haskell isn't even that much slower than C.
Haskell code that performs close (within an order of magnitude in terms of run time and space) to its C/C++ equivalent typically is also close in code length (and often less readable!) and often unsafe as well (requires explicit unboxing etc.)