René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should aliased encodings be dropped?","articleBody":"As of Node 18, there are [3 encodings that are simply aliases to another](https://nodejs.org/docs/latest-v16.x/api/buffer.html#buffers-and-character-encodings):\r\n- `binary` is an alias for `latin1`\r\n    - \u003e See [binary strings](https://developer.mozilla.org/en-US/docs/Web/API/DOMString/Binary) for more background on this topic. The name of this encoding can be very misleading, as all of the encodings listed here convert between strings and binary data. For converting between strings and Buffers, typically 'utf8' is the right choice.\r\n- `ucs2` and `ucs-2` are both aliases to `utf16le`.\r\n- `ascii` is an alias in one direction but not another: \r\n    - \u003e For 7-bit [ASCII](https://en.wikipedia.org/wiki/ASCII) data only. When encoding a string into a Buffer, this is equivalent to using 'latin1'. When decoding a Buffer into a string, using this encoding will additionally unset the highest bit of each byte before decoding as 'latin1'. Generally, there should be no reason to use this encoding, as 'utf8' (or, if the data is known to always be ASCII-only, 'latin1') will be a better choice when encoding or decoding ASCII-only text. It is only provided for legacy compatibility.","author":{"url":"https://github.com/JordanMartinez","@type":"Person","name":"JordanMartinez"},"datePublished":"2023-07-05T18:35:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/58/purescript-node-buffer/issues/58"}