Why would we choose to use tarballs?

All the Red Hat distributions of Linux are provided as RPM files. An RPM file, also known, as a “package”, is a way of distributing software so that it can be easily installed, upgraded, queried, and deleted. However, in the Unix world, the defacto-standard for package distribution continues to be by way of so-called “tarballs”. Tarballs are simply compressed files that can be readable and uncompressed with the “tar” utility. Installing from tar is usually significantly more tedious than using RPM. So why would we choose to do so?
1) Unfortunately, it takes a few weeks for developers and helpers to get the latest version of a package converted to RPM’s because many developers first release them as tarballs.
2) When developers and vendors release a new RPM, they include a lot of options that
often are not necessary. Those organization and companies don’t know what options you
will need and what you will not, so they include the most used to fit the needs of
everyone.
3) Often RPMs are not optimized for your specific processors; companies like Red Hat
Linux build RPM’s based on a standard PC. This permit their RPM packages to be
installed on all sorts of computers since compiling programs for an i386 machine can fit
on all systems.
4) Sometimes you download and install RPM, which other peoples around the world are
building and make available for your purposes. This can pose conflicts in certain cases
depending how this individual built the package, such as errors, security and all the other
problems described above.