You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the base58-encoding has to be implemented in PHP, which is slow compared to native code doing the same.
Base58 encoding produces strings that have desirable characteristics compared to base64:
URL friendly (no /+ or -_ to deal with)
less confusable characters (no 0Ilo)
output of similar size (~73% vs 75%)
This makes it perfect to represent unique identifiers or hashes for example. symfony/uid implements it and my feeling is that it's getting increasingly popular.
Having a native and fast implementation would be nice.
Currently, the base58-encoding has to be implemented in PHP, which is slow compared to native code doing the same.
Base58 encoding produces strings that have desirable characteristics compared to base64:
/+
or-_
to deal with)0Ilo
)This makes it perfect to represent unique identifiers or hashes for example. symfony/uid implements it and my feeling is that it's getting increasingly popular.
Having a native and fast implementation would be nice.
See https://en.wikipedia.org/wiki/Binary-to-text_encoding#Base58 for some more background.
The text was updated successfully, but these errors were encountered: