... reinventing the wheel runs counter
to everything we do in CS.
You can read all you like about how to juggle - if you don't put in the hours, you won't be able to do it.You can read all you like about how to unicycle - if you don't put in the hours, you won't be able to do it.
You can read all you like about how to program - if you don't put in the hours, you won't be able to do it.
Skills require practice. These instances of "left as an exercise for the interested reader" are to help you really learn and properly understand the material. And if you don't care, don't bother. If you are unwilling to put in the time then the chances are that you would end up thinking you understand an explanation, whereas in fact you don't.
The above is only for good writing, of course. There are plenty of instances of bad writing, but that's not then a complaint about the subject, it's a complaint about the writer.
Someone once said of Feynman that his lectures were beautifully clear, and that those who listened gained real insight and understanding. Until they had to use it. Then they realised that they didn't really understand it at all.
If you want understanding, do the exercises.
So there you are, I've done as you predicted and pointed out that you're just being lazy, and that if you really want to learn then you have to put in the work. Just because you preempted it, doesn't mean it's wrong. It's right, you already know it. Complaining won't help you.
Put in the time.
1. it is doubtful that the author has actually done the work to prove his own assertion, and uses the phrase to cast his own burden on the reader,
2. the author has possibly done the work, but can't be bothered to condense it to the quality required for publication,
3. showing the work would clearly be useful for the target audience, but the author is more concerned with making the material appear difficult, or
4. the author is being ironic, because the assertion is either superfluous, outright incorrect, or known to be unprovable.
In fact, all these bad use-cases are common sources of humor among math nerds (http://www.jargon.net/jargonfile/e/exerciseleftasan.html), (http://abstrusegoose.com/12), (http://fasterdonuts.tumblr.com/post/4516834904/the-proof-is-...) ... so I think I'm being fair in calling this phrase a trope. As in, its overuse is well-known, tolerated, and occasionally ridiculed.
tldr: I am indeed complaining about bad writing, not the subject--specifically that "left as an exercise" has become a common idiom behind which bad writers in math and CS hide, and its inappropriate use is now all too common.
But it is a phrase that has its place, there are times when it's exactly right to use it. Don't reject it outright. I've used it in publication where the editor actually asked me to remove details and put the phrase in its place.
It's not always the author.
Obviously mathematicians don't leave "exercises for the reader" in research papers, but it is common in textbooks or expository writing.
> I always felt that phrase has no place in the internet age, where the concept of a "page limit" is laughable and a simple hyperlink can point me to chapters upon chapters of appendices.
The constraint is not page length, of course, but time. It is a much better use of a mathematician's time to leave easily reproducible proofs to the reader, and focus on the interesting ideas.
Anyway, doing these kinds of exercises is actually very useful in understanding new ideas.
ORLY? I'll leave this right here for you:
http://scholar.google.com/scholar?hl=en&q=left+as+an+exe...
That's >100k hits from what Google Scholar can index alone--a few are from books, but the vast majority are journal articles.
Do you really think anyone would benefit from such proofs in a paper? I would be interested if you could give an actual example of a paper where a reader might be inconvenienced by something being left as an exercise.
I know somebody is about to point out to me that I'm being "lazy" and should enjoy doing more work to learn so and so, but being asked regularly in the literature to reinvent somebody else's wheel seems to run counter to everything we do in CS (and academia in general, I would think). This article aside, I do sometimes feel that academic writing in the math/CS realm occasionally reeks a little bit of snobbery, where communication is held secondary to keeping up appearances.