That could have been written better. Thanks for the feedback.
That could have been written better. Thanks for the feedback.
> Haskell I would argue against being an industry language
FYI, the problems the Haskell community has been working on are things like scalability, performance and safety because they're critical to industrial problems. Toy approaches don't work at the scale we operate at -- you need real computer science.
You want 1,000,000 Haskell threads in your app? You've got it. Want to write numerical models that compete with C++ code, in a fraction of the development time? Done. Want to guarantee the app won't crash? Solved. Run models over 10,000 cores? It happens.
Because we put the work in.
---
/me wanders back to a multi-million line Haskell codebase running systems in 25 countries, processing billions a year in financial transactions.
Curious... Can't be a bank, too conservative. Hedge fund? I know Jane Street love their OCaml so functional does have a place in that world. But 25 countries? You'd have to be huge.
There is REAL WORK being done in Haskell! Now I just gotta find out how to get my foot in the door :)
This "throwaway" line on my resume: """Interest in functional programming (Erlang, Haskell, Lisp) and associated techniques as they relates to increasing software reliability and scalability."""
...has gotten me at least 2-3 calls/emails for erlang/haskell-specific work over 3-4 years, and that's without even trying.
Don't be afraid either to make up a second resume b/c from what I can tell recruiters just do google searches and click on links. With linked-in, write a "brave" summary up top and put in a strong haskell statement or two in your details section and you'll probably start getting some calls.
If you're happily employed right now then don't be afraid to change your resume / linked in / passive search to reflect your dream job instead of a "real" job-search resume. Just be ready to "change it back" when you get serious about looking.
I know two large international banks that have significant Haskell codebases. I don't know where you get the idea that banks are too conservative.
The idea comes from 10 years of working with them as an external vendor. I see all sorts (but especially Python and C++) on prop desks, but mostly C# in other areas (integration, data management etc.) That being said, nearly all of my experience is in front office trading and asset management, primarily in listed instruments, with little on OTCs, and nothing on payment processing, 'core banking' or the kind of stuff that spans the entire organisation.
It sounds like Haskell has found a niche at Standard Chartered doing perhaps just that. What are those two banks you mentioned doing with their Haskell code?
This is not fair on Haskell but that is what people think and that really is the issue that Haskell has to overcome.
But that is beside the point. Haskell is more difficult to learn.
For those of us who learned to program in an imperative language first, the difficulty with learning functional programming is unlearning all of our bad habits.
People like dons can do amazing work in Haskell. There at 10x or 100x as many people who can't (not without at least a PhD's worth of study at least), but could be productive in Go on a large array of projects they need to do.
/Studied haskell, hung out on #haskell, thinks its awesome, made me a better java programmer, but always gets blocked on showstoppers due to not knowing the incantations and deep type theory needed to structure a program for high performance and debug space leaks.
Hope the codebase runs well, because that's the bank I use in Singapore ;-)
Has you/anyone written something about how Haskell got picked for the task by that particular bank? Is the language used at other financial type businesses? I've heard some firms use Ocaml.
Jane Street.
Would be fun to see a panel with dons and Yaron Minsky discussing the pros and cons of Haskell and Ocaml, respectively.
I had some discussions about OCaml vs Haskell and, honestly, nobody could come up with a particularly strong case in either direction. (That said, we didn't do anything using multiple cores where Haskell has a bit of an advantage, I believe.) It always came down as "well, Haskell is awesome, but we're already using OCaml and it's pretty awesome too, and maybe easier to learn".
Much more interesting would be Haskell/OCaml vs everybody else, but that gets played out all the time anyhow :P.
Reality and PHP would disagree for 90 to 99% values of "you".
Widely used web servers include http://snapframework.com/ and http://www.yesodweb.com/. There are widely available numbers and reviews of these systems. A new book by O'Reilly covers Yesod (http://www.yesodweb.com/book)
Erlang is nice, but has its own not-so-simple issues: http://www.youtube.com/watch?v=G0eBDWigORY
Interestingly, many things in Go's design that might seem 'deficiencies' from the point of view of Erlang means most of those problems don't apply to Go at all.