Shill for Haskell thread

Frederick's experiences echo that of many others who've taken the leap. All of these points echo our experience at fynder. Another couple of point to add (I'll add some more as I think of them):

You can get away with bad code at the periphery of your systems for longer. At fynder we had a pretty nasty data scraping and import utility that grew over time and became pretty unwieldy. However it still worked and was easy to change without breaking. It also fed data into a system that had a very strong guarantee of integrity so there was another line of defence. (I've seen /u/ryantrinkle say similar to this too)

You can go a long way with a small number great programmers laying out the types and the structure, with lesser able programmers "filling in the gaps" as they get up to speed. For example at fynder /u/ocharles came up with a great use of singleton types to make our socket.io communications safer [1]. Even though I could never come up with that from scratch, I was able to add to it and extend it quite happily after a 20 minute explanation (and some follow up questions).

You don't get either of those benefits with, say python, the language I use day to day at the moment. Once your python codebase loses a certain amount of cohesion, it's way harder to refactor your way out, and I think you end up staring down the barrel of a re-write a lot sooner. Equally there's no culture of common fundamental patterns (Functor, Applicative, Monad) that everyone understands so you can't really have a few rock stars implement the core of your system and people of lesser abilities code around the core. You end up having to code to the lowest common denominator whereas in Haskell you can program up to the strongest level more easily.

[1] https://ocharles.org.uk/talk.pdf

It can't be expressed enough IMO how good the refactorability of Haskell code is and how important that is for a business (especially in a startup environment). Unfortunately I think this property is a bit of "you have to see it to believe it" and it's really hard to explain to someone a) why it is that way and b) why it's important.

I do think it's something we as a community should get better at communicating though.

Lingo was developed in-house by OTAS Technologies in order to leverage the OTAS Base analytics API. The NLG engine was developed on the Haskell stack provided by FP Complete.

"We chose Haskell and the FP Complete stack because we knew the complexity of the problem required a new approach. The result was that we built better software faster than ever, and delivered it defect-free into a production environment where it has proven robust and high-performance," add Doris.

http://www.automatedtrader.net/news/at/153887/otas-launches-otas-lingo

Native Client

Our users want to query their databases without any new IT or admin setup, so users connect via their local machine with their existing credentials. Wagon handles connections through the native client, since most databases require socket-level network access that isn’t possible directly from browser.

Exploration and analysis can be a time-consuming and tedious job with existing SQL tools. Each step is an additional database query subject to queuing, slow execution, and changing data. Our users want to quickly explore results and evaluate summary statistics without executing subsequent queries. To power that experience, the client also computes statistics and caches query results on the local file system.

We built the native client in Haskell. It’s a high level language with great libraries, static compilation, a high performance ceiling, and an active community. We use MacGap to bundle the client and the frontend into a downloadable OS X application (Windows soon!).

Technology: Haskell, MacGap

Prototyping and refactoring is safe with Haskell’s type-driven development. The compiler helps us avoid bugs and edge cases as we iterate.
Haskell’s opt-in control over compiler optimizations and strictness allows for incremental optimization. GHC includes a capable profiler, and the community maintains libraries for testing and performance measurement.

Backend Services

Our backend services persists state and shared data to allow users to securely collaborate on queries, results, and charts. The backend is also written in Haskell: using the same language for the client and the server helps us stay flexible and reduce complexity. We store application state in Postgres while larger immutable data, like shared query results, live in Amazon S3.

Technology: Haskell, Postgres, Amazon S3

Haskell’s lightweight threads and the GHC runtime scale well on multi-core machines.
Postgres is powerful, flexible, and straightforward to host. We use features like TOAST and JSON support to test new features.

http://www.wagonhq.com/blog/engineering-at-wagon/

del

unsafePerformIO . print $ "Well typed programs can't go wrong"

>>6
You don't need unsafePerformIO to misquote Milner.

>>6

"Well typed programs can't go wrong"

This is not what Haskell claims to be. Stop being a retard.

>>8
Actually, it is.

Haskell is a simple and readable language for normal people like physicists and mathematicians, cleansed of bytesodomy and rendering specially-bred computer assfuckers-programmers useless. Yes, you read this right. After this language for normal people will get widespread, the byte-Sparta of military faggots-programmers hardened by getting anally fucked with the von Neumann architecture and orally fucked with the applicative order will lose any meaning. What will remain for these pathetic subhumans, whose brains have been whitewashed of anything human for 5 years in grad school? The only thing remaining for them will be ceasing their lowly existence.

>>8
You wouldn't know it from the way people talk around here.

IF IT COMPILES, IT WORKS

>>11
You got references to back that up?

>>13
Yes, because I am autistic and wrote down every post number in my notebook.

static types are a fucking joke, how stupid do you have to be to not know to pass and int to a function that takes and int and bool for a bool. You learn this shit at age 5, square peg square hole, round peg round hole. Even that is above the intellectual capacity of a haskell programmer.

>>14
Ok, let's see 'em. Because I don't remember any of them.

>>15
I bet you're a big fan of hungarianShitCase notation and/or can't program without Intellisense™.

>>15
http://www.lispcast.com/img/typing.png

>>16
I think >>14-kun-sama-chan was being sarcastic.

>>18
You missed one. But don't worry, you'll get the hang of this sarcasm thing eventually!

>>19
Stop pretending that you were being sarcastic.

>>20
Are you for real?

>>21
back to reddit you goes

>>22
Nice dubs!

>>22
quality bump℠

At the start of the products’ life we mostly analyzed small retirement plans with 100 to 500 plan participants. As time went on we started seeing plans with 2,000 participants and even 10,000 participants. At these numbers the execution time for the processing started going outside of acceptable bounds. Luckily, every participant could be analyzed in isolation from the others and so the problem was embarrassingly parallel.
I changed one line of code from

map outputParticipant parts

to

map outputParticipant parts `using` parListChunk 10 rdeepseq

and execution times were now about 3.7x faster on our 4-core server.

>>25
Too bad its 50 times slower than C.

>>26
Just double the cores. Are you too poor to afford 8 cores?

>>27
I think you mean 64 cores.

Bicycle Parking Guidance System in Utrecht

I'm proud to announce that the day after I came back from ZuriHac 2015 we at LumiGuide had the grand opening of our bicycle parking and guidance system that we developed for the city of Utrecht. To our knowledge it's the first system in the world that guides cyclists to available parking space on a city-wide level.

The optical sensors that detect if there's space to park your bicycle are based on a computer-vision algorithm. Haskell is used throughout the system:

- We used GHCJS for building our highly interactive web-client for calibrating the optical sensors.

- The central management server is also written in Haskell.

- Haskell was also used to implement the binary protocols used for communicating with the displays and to interface with third-party parking facilities.

-- Bas van Dijk, chief technology officer at LumiGuide in Nijmegen

https://bicycledutch.wordpress.com/2015/06/09/bicycle-parking-guidance-system-in-utrecht/

>>26
Optimized GHC Haskell is within 3x of C. It has also been known to beat C on occasion.

The Haskell ecosystem has evolved so much that open-source libraries deserve whole talks about them https://www.youtube.com/watch?v=5_fCUSOn7m0&feature=youtu.be

With Lisp, it's just a handful of retards writing interpreters. All the libraries on Cliki are either bitrotten or incomplete abandonware. That is, when then links aren't broken. Lisp is like an old dilapidated hut with a couple of autists inside screaming of their superiority. Haskell is a skyscraper in Abu Dhabi.

>>30
*And reads nothing like Haskell should.

dubs

>>31
The Haskell community is full of bullies

>>34
Haha soft-skinned bitch. Go cry in the corner, emo boy.

>>35
why would you post such a thing?

>>36
Because you've insulted me with your weakness, pussy. Man up!

How Haskellers are seen vs how they see themselves

http://chrisdone.com/posts/haskellers

>>38
cool meme gifs

Muh nads

This expression indicates a Haskell programmer's confusion and lack of understanding. When confronted with something he can not understand or respond to, Haskell programmers mumble, "Muh nads", or "Muh nads, muthafucka." This is usually followed by crotch grabbing and foot shuffling.