Let’s agree on JΦEG, then 
By the same token, GIF is hard G because of Graphics. 
What about PNG? I’ve always refered to it as “ping.” 
I remember reading decades ago that it was supposed to be “Jif”, not “gif”. Well, I remained a renegade and have always called them “gif”. After all what did “they” know, “they” were just the originators of the format… 
The real problem here is that we often refer to the JFIF file format (JPEG File Interchange Format) by saying JPEG. 
JPEG information and specs should be mandatory reading. 
A very long time ago, my bed table reading was the ADA language specifications. Never slept so well 
Maybe practice first on K&R, so it’s not such a shock… 
K&R is actually interesting and engaging, IMO.
I cannot get past the third chapters of many of those books. 
Aspiration is one thing. Will is another all together.
It’s been a LOOOONG time since I looked at K&R but my reaction was that it’s dense, concise, accurate and assumes the reader knows the terrain. That’s not bad, but I just found it rather easy to miss points, indeed, rather difficult to feel I fully understood all that was said and implied when I read it.
But it’s apparently a model (of sorts, according to some) of concise technical documentation.
What is K&R??
I did a search but only found a Pentax K-R. Nice, but not what I was looking for…
My guess: K&R - Wikipedia. Not the last point. 
Yep - The C Programming Language - Wikipedia
By Brian Kernighan and Dennis Ritchie
The description of the C language designed by Ritchie. Not to be confused with K&B, a defunct drug store chain from New Orleans. 
The first paragraph of chapter 1, entitled “A tutorial Introduction” is long, but not overly scary or unfriendly:
Let us begin with a quick introduction to C. Our aim is to show the essential elements of the language in real programs, but without getting bogged down in details, rules, and exceptions. At this point, we are not trying to be complete or even precise (save that the examples are meant to be correct). We want to get you as quickly as possible to the point where you can write useful programs, and to do that we have to concentrate on the basics: variables and constants, arithmetic, control flow, functions, and the rudiments of input and output. We are intentionally leaving out of this chapter features of C that are important for writing bigger programs. These include pointers, structures, most of C’s rich set of operators, several control-flow statements, and the standard library.
After 2 more introductory paragraphs, the “hello world” program is given. (I think this may be the first instance of “Hello, world” in the literature - it has since become a standard part of the introduction of many languages since.
OK, I am a CompSci graduate, so although I learned BASIC and Pascal before C, K&R was never hideously difficult for me; moreover, its (K&R’s, and also C the language’s) density or concision was actually a feature that I found helpful. That’s why K&R is still something I refer to 35 years after starting university - I’d never do that with my first programming in Pascal book.
Seriously, the specification of C in K&R became the benchmark by which other language specifications and introductions are to be measured, because it is such a well-written and accessible work.
/soapbox descent
I totally concur.
But the book is easy to read because the language is simple and elegant. But then, the language and the book are from the same people. To quote Nicolas Boileau: “Whatever is well conceived is clearly said, and the words to say it flow with ease.”.
And to quote another French author “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."