> > Why do it in core? > Is userland base16/base32 performance unsatisfactory?
Even if the performance is satisfactory, having this in core can help user-land code to get rid of their own implementations (which they often do, to be URL-safe, for example). I imagine native implementations can make use of CPU SIMD acceleration as well, like we already do for the current base64 functions. The initial message also mentions adding this functionality into a separate namespace, so I'm quite positive with this proposal. Even more so than the previous proposals that proposed to add new parameters to the base64 functions.
