search

seliopou / elm-d3

Elm bindings for D3.js
Other
335 stars 36 forks source link

Try to make description clearer #8

Closed evancz closed 10 years ago

evancz commented 10 years ago

I have always been a bit confused by the construction of the first sentence. It emphasizes things in a way that is hard for me to understand.

I took the description from the D3 site and tried to describe the benefits of elm-d3 in a simpler way.

I also got rid of the word pure because I don't want to use that in Elm branding. For people outside of Haskell, the term "pure" has come to point to something cultish, bringing to mind things like chastity belts and a holier-than-thou attitude. And when you look it up without knowing anything about Haskell, the first question is "how can a pure language do anything?!" which I think points to a problem with the term in the first place. I'd like to reframe this stuff as "managed effects" or "computations" or whatever. Something that does not have mixed brand association and that gives a clearer view of why it's an important property. In any case, I deemphasized this whole thing.

evancz commented 10 years ago

Ah, it may be better to say "type inference" than "static types". Type inference implies static types and I think people generally react more positively to that term.

seliopou commented 10 years ago

Thanks for taking a crack at this. It's been something that I've been meaning to address. Though the current description isn't great, it is very short. My policy for top-level descriptions is that they should be no more than two or three sentences. They should state what the project is in terms that are clear to the intended audience, and then a little more information for those that might be on the fringe of that audience.

I'll try and come up with a replacement, while taking into account this commit.