4 ms·

I'm really excited about this. If facebook is able to use it in production, then Haskell is no longer an academic language. I would tell my boss that we can use

by co_dh 11y ago

I'm really excited about this. If facebook is able to use it in production, then Haskell is no longer an academic language. I would tell my boss that we can use Haskell because facebook is using it:) BTW, the stackage project have resolved a big problem (Cabel hell) in Haskell ecosystem, and I start to use haskell again.

boothead 11y ago
If you need anyone to back you up, I would be happy to share my experience building a team of Haskellers, putting it into production at a start up and how Haskell scales to a large enterprise.
- kornish 11y ago
  (not the parent commenter, but..) That would be great - do you have any writing about your experience anywhere? Someone a few days ago made a comment that Haskell posts on HN frequently get many upvotes but fewer comments, and that this symptom is indicative of lots of people who are following the language but haven't had a chance to dive in. I think hearing more success stories about putting it into prod would go a long way towards allaying fears from earlier days. Seems like the HN community would benefit from hearing your story.
  - elcapitan 11y ago
    +1
  - boothead 11y ago
    I have a write up about the start up stuff here: https://www.fpcomplete.com/business/blog/utilizing-haskell-fynder/ https://www.fpcomplete.com/business/blog/utilizing-haskell-f... There's also a more in depth version on the commercial haskell mailing list (I can't find it from work I'm afraid). Feel free to fire any more questions at me :-)
  - boothead 11y ago
    Here's the other link I mentioned: https://groups.google.com/forum/#!searchin/commercialhaskell/fynder/commercialhaskell/GBn9rpcZZbw/xJ2nIW1efJQJ https://groups.google.com/forum/#!searchin/commercialhaskell...
- carterschonwald 11y ago
  and likewise I'm part of a team thats got Haskell code in production at a fortune 20(ish) company. And we've been slowly growing a positive reputation within the firm for repeatedly building and delivering some pretty ambitious projects too! :)
deleted 11y ago
[deleted]
KirinDave 11y ago
Facebook using Haskell, or any language, does not make it less "academic" or more "production quality." Ultimately, we can use lots of different languages in different roles. People have been shipping Haskell code in production for years. The runtime and compiler have been up to snuff for some time, and honestly the build tools were not in any worse of a place than Go's are right now. The decision if something is production-ready for your shop is a matter of your personal (and/or organizational) commitment to that technical platform. You do not need the blessing of a big company to use a tool. Perpetuating this idea only makes it harder for people to try new tools. And so long as Haskell continues to be flexible and easy to extend, it'll still be useful to academia (hence the 100+ language extensions still available).
- kornish 11y ago
  I agree that the line of reasoning in the parent comment is flawed ("if Facebook is using it, then we can use it too") and that making a language decision is very much about picking the right tool for the job. However, I think the comment touches on a truth: public perception matters in language decisions. A tool which is perceived to only be useful to academics and tinkerers often times won't make it onto the short list, even when it merits being there. Seeing that Facebook can use this tool effectively at scale might mitigate the early adoption risk that many feel, and let them concentrate on evaluating Haskell for how it fits the problem. Without the validation of seeing it used for large, real-world systems, it might never make it that far.
- ori_b 11y ago
  Strongly agree -- I'm on a team at Facebook that has D code in production. There is a lot of investment that we'd have to do to make it what I'd call solidly production quality. At one point, I found myself writing a heap profiler, since the tools available where inadequate. If your company doesn't have the ability or will to fix issues deep within the runtime of the shiny new system you're using, I'd be cautious about using a shiny new tool in production. I'm not necessarily saying "Don't do it", but you do need to think long and hard about how you'd handle a tricky bug in your tool.
  - 11y ago

by co_dh 11y ago

boothead 11y ago

If you need anyone to back you up, I would be happy to share my experience building a team of Haskellers, putting it into production at a start up and how Haskell scales to a large enterprise.

kornish 11y ago
(not the parent commenter, but..) That would be great - do you have any writing about your experience anywhere? Someone a few days ago made a comment that Haskell posts on HN frequently get many upvotes but fewer comments, and that this symptom is indicative of lots of people who are following the language but haven't had a chance to dive in. I think hearing more success stories about putting it into prod would go a long way towards allaying fears from earlier days. Seems like the HN community would benefit from hearing your story.
- elcapitan 11y ago
  +1
- boothead 11y ago
  I have a write up about the start up stuff here: https://www.fpcomplete.com/business/blog/utilizing-haskell-fynder/ https://www.fpcomplete.com/business/blog/utilizing-haskell-f... There's also a more in depth version on the commercial haskell mailing list (I can't find it from work I'm afraid). Feel free to fire any more questions at me :-)
- boothead 11y ago
  Here's the other link I mentioned: https://groups.google.com/forum/#!searchin/commercialhaskell/fynder/commercialhaskell/GBn9rpcZZbw/xJ2nIW1efJQJ https://groups.google.com/forum/#!searchin/commercialhaskell...
carterschonwald 11y ago
and likewise I'm part of a team thats got Haskell code in production at a fortune 20(ish) company. And we've been slowly growing a positive reputation within the firm for repeatedly building and delivering some pretty ambitious projects too! :)

deleted 11y ago

[deleted]

KirinDave 11y ago

Facebook using Haskell, or any language, does not make it less "academic" or more "production quality." Ultimately, we can use lots of different languages in different roles. People have been shipping Haskell code in production for years. The runtime and compiler have been up to snuff for some time, and honestly the build tools were not in any worse of a place than Go's are right now. The decision if something is production-ready for your shop is a matter of your personal (and/or organizational) commitment to that technical platform. You do not need the blessing of a big company to use a tool. Perpetuating this idea only makes it harder for people to try new tools. And so long as Haskell continues to be flexible and easy to extend, it'll still be useful to academia (hence the 100+ language extensions still available).

kornish 11y ago
I agree that the line of reasoning in the parent comment is flawed ("if Facebook is using it, then we can use it too") and that making a language decision is very much about picking the right tool for the job. However, I think the comment touches on a truth: public perception matters in language decisions. A tool which is perceived to only be useful to academics and tinkerers often times won't make it onto the short list, even when it merits being there. Seeing that Facebook can use this tool effectively at scale might mitigate the early adoption risk that many feel, and let them concentrate on evaluating Haskell for how it fits the problem. Without the validation of seeing it used for large, real-world systems, it might never make it that far.
ori_b 11y ago
Strongly agree -- I'm on a team at Facebook that has D code in production. There is a lot of investment that we'd have to do to make it what I'd call solidly production quality. At one point, I found myself writing a heap profiler, since the tools available where inadequate. If your company doesn't have the ability or will to fix issues deep within the runtime of the shiny new system you're using, I'd be cautious about using a shiny new tool in production. I'm not necessarily saying "Don't do it", but you do need to think long and hard about how you'd handle a tricky bug in your tool.
- 11y ago