Hacker News new | ask | show | jobs
by atopuzov 2428 days ago
Speaks more about the quality of the management/leadership then haskell itself.
2 comments

It speaks to what may happen when the orginal haskell developers leave. Highly likely it will be rewritten.
I mean, when your whole core development team leaves, you have bigger problems than programming language choice.
Exactly. The value is in the mental model the development team has accrued through working on the code, not the code itself.[1][2] If you lose the code but retain the development team then the code can be rewritten. Lose the team but keep the code, as in this case, and you're left with a bunch of software that no one really understands how to maintain, much less improve on, without working at cross-purposes to the original design. For a new team to develop the same degree of experience and familiarity with the codebase as the original team is only marginally less work than reimplementing it from scratch. At that point the language it's written is the least of your issues.

[1] http://pages.cs.wisc.edu/~remzi/Naur.pdf [2] https://news.ycombinator.com/item?id=10833278

No doubt. Just wanted to share my experience, and the potential risks of starting a large project (or acquiring one) in a language most 'coders' aren't familiar with :o
There are potential risks, but didn't Paul Graham argue (about Lisp) that some of these less familiar languages can be your "special weapon"?
It's a deathblow to a large project to simultaneously lose all developers regardless of what language its written in.
I wouldn't want to have most 'coders' on a project like this anyway...