Elmo wrote:The only bad thing about it as I see it, is that Outlook Express doesn't support it yet. (No mention if support for it will appear in Internet Explorer 7.)
This is a big plus, if it discourages people from using
non-standards-compliant mailers. Of course, if you're
trying to do get many big files from usenet with either
Outlook or Internet Exploder, you're going to spending
a lot of extra time anyway. They have an idiot-friendly
interface, but it's not very productive compared to tools
intended for serious users.
Elmo wrote:
With everything good there must be a bad and the only other complaint I have heard is that yEnc is more "lossy" than other encoding techniques. You might be able to detect a slight loss of resolution if you open a pic in something like Photoshop and compared two photos at the pixel-level. The average pair of eyes don't see the difference though, so yEnc is just a more efficient way of moving binaries over the web.
This is not at all true. yEnc is not 'lossy'. It is a conversion
from binary to ascii, and the reverse coding will reproduce
the original binary file exactly bit for bit. Assuming, of course,
that you have all of the yEnc file. The main advantage
of yEnc is that the overhead is low. The ascii file it codes to
is only about 10% larger than the original binary, so it saves
bandwidth. Base64 and UU encoding add about 50%.
yEnc is also advertised to be more robust about missing
parts, so that an incomplete file can be reconstructed
more completely. This only matters, of course, if you have
par files to fill the gaps, but the combination of yEnc and
par is enormously more robust than the old days when
we had to try to depend on UU encoding. For jpegs, which
usually fit in one part regardless of encoding, yEnc just
saves about 25-30% of download time.