On 27 May 2021, "Andrzej P. Wozniak" <us...@poczta.onet.pl.invalid>
wrote in alt.comp.freeware:
> Beware - RIOT is buggy. That's the reason.
>
> * Old RIOT 0.62 (32-bit) doesn't work properly with IrfanView
> (32-bit) in Windows 10 (64-bit):
>
http://luci.criosweb.ro/riot/bbpress/topic.php?id=592
> * New RIOT 1.0.1 works properly only in Windows 10. 32-bit doesn't
> work in any older system at all:
>
http://luci.criosweb.ro/riot/bbpress/topic.php?id=624
>
> Note the dates for those reports. The problems in RIOT aren't
> fixed so far.
>
> For PNG you can use new OptiPNG plugin - this algorithm is also a
> part of RIOT tool. Internal PNG support in IrfanView has been
> improved some time ago and now it gives better results than RIOT
> with fast optimization.
I just found this little notice that may explain things better. The way
I read this is that 'programming philosophy' disagreements have more to
do with the removal of RIOT than bugs or anything else:
https://riot-optimizer.com/riot-reaches-version-1-0-with-amazing-changes/
"Unfortunately there are low chances RIOT will ever be implemented in
IrfanView on the 64bit version, not because RIOT does not work, but
because Irfan has some weird demands (yes, I really mean demands) on the
size and packaging of the RIOT plugin. IrfanView does not have an open
plugin architecture, so unless me and him agree on something and he
accepts to simply add the support manually (since again, his plugin
architecture is not open, which defeats the purpose of using plugins
btw), you are stuck with using the 32 bit version and probably an older
version of IV in the future, if he removes RIOT support altogether from
it’s 32 bit version. He insists of bundling the plugin, even if only
the support is necessary, and the installation can be made by RIOT as it
was for the recent years when the plugin was updated, and there were no
issues with that in the past years. Also he has some crazy ideas on
having a single dll (controlling the structure of how RIOT is made) and
expectations about the size, which would only be bellow 3 MB anyway ,
and that request to go bellow 3 MB is silly now with these 1 TB
harddrives.. We are not in 1996 anymore when I had a 160 MB disk. RIOT
is quite complex and has support for formats for which iV has plugins,
also the 64 bit adds overhead. Can’t see why this fixation for size
and how one megabytes makes any difference for a user with a terrabyte
harddrive. Users don’t fill their disks with programs, they fill them
with data. Basically the 64 bit version of IV now has that "Save for
web" menu option coded to not try to run RIOT, even if RIOT would
actually work on 64 bit.
"Anyway, we’ll see what happens. Maybe you will have the 64 bit
version for IV, but it’s really not my call here."