haskellweekly / haskellweekly.github.io

A free weekly newsletter about the Haskell programming language.

Haskell Weekly

Haskell Weekly publishes curated news about the Haskell programming language. It is both a newsletter and a podcast. Find out more at haskellweekly.news.

Haskell Weekly is run by Taylor Fausak.

Contributing content

We appreciate all contributions, from issues to pull requests. Nothing is too small!

If you want to bring our attention to something, please open an issue! This can be used for anything from typos to new content. For example, this has been used for calls for participation, jobs, and bugs.

If you want to make a change yourself, please open a pull request! We encourage you to make changes when you can, and we'll work with you to get your changes merged quickly. For instance, this has been used for packages of the week, featured content, and typos.

Job postings

We are happy to include job postings for Haskell engineers! If you'd like a job posting to be included in more than one issue of Haskell Weekly, please consider advertising with us. This page explains all the details: https://haskellweekly.news/advertising.html.

Contributing code

The code that powers Haskell Weekly does not change that frequently. However we still welcome changes to it! The overall guidelines from above also apply to code. In addition, there are a couple other things to keep in mind:

• Pretty much any build tool should work. Use whatever you prefer, whether that's Stack, Cabal, Nix, or something else.

• Most small changes probably don't require running things locally. We have continuous integration (CI) set up and will help you work through any potential build errors.

Architecture

For the most part Haskell Weekly is just this repository, which is a single Haskell web service. However it relies on some external services:

• GitHub: Hosts source code.

• Mailchimp: Manages subscriber information and sends weekly emails.

• Square: Accepts payments for advertisements.

• Amazon Web Services: Does everything else.

haskellweekly.github.io's Issues

Use better date format

The emails use the “mm/dd/yyyy” format, which is garbage. It should use “yyyy-mm-dd” instead.

Should be an easy change to the *|RSSFEED:DATE|* tag. https://templates.mailchimp.com/getting-started/merge-tags/rss-merge-tags/

Subscription information

Haskell Weekly's subscription information should be public. In the past I tweeted the numbers, but that was tedious. I would like a more automated solution.

Feature "Transity"

Two weeks ago I published Transity (https://www.feram.io/blog/2018-06-05_transity_the_future_of_plain_text_accounting/) and I was blown away by all the feedback. So I thought it might also be interesting for the Haskell Weekly crowd.

However, it's written in PureScript.
Do you feature PureScript Projects in the newsletter as well?

Building Blocks

Hey Taylor,

Thanks for doing this newsletter, loving the content!
I was wondering if any of my work could be interesting to people?

• Building Blocks article, article.

  A more visual approach to introducing FP and purity/immutability.

• Shikensu, library.

  Run a sequence of functions on in-memory representations of files.

If not, carry on.

✌️

Collect information about featured authors

I think there is a valuable feature Haskell Weekly could be providing that it isn't: A list of good authors to follow who produce Haskell content. Currently there are two ways to get this information:

1. See who Haskell Weekly follows on Twitter. This isn't great because not everyone uses Twitter. Also Twitter can have a lot more noise to signal compared to a blog. https://twitter.com/haskellweekly/following

2. Trawl through issues of Haskell Weekly and add sites to a feed reader or something. (This is actually what I do right now! Ugh.)

Both ways suck. I have people ask who to follow in the Haskell community, and I wish I could point to something on Haskell Weekly to answer that. Haskell Weekly seems well situated to provide such a list.

So I'm proposing that I collect information about authors features in Haskell Weekly. The idea is to provide the information in both a way that is good for humans as well as a machine-readable format. The end result could even be used to provide a service like Planet Haskell.

For each author, the following information would be immediately useful:

• Name. For most authors, this is a person. Sometimes it's a company, like "FP Complete", and sometimes it's a project, like "Stackage".

• Site/URL. This is the home page, not the specific piece of content.

• Feed. Not everything has a feed, but if Atom or RSS is available, it would go here. I prefer Atom over RSS.

• Twitter. Also not ubiquitous. However Haskell Weekly announces new issues on Twitter and mentioning featured authors is a nice way to alert them as well as increase engagement.

Found a haskell job

Hello!
Not sure if it is a right place to write about something like that, but that's only way which I've found to contact you.
I've noticed, that Jobs section is pretty poor, so when I found a related vacancy, I feel confident to notify you about it. Unfortunately, it's in Russian, but I'm sure a few people from such location are reading haskell weekly and it could help someone to find his/her dream job, 'cause the company, in my opinion, is great: biocad(eng)

[RU] Haskell Developer

promote the linux.conf.au FP miniconf

linux.conf.au 2018 (Jan 22..26, Sydney) will feature the Real World Functional Programming
miniconf on either Mon 22nd or Tues 23rd.

The call for papers is open until November 27th. Full details at
https://linux.conf.au/programme/miniconfs/functional-programming/.

It would be great if you could mention the CFP in the Call for participation section of an upcoming issue!

Anduril Industries Job Posting

Hi! I was wondering if you'd graciously consider including Anduril Industries in the jobs section of issue 102? We've reached out in a few other places and have been using roughly this blurb:

Anduril Industries (https://www.anduril.com) is hiring. TL;DR: Come write Haskell, Rust, and Nix (and some C++ when necessary) to make autonomous robots and drones go!

We're a team of software and hardware engineers from various backgrounds (game development, computer graphics, financial technology, government intelligence, biotechnology) working to improve the state of defense technology. Our strategy involves focusing on product development instead of traditional governmental processes. By funding product development ourselves instead of relying on government funds, we're able to create more focused products faster and with significantly fewer resources. By leveraging hardware and techniques that have only recently become feasible to deploy at scale (e.g. GPGPU computing), we can significantly advance the state of the defense technology market.

We're searching for generally competent, mathematically inclined software engineers, and we're especially interested in those with experience in computer vision (first principles techniques and machine learning), sensor fusion, detection and tracking, and statistical parameter estimation. Our team is increasingly applying functional programming and related technologies; we run Haskell and Rust code in production and use Nix to achieve reproducible build environments and keep deployment, CI, and cross-compilation sane.

If you like FP, interfacing with hardware, and solving problems in detection, tracking, and autonomous vehicle control (land and air), drop me a line at travis-at-anduril-dot-com.

Thanks so much!

Support HTTPS

https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/

Document rules

I have a bunch of unwritten rules for Haskell Weekly. I've written about some of them incidentally:

• #57 (comment)
• #55 (comment)
• #51 (comment)
• https://www.reddit.com/r/haskell/comments/5m6p05/issue_36_haskell_weekly/dc1k9kx/?context=3

It would be nice to codify these (and other) rules in something like CONTRIBUTING.markdown.

Job section

Hi there!

I was wondering if it would be a good idea to create an additional section with new Haskell jobs. Something like what This Week in Rust is doing.

If it's a matter of curating the list every week, I can do that. I see the process as something along the lines of checking whoishiring.io, Functional Jobs, Functional Works, AngelList, then posting the relevant links to Haskell jobs. If there aren't any new ones this week, mention that instead.

What do you think?

Publish RSS feed

Instead of running everything through MailChimp, it might be better to run Haskell Weekly as a blog that happens to send emails. I could set up a blog through GitHub Pages with an RSS feed. Then MailChimp could consume that RSS feed and send it out as an email.

Initially suggested on Reddit by u/throwawaylifespan: https://www.reddit.com/r/haskell/comments/4x8ggr/announcing_haskell_weekly/d6dbahn

Fix broken links

The sequel to #61.

• 404 http://chrispenner.ca/post/homebrew-haskell
• 404 http://winterland.me/2017/08/18/an%20unified%20array%20interface/
• 409 http://www.seas.upenn.edu/~sweirich/papers/systemd-submission.pdf
• 404 https://angel.co/nstack/jobs
• ERROR: HttpExceptionRequest Request { host = "arxiv.org" port = 443 secure = True requestHeaders = [] path = "/abs/1703.10857" queryString = "" method = "GET" proxy = Nothing rawBody = False redirectCount = 10 responseTimeout = ResponseTimeoutDefault requestVersion = HTTP/1.1 } (ConnectionFailure Network.Socket.sendBuf: failed (No error)) ("https://arxiv.org/abs/1703.10857")
• ERROR: HttpExceptionRequest Request { host = "blog.hustlr.in" port = 443 secure = True requestHeaders = [] path = "/posts/2017-07-19-midterm-eval.html" queryString = "" method = "GET" proxy = Nothing rawBody = False redirectCount = 10 responseTimeout = ResponseTimeoutDefault requestVersion = HTTP/1.1 } (InternalException (HandshakeFailed Error_EOF)) ("https://blog.hustlr.in/posts/2017-07-19-midterm-eval.html")
• 504 https://medium.com/@n0mad/when-competing-with-c-fudge-the-benchmark-16d3a91b437c
• 409 https://www.cis.upenn.edu/~jpaykin/papers/pz_linearity_monad_2017.pdf
• 404 https://www.shimweasel.com/2017/07/13/a-modest-scraping-proposal

DataHaskell section

Hi!

would you be open to a new section, related to numerical and data science activities? I started a DH newsletter [1] last Sunday, but I have a feeling Haskell Weekly is more visible these days.

Thanks!

[1] https://mail.haskell.org/pipermail/haskell-cafe/2018-June/129281.html

Feature 'summoner' on HaskellWeekly

Hello! I notice that in latest HaskellWeekly our project summoner wasn't mentioned:

• https://haskellweekly.news/issues/110.html

Though we had announcement on Reddit recently:

• https://www.reddit.com/r/haskell/comments/8nsgll/ann_summoner_better_cabal_init_or_alternative_to/

Maybe you could include it in next Haskell Weekly news feed?

Add Twitter cards

https://dev.twitter.com/cards/types/summary

I usually post new issues to Twitter. They don't look great.

Event: Auckland FP Meetup - 27 March - Learn FP

Please add this event to the next issue:

-   March 27: [Auckland FP Meetup: Learn FP Hands-on](https://www.meetup.com/Functional-Programming-Auckland/events/248322238/) in Auckland, New Zealand

i.e.

• March 27: Auckland FP Meetup: Learn FP Hands-on in Auckland, New Zealand

Change how deploys work

The current setup is pretty crappy:

• Rendered HTML lives on the master branch, which nobody should ever actually look at. https://github.com/haskellweekly/haskellweekly.github.io/tree/master
• Development happens on the hakyll branch, which is automatically rendered and pushed to master on CI. Also it's poorly named because it doesn't use Hakyll anymore (since #84). https://github.com/haskellweekly/haskellweekly.github.io/tree/hakyll
• Each issue happens on its own branch, like issue-94, which usually gets merged into hakyll for publication. https://github.com/haskellweekly/haskellweekly.github.io/tree/issue-94

This is all very confusing and no doubt hampers contributions. I think a better system would be:

• Develop on the master branch.
• Publish to the gh-pages branch.
• Use tags to control publishing rather than publishing whatever's on master at any given time.

FHPC 2018 Call for Presentations and Demonstrations

Functional High Performance Computing 2018: Call for Presentations and Demonstrations

The refereed paper deadline has passed. In the workshop spirit, the refereed paper presentation program is being expanded to accommodate less formally reviewed presentations in the form of talks not based on accepted papers, and software demonstrations. Topic areas of interest include research or development in progress, experience reports, and position/white paper statements.

Proposals will be subject to a mild reviewing process to insure relevance and general interest to FHPC. We expect time slots to be between one-half and one hour.

Prospective presenters are requested to submit an abstract describing their proposed contribution via the paper submission site. The deadline is July 29, 2018, midnight anywhere on Earth, but the PC reserves the right to accept proposals at any time after submission. As such, early submission is strongly encouraged.

https://icfp18.sigplan.org/track/FHPC-2018-papers

Branches automatically deploy

https://travis-ci.org/haskellweekly/haskellweekly.github.io/builds/151813965#L734

Quito Lambda event

Thanks for the suggestion, @nebtrx! https://www.meetup.com/Quito-Lambda-Meetup/

CfP: Workshop on Functional High-Performance Computing 2018 at ICFP

Hello,

I'd like to draw attention to the following--thanks for considering!

Kei Davis (as co-chair)

CALL FOR PAPERS
FHPC 2018
7th ACM SIGPLAN Workshop on Functional High-Performance Computing
September 29, 2018, St. Louis, Missouri, USA
https://icfp18.sigplan.org/track/FHPC-2018-papers

Improve design

The current styling is ... spartan.

It would be nice to be on par with other newsletters like Ruby Weekly and This Week in Rust.

Call for Participation section

Hi Taylor,

What do you think about adding this kind of section to the newsletter? It would include open source projects that need help, possibly including the difficulty of each issue.

This is something that This Week in Rust does and it seems to be working quite nice. Here's what that looks like:

I understand that it might be a bit trickier to do this for Haskell projects, but including even a few open issues each week might be a nice way to get people more involved. Especially if there are easier issues out there, that would be a good opportunity for people new to Haskell to actually practice using it.

I am up for handling this part myself, either by encouraging people to tweet/email me with their issues and then editing the newsletter on my own or by writing up a document describing how to add new issues, where things go and so on, so that people could send the PRs here themselves.

Let me know if this is something worth doing.

Thanks!

Include link to discussion

It could be nice if an item also had a pointer to the relevant discussion of the link, e.g Reddit, mailing list or other relevant forum.

Would that be interesting?

CFP: Haddock quick jump

haskell/haddock#781

CI build is broken

The CI build died twice in a row:

• https://travis-ci.org/haskellweekly/haskellweekly.github.io/builds/255657701
• https://travis-ci.org/haskellweekly/haskellweekly.github.io/builds/255659376

Building simply takes too long (or consumes too much memory) for Travis to handle. I see a couple ways out of this:

• Prune the dependencies. This would be hard because Hakyll eventually depends on Pandoc, which is a beast to build.
• Switch to lighter dependencies. For example, I could get away with using CMark instead of Pandoc. This would require writing a little bit of my own code.
• Aggressively remove almost all dependencies. In other words, write my own static site generator. This might be fun but also time consuming. It could also allow me to do some interesting stuff, like representing issues as Haskell data types.
• Switch to GitHub Pages (which uses Jekyll) and avoid building anything myself. This is by far the easiest option since I'm already familiar with Jekyll. The downside is that Haskell Weekly wouldn't be built with Haskell.

Track outbound links

MailChimp tracks clicks in the emails. It would be nice to track clicks on the website through Google Analytics. https://support.google.com/analytics/answer/1136920

End of year issue

Last year I did a small roundup of the most popular links at the end of the year: https://haskellweekly.news/issues/35.html

I'd like to do something similar this year. I could either do the top N links of the year or the best link from each issue. Choosing the best link from each issue is easy, but it also results in a lot of links. And what happens if one issue had two killer links? On the other side of things, should the top N links be chosen by absolute number of clicks or percentage clicks from subscribers? In either case, should web clicks count, or should only email clicks matter?

Mood Media PureScript job ad

We are still looking for a PureScript dev at Mood Media and was wondering if you'd mind adding it to the Jobs section for the next weekly. Here's some more details:

Mood Media is still looking for a junior/mid-level PureScript developer to work on our Digital Signage
solution. PureScript experience is not required (any FP experience will do).
The job is in Bucharest, Romania (no remote).
We are doing all new development in PS, and migrating existing (TypeScript/Angular) code to PS as well. There are plans to migrate server-side tools and code (from C#) to Haskell.
For more info, https://www.linkedin.com/jobs/cap/view/558610746/

Thank you

Patreon

I set up a Patreon for Haskell Weekly: https://www.patreon.com/haskellweekly

People have asked for this before, but I don't have any links handy.

I think it might be better to go with the patron model rather than advertising (see #57 and #89).

At any rate, this issue exists to fine tune the Patreon page and figure out how to broadcast it.

Upgrade to GHC 8.0.1

I think Hakyll is in the latest nightly snapshots. It would be nice to be on GHC 8.0.1 instead of GHC 7.10.3.

Create page describing ads

Issue 57 was the first to feature an ad. Since then I have sold a few more, but the process has been a little painful. It would be nice to have a page to point people to that explains what ads look like in Haskell Weekly, how much they cost, and some basic stats like number of subscribers and open/click rates. For an example, Functional Jobs looks pretty nice.

2nd CfP Workshop on Functional High-Performance Computing 2018

https://icfp18.sigplan.org/manageCalls/FHPC-2018-papers

The 7th ACM SIGPLAN Workshop on Functional High-Performance Computing (FHPC 2018) is being held as in previous years in conjunction with the International Conference on Functional Programming (ICFP 2018) together with numerous other workshops/symposia, and as a first, colocated with Strange Loop, in St. Louis, MO, USA.

RSS feed isn't a valid link

Checking the RSS feed using the Feed Validator and the feed does not validate.

Specifically, error:

Server returned [Errno 1] _ssl.c:504: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

The help on that error explains:

Your feed couldn't be validated because there was a problem downloading it from the web server. You should try to diagnose this using a web browser, and make sure that the URL you supplied resolves to an accessible file.

This usually means that the URL was wrong, or that permissions on the server don't allow us to fetch that file. The error shows the message that the server sent, which may help.

2017 survey results

The survey (#102) went out last Wednesday. I had originally planned to keep it open for a month (through December 1), but now I think I'll only keep it open for a week (through November 8). New submissions have already slowed to a crawl (less than one an hour), and I've received more responses than I've expected (more than 1,100). I would rather close the form and do something with the results than leave it open for a long tail of submissions to trickle in.

So, on that note, here's what needs to be done with the survey data:

• Collect all the responses and export them to some useful format, probably JSON. This is for private use and will not be shared.
• Strip any potentially personal information from the responses and export them to JSON and CSV. This is for public use and will be shared. It's not yet clear if free-form answers should be included or excluded from this data.
• Graph all the basic multiple-choice answers. The graphs should be self-explanatory so that they can be posted to social media without being misconstrued. For example, they should include the year, original question text, original answer choices, and actual data labels.
• Analyze all the free-form answers and synthesize them into some key points.
• Put all that together into a blog post or infographic or something. This is a little weird because Haskell Weekly hasn't published original content in the past. Should it start now, or should I post the results on my blog and feature them here? I'm not sure yet.

Fix broken links

I found a few broken links with https://gist.github.com/tfausak/f0581d40cc7d308aa93940cd531ccc94:

• http://blog.fightingtanukis.com/posts/2016-05-23-documentation-hierarchy.html
• http://coldwa.st/e/blog/2016-05-04-Cabal-1-24.html
• http://lwm.github.io/posts/html/document-haskell.html
• http://www.seas.upenn.edu/~sweirich/papers/systemd-submission.pdf
• http://www.snoyman.com/blog/2016/08/haskell-org-evil-cabal
• https://dl.dropboxusercontent.com/u/40457956/haskell_sucks.pdf
• https://lwm.github.io/haskell-static/
• https://lwm.github.io/stackage-8.0.2/
• https://mmhaskell.com/blog/2017/4/10/putting-your-haskell-to-the-test
• https://mmhaskell.com/blog/2017/4/3/compile-driven-learning
• https://mmhaskell.com/blog/2017/5/15/untangling-haskells-strings
• https://mmhaskell.com/blog/2017/5/8/4-steps-to-a-better-imports-list

Some of them may be false positives. It would be nice if these were checked automatically every now and then.

Building Forum Software

Mr. Fausak,

As I've promised you on this issue, I've completed a blog post about building software.

The article in question can be reached here.

Regards,
Ibnu.

Stack and the call for contribution this issue

Thanks for all your work on Haskell Weekly - it's great.

I wanted to note that in the 'Call for Contribution' section this latest issue, the Stack related issue was closed. That's fine, of course, things are moving along but it got me thinking. Might we get a 'Stack needs people to help all the time, forever' note in there to try and get people involved? If that is a bit much, perhaps linking out to the 'newcomer-friendly' issues, which might also be better - https://github.com/commercialhaskell/stack/issues?q=is%3Aopen+is%3Aissue+label%3A%22awaiting+pull+request%22+label%3a%22newcomer+friendly%22. Up to you!

Fix broken links

This is routine maintenance. It picks up where #107 left off. I added a script to check for broken links: fcbe834. Running the script gave 24 broken links:

• 001 http://typed.funops.co/tutorials/2016/05/25/unreasonable-effectiveness-of-reasoning-understanding-bottom.html ConnectionFailure Network.Socket.getAddrInfo: does not exist (nodename nor servname provided, or not known)
• 001 https://goc.vivint.com/problems/hm InternalException (HandshakeFailed (Error_Protocol ("certificate has expired",True,CertificateExpired)))
• 001 https://quasimal.com/posts/2018-01-08-prefix-tree-parsing.html InternalException (HandshakeFailed (Error_Protocol ("certificate has unknown CA",True,UnknownCa)))
• 001 https://storm-country.com/blog/gof-strategy InternalException (HandshakeFailed (Error_Protocol ("certificate has expired",True,CertificateExpired)))
• 001 https://storm-country.com/blog/LambdaCase InternalException (HandshakeFailed (Error_Protocol ("certificate has expired",True,CertificateExpired)))
• 001 https://turingjump.com/blog/bookkeeper/ ConnectionTimeout
• 001 https://turingjump.com/blog/tech-empower/ ConnectionTimeout
• 001 https://turingjump.com/posts/smerdyakov.html ConnectionTimeout
• 001 https://www.vacationlabs.com/haskell-internship/ InternalException (HandshakeFailed (Error_Protocol ("certificate has unknown CA",True,UnknownCa)))
• 403 http://r6.ca/blog/20171010T001746Z.html
• 404 http://asivitz.com/posts/layers
• 404 http://vmob.me/DE3Q17Haskellweek
• 404 https://blog.qfpl.io/posts/reflex/widgets/growing-a-date-picker-1/
• 404 https://functionaljobs.com/jobs/9050-backend-ruby-and-haskell-engineer-at-health-efilings
• 404 https://functionaljobs.com/jobs/9053-software-engineer-haskell-full-stack-at-capital-match
• 404 https://github.com/haskell-perf/attack/blob/054fb2c82f91fcee7bce76661ea290c80c450a20/archive/2018-jan.md
• 404 https://hihenry.com/fullstack-engineer
• 404 https://ibnuda.gitlab.io/636452721192300168_authorizationinservant.html
• 404 https://jobs.zalando.com/jobs/993940-backend-software-engineer/
• 404 https://lwm.github.io/ghc-802-stackage-nightly-and-lts-update/
• 404 https://lwm.github.io/lets-write-documentation-for-haskell/
• 404 https://lwm.github.io/static-analysis-with-haskell/
• 404 https://www.meetup.com/Beaverton-Haskell-Meetup/events/241822925/
• 999 https://www.linkedin.com/jobs/cap/view/558610746/

Some of those might be false positives. The "001" status code means there was an HTTP exception. The "999" status code isn't my doing, so either LinkedIn is returning some weird stuff or the HTTP client is bungling something.

Compose Melbourne event

Thanks for the suggestion, @sordina! http://www.composeconference.org

Survey

I recently saw the Rust survey results: https://blog.rust-lang.org/2017/09/05/Rust-2017-Survey-Results.html

I know of a few Haskell surveys from the past:

• http://blog.johantibell.com/2010/08/results-from-state-of-haskell-2010.html
• http://blog.johantibell.com/2011/08/results-from-state-of-haskell-2011.html
• https://www.fpcomplete.com/blog/2015/05/thousand-user-haskell-survey

There may be more, but I don't know about them.

The previous Haskell surveys didn't get as many responses as the latest Rust survey:

Survey	Responses
Rust 2017	5 368
Haskell 2015	1 240
Haskell 2011	798
Haskell 2010	804

Regardless, I think it would be good to survey the Haskell community. Probably on a yearly basis. Seeing as I run Haskell Weekly, it makes sense to me to send the survey out through Haskell Weekly. I don't yet know what I want the survey to look like or when it should go out. That's what this issue is for 😄

Include event locations

@MaxGabriel suggested that I include the locations of the upcoming events. That sounds like a good idea to me!

Figure out a way to feature old content

@eborden suggested this.

There's a lot of old content that's not news but would still be nice to feature somehow. Stuff like this:

• http://www.haskellforall.com/2016/02/state-of-haskell-ecosystem-february.html
• http://www.stephendiehl.com/posts/production.html
• https://code.facebook.com/posts/745068642270222/fighting-spam-with-haskell/
• http://comonad.com/reader/2014/letter-to-a-young-haskell-enthusiast/
• https://ocharles.org.uk/blog/pages/2014-12-01-24-days-of-ghc-extensions.html

The two problems that need solving are:

• Where should this content go?
• How should this content be chosen?

Since I'm currently the only editor of Haskell Weekly, the news I pick reflects my bias. That's kept in check a little by only picking recent stories for each issue. If I'm reaching back to publish anything, I may have to be more careful about what I pick.

One way around that could be to pick the "best" links from previous issues, where "best" might mean "most clicked on, according to MailChimp". Obviously that limits me to a year's worth of content at this point.

Depending on how this content is presented, how long should it last? Would it be one piece of content "from the archives" each week? Several at a time, but not on any regular schedule? What should I do if I run out of content? Do I start cycling at that point?

Document services used

This is mostly for my own benefit at this point. Extracted from #59 (comment):

• Name.com for domain name registration.
• Cloudflare for DNS and HTTPS.
• GitHub (duh) for repository hosting.
• Travis CI for tests and static file generation.
• GitHub Pages for static file hosting.
• Google Analytics for site analytics.
• MailChimp for email stuff, including managing subscribers, sending emails, and analytics.
• Feedly for keeping up with Atom/RSS feeds.
• Twitter for announcing new issues and generally interacting with the community.
  • Random other social accounts including Reddit, Lobsters, Hacker News, and the haskell-cafe mailing list.
• Square for collecting payments.

Come up with a better way to handle events

Linking to one event from meetup.com per day isn't that great. I think making a more robust solution that takes less effort in the long term wouldn't be too hard.

[Content] An example of Haskell on the JVM using Frege

An example of Haskell on the JVM using Frege is reported on here:

http://www.jeroenkeiren.nl/blog/on-games-and-simulations/

The post describes a tool that was developed to visualize an important concept in the "theoretical" sub field of computer science. The author gives a detailed account on the design decision to write the core of the application in Haskell and use Java to provide a visual rendition of the Haskell core. It also shows another application where the author has replicated this choice. The article provides a high-level overview of the realization of such an application, but is also linked to a source code repository of the project for the more interested reader.

Disclosure: it is me who wrote the article.

Meetup in Frankfurt, Germany

I will be giving a talk at the Frankfurt HUG: https://www.meetup.com/Frankfurt-Haskell-User-Group/events/251622624/

Would be great to have it in the newsletter ;)

Two entries: cachix and well-typed course

1. https://github.com/cachix/cachix and http://cachix.org

2. https://www.well-typed.com/blog/2018/06/remote-interactive-type-level-programming-course/

Twitter card image does not show up

I'll bet the URL has to be absolute.