News for hackers. Stuff that matters.
Re:Argh-P-M – Dissecting the RPM file format (2016) by rwmj on Wednesday July 11, 2018 @09:42AM (#17506752)
Almost no one who uses RPMs needs to know the internal format, and if they do they should use rpmlib (or rpm2archive if they just want to unpack the files). Does anyone not use JPEG because they think the internals of JPEG binary format are a bit complicated?
Re:Argh-P-M – Dissecting the RPM file format (2016) by bmn__ on Wednesday July 11, 2018 @11:04AM (#17507470)
The point of the exercise was to not use rpmlib. The comparison to JPEG is inappropriate because it has dozens of interoperable implementations.

Formats defined by a single implementation are sickly and much less viable (remember the lessons of http://libmng.com/ ?); I applaud the reverse engineering effort from the article.

Re:Argh-P-M – Dissecting the RPM file format (2016) by pornel on Wednesday July 11, 2018 @09:52PM (#17511637)
> Does anyone not use JPEG because they think the internals of JPEG binary format are a bit complicated?

Yes! There are lots of examples like this.

• Plenty of small tools write BMP or Targa instead of JPEG or PNG, because these formats are dead simple to reinvent.

• JPEG as we know it is JFIF, which has clearly won over alternative JPEG data containers, such as more complicated TIFF (mode 6). BTW JPEG, for what it does, is brilliantly simple.

• MNG never took off, but dumber APNG did.

Formats that are intended for interoperability need multiple implementations, and it does happen that authors say "no, fuck that" and choose a different format instead.