borrow from blakeembrey/pluralize

Hello! Firstly, thanks very much to spencer and contributors for working so hard on v7 - very exciting new API.

I’m thinking about using compromise in a little project of mine and wanted to test its boundaries a little so I whipped up a jsbin with v7.0.4:

http://jsbin.com/qegelofaku/3/edit?html,console

Of the random words I chose, compromise seemed to get about 1/6 wrong - but I suppose I was choosing slightly uncommon words on purpose. My question is: Should I wait until v7 is released (is there an ETA?) before judging its accuracy, or is the accuracy that we see in the JSBin to be expected in the official v7 release anyway?

I understand that some compromises have had to be made, so this isn’t a critique, I’m just trying to get a sense of how accurate compromise is (or will be) so I can judge whether it’s the right fit for my project. Thanks!

[spencermountain]

neat, i’d never seen either project, actually. will take a look

[spencermountain]

hey, these all work now, as of v7.0.5 - with the exception of durian. 🎉