News for hackers. Stuff that matters.

A comment on Haskell in the Datacentre. Parent comment

Re:Haskell in the Datacentre by lmm on Wednesday December 14, 2016 @07:50AM (#13175577)
> Because it's already there and it already works just fine.

Well clearly it didn't work just fine if its threading model was interacting poorly with that of their Haskell code. If there's a mismatch between those two components then that will continue to bite them in the future, and it's legitimate to ask whether moving the boundary would be a better way to solve the problem.

[ Parent | on HN ]
Re:Haskell in the Datacentre by mattnewton on Wednesday December 14, 2016 @09:20AM (#13176083)
There is an old saying: "We did what we did, not because it was easy; But because we thought it was going to be easy"

When they realized the bug the path forward probably seemed like patching and not a Haskell re-write, and that's a reasonable mistake to make.

[ Parent | on HN ]
Re:Haskell in the Datacentre by easytiger on Wednesday December 14, 2016 @08:47AM (#13175878)
your right, makes more sense to have both in c++
[ Parent | on HN ]
Re:Haskell in the Datacentre by massudaw on Wednesday December 14, 2016 @08:57AM (#13175929)
That was the last tried solution, didn't work out well. And what is holding is nothing haskell specific. Is just wasting effort re implementing good broad used code at Facebook.
[ Parent | on HN ]