
I'm not saying Haskell is unstable. I'm saying that the attitude expressed in the following quote is at odds with the needs of business: "And as far as something like dealing with a changing language and libraries, the mainstream already has well-established and popular techniques for doing just: agile development." Regards, John A. De Goes N-Brain, Inc. The Evolution of Collaboration http://www.n-brain.net | 877-376-2724 x 101 On Oct 2, 2009, at 9:03 AM, minh thu wrote:
2009/10/2 John A. De Goes
: On Oct 1, 2009, at 12:13 AM, Curt Sampson wrote:
And as far as something like dealing with a changing language and libraries, the mainstream already has well-established and popular techniques for doing just: agile development.
A project manager's worst nightmare:
"Sorry boss, but we're just not going to be able to meet that deadline, because, well, a language extension we were using was dropped from the language, and the syntax for some core operators was changed. Not only is our code broken, but many of the libraries we were using are broken. Don't worry, though, we're 'agile', so our unit tests will tell us when our code is working again."
Big business demands stability.
Hi,
Of course, the haskell community is that immature. People keep dropping extensions without a thought for potential problems. And the package versioning policy is just a joke written for next april fools day. Sorry for the spoiler.
Cheers, Thu