sjakobi

Wrong link?!

Hmm, that bike looks very much like Swapfiets' "Deluxe 7" model, which has a 7-gear hub, so not a single speed! The gears also explain why there are three wires leading to the handlebar (2 for the brakes + 1 for the gears).

Nevertheless, the lowest gear on that bike is still not much help on a steep ascend like this.

How does Lebanon lose from this project?

http://hackage.haskell.org/package/brick is popular in the Haskell world.

Discussion on r/haskell: https://www.reddit.com/r/haskell/comments/gtm3w0/on_marketin...

There a several companies who benefit massively from using Haskell, not least by attracting talent!

The most recent instance is probably Juspay: https://github.com/juspay

jdh30, the author of both comments, is a massive OCaml fanboy and Haskell hater. I've seen him try to take Haskell performance numbers and interpret them using the wrong units to make them look worse. I'd take anything that he says about Haskell with a big, big grain of salt!

Regarding build tools for C, you might find this one interesting:

https://github.com/vmchale/cpkg

Hughes' pretty printer works really well for pretty-printing Haskell code, but Wadler's is more flexible for pretty-printing C-style languages where there is a dedented closing brace at the end of scopes.

That's very interesting! So far I've only used Wadler-Leijen-style prettyprinters.

Are Hughes-style pretty printers "better" in some way for Haskell-like documents? If so, why?

There's a similar blog post by Gabriel Gonzalez which focuses on the incentives set in Haskell:

http://www.haskellforall.com/2016/04/worst-practices-should-...

Thanks for mentioning BR Heimat! I didn't know I needed this! :)

FYI OP: I posted your review on r/haskell where it got several comments: https://www.reddit.com/r/haskell/comments/ewjnf4/a_pythonist...

Doctests are often useful to briefly demonstrate how something works: http://hackage.haskell.org/package/doctest

They are a bit finicky to set up though.

Another good resource: http://yannesposito.com/Scratch/en/blog/Haskell-Tutorials--a...

Hm, I'm afraid to say that I can't find a good resource on how to write and build docs for Haskell libraries. Maybe that's a tutorial you could write once you've figured it out?! ;)

Here are a few links though:

* https://ndmitchell.com/downloads/slides-drive-by_haskell_con...

* https://haskell-haddock.readthedocs.io/en/latest/markup.html

* https://docs.haskellstack.org/en/stable/build_command/#synon...

Also, maybe join the #haskell-beginners channel on Slack: https://fpchat-invite.herokuapp.com/

There are other platforms too though, e.g. https://www.reddit.com/r/haskellquestions/, https://discourse.haskell.org/

This sounds similar to the process used for some parts of Cardano. Duncan Coutts talked about this in this video:

https://www.youtube.com/watch?v=TZGVgNsJSnA

Even Haskell doesn't get it right: there are no exhaustiveness checks on pattern matches

Just enable -Wincomplete-patterns or -Wall!

What are modular implicits?

What kind of compiler is it? What does it compile?

Are you the only person who has worked on it?

This appears to be the building that contained the machines:

https://www.google.de/maps/@49.4431182,11.0857279,3a,75y,31....

I found it via the "GlaserExpress" trailer that appears in a few pictures. I used to live nearby a decade ago.

How can you tell?

In the article about non-Turing-complete languages, I kind of expected to find a mention of Dhall which is a fancy new programmable configuration language:

https://github.com/dhall-lang/dhall-lang

Oh, I had never heard of that command before. Does it work well, i.e. does it improve your workflow?

I'm not sure what that statement was based on. The stack project certainly still uses haddock to document its code.

At least some of the projects he cites also use readthedocs for user guides etc.

How do I get (I mean, build in stack) my useful documentation?

Try

    stack haddock --open <packagename>

https://github.com/hmemcpy/milewski-ctfp-pdf appears to have quite a few fans.

See my reply to a similar comment: https://news.ycombinator.com/item?id=13786992

Have you tried ghcid? In my experience it was a bit quicker than `stack --file-watch`

See https://news.ycombinator.com/item?id=13784085 for why hiring is unlikely to be a problem for them.

I also encourage you to find _any_ experience report that tells of difficulties finding the right candidates for a Haskell job.

A nice feature of stack that cabal AFAIK will not provide is that it takes care of installing GHC in multiple versions. I think that's very important for newcomers.

Not an aspect of the design but an anecdote on their great customer service:

I got my pair of Ortlieb Back Roller Classics as a present four years ago.

After I had used at least one bag almost every weekday since then, the rubber shoulder pads had recently ripped and the inner pockets frayed over the screw nuts.

When I contacted their customer service with pictures of the damage, they sent me replacement shoulder straps and pockets free of charge (they even covered shipping costs) although I had no receipt to prove the age of the bags.

I always carry my Ortlieb bags with the hooks facing away from me.