I see a lot of critical comments on here.

The blog post is an exploration of an alternative way to structure code in Haskell.

Why is the bar such that Haskell blog posts have to either demonstrate something clearly better then the status quo or that they need to explain the fundamentals of the language?

▲

wk_end a day ago | parent | next [-]

The audience is going to meet the article where they're at.

It's fine for, say, a blog post aimed at Haskellers to assume Haskell knowledge, but when posted on a board largely consisting of people without Haskell knowledge, it's natural that you're going to get at least a few people saying, "hey, I don't understand this".

But I'll be honest - I'm familiar with Haskell and the ML module system and the underlying concept (that typeclasses and modules are roughly equivalent in some sense), but I'm unfamiliar with Backpack so I still struggled to follow it a little. The target audience is an extremely narrow niche. So I think it's just somewhat poorly written; it doesn't feel like the author really had an audience in mind, other than themselves. There's probably ways of writing this - without spending too much time regurgitating the basics - that would be more palatable to more people.

▲

solomonb a day ago | parent | next [-]

> The audience is going to meet the article where they're at.

I hear you on this point but anyone can post anything on this forum. The burden should not be on the author to write a post that aligns with whatever forum their blog might get posted onto.

▲

teddyh a day ago | parent [-]

The author is free to ignore any and all complaints they consider unfounded. It’s not even like the author is recieving any complaints personally; they have to come here to see any. And if they come here, they will get to read the viewpoint visible from here.

	▲	scrubs 11 hours ago \| parent [-]
		Bingo- post to hn ... you'll get per review. Thats the deal.

▲

scrubs 11 hours ago | parent | prev [-]

Death? cryOfUprising? Why be weird? Is the article supposed to communicate something or is it an entry in the author's personal diary that got out? Sheesh. ... I know language profs try hard to teach people to write. It wouldn't kill to listen.

▲

mvdtnz a day ago | parent | prev [-]

Maybe if the post title used the word "Haskell" it wouldn't attract the opinions of people not interested in Haskell? Pretty obvious stuff.

▲

randomNumber7 a day ago | parent [-]

It contains "type class".

	▲	Asraelite 3 hours ago \| parent \| next [-]
		Those are not exclusive to Haskell. Personally, just from reading the title, I was hoping for an article about the design of type systems in programming languages in general.
	▲	mvdtnz 21 hours ago \| parent \| prev [-]
		... which won't mean much to someone who doesn't know Haskell. The kind of person who might click on this link thinking "types and classes are the same thing, what does he mean 'type class'". (don't @ me with your pedantic bullshit about how types and classes are different, I don't care).