danvics/oxipng
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update history

Browse source
This commit is contained in:
Andrew 2026-01-06 17:07:13 +13:00
parent c83bd0b002
commit 7283475f97
1 changed files with 5 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -138,17 +138,13 @@ and specifying the desired ones, for example:
## History ## History
Oxipng began as a complete rewrite of the OptiPNG project, Oxipng began in 2015 as a rewrite of the OptiPNG project. The core goal was to implement
which was assumed to be dead as no commit had been made to it since March 2014. multithreading, which would have been very difficult to do within the existing C codebase of OptiPNG.
(OptiPNG has since released a new version, after Oxipng was first released.)
The name has been changed to avoid confusion and potential legal issues.
The core goal of rewriting OptiPNG was to implement multithreading,
which would be very difficult to do within the existing C codebase of OptiPNG.
This also served as an opportunity to choose a more modern, safer language (Rust). This also served as an opportunity to choose a more modern, safer language (Rust).
Note that, while similar, Oxipng is not a drop-in replacement for OptiPNG. However, Oxipng has evolved considerably since then. While some of the options remain similar to
If you are migrating from OptiPNG, please check the [help](MANUAL.txt) before using. OptiPNG, the architecture and capabilities are now quite different. It is not a drop-in
replacement - if you are migrating from OptiPNG, please check the [help](MANUAL.txt) before using.
## Contributing ## Contributing