Update readme.markdown

[perguth]

Mention flip-tape in the section "other". 🦊

[ljharb]

So is this the (deprecated in every other language and testing framework) "should" approach, where it polyfills matchers onto every value?

Does it work with Object.create(null) or with objects from other realms? What if I'm doing for..in over an object, won't the presence of the matchers suddenly break my code?

[perguth]

It only attaches tapes methods to the String prototype (see lines marked with // eslint-disable-line https://github.com/pguth/flip-tape/blob/master/index.js).

So in the case of a for...in loop over a String object your code would probably break. However I don't think for...in-ing over a String is a likely case. Nonetheless I should point that out in the readme.

[ljharb]

aha, i misunderstood. so you're just doing description.matcher(…) instead of matcher(…, description).

That's definitely much less problematic, so I no longer have a concern about including it in the readme. (I'm still confused why you wouldn't want matcher(description, …) to avoid any issues with screwing with String.prototype)