From: Feross Aboukhadijeh <feross@feross.org>
Date: Wed, 8 Jan 2014 03:33:04 +0000 (-0800)
Subject: README
X-Git-Url: https://zoso.dev/?a=commitdiff_plain;h=42457dffb19fbc81ac0ff80e30676ee5e5a66f53;p=buffer.git

README
---

diff --git a/README.md b/README.md
index f583692..9c0c8ac 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ By augmenting the instances, we can avoid modifying the `Uint8Array` prototype.
 
 ## Important Differences
 
-- **Use `Buffer.isBuffer` instead of `instanceof Buffer`.** `instanceof Buffer` doesn’t work because the Buffer constructor returns a `Uint8Array` (as discussed above) for performance reasons. In node `Buffer.isBuffer` just does `instanceof Buffer`, but in browserify we use a `Buffer.isBuffer` shim that detects our special `Uint8Array`-based Buffers.
+- **Use `Buffer.isBuffer` instead of `instanceof Buffer`.** The Buffer constructor returns a `Uint8Array` (as discussed above) for performance reasons, so `instanceof Buffer` won't work. In node `Buffer.isBuffer` just does `instanceof Buffer`, but in browserify we use a `Buffer.isBuffer` shim that detects our special `Uint8Array`-based Buffers.
 - **Don't rely on `slice()` to modify the memory of the parent buffer.** If the browser is using the Typed Array implementation then modifying a buffer created by `slice()` will modify the original memory, [just like in Node](http://nodejs.org/api/buffer.html#buffer_buf_slice_start_end). But for the Object implementation (used in unsupported browsers), this is not possible. Therefore, do not rely on this behavior until browser support gets better. (Note: currently even Firefox isn't using the Typed Array implementation because of [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=952403).)
 
 ## Performance