2 ms·
I was brief and to the point, though. There's a lot of material to cover and I did so fairly quickly. I figured the title was enough to give away the general
by davidw 15y ago
I was brief and to the point, though. There's a lot of material to cover and I did so fairly quickly.
I figured the title was enough to give away the general gist of the article: it's about a programming language and the problems it had. If that's a subject that interests you, perhaps the article is worth a read. I wrote the article to talk about a subject I know well, for people interested in that subject.
tl;dr: not everything can be dumbed down to TV-style sound bytes.
- bborud 15y agoIf you were to submit a paper to a conference or a journal and they asked you to provide an abstract -- would you be offended? Why not? When you read ACM or IEEE journals, do you see the abstracts as "dumbing down to TV-style sound bytes"?
- davidw 15y agoLet's put it this way: if you can't figure it out from the title of the article, it's just not for you. The article was not meant for people with a casual interest in the subject, but those who wanted to know about the details. If that's not you, so be it. I would note, however, that at this point you've surely spent more time complaining here than it would have taken you to read the entire article.
- tbsdy 15y agoHe is not writing for the ACMA or the IEEE. He is writing a blog. There is no need for an executive summary! His article is fine, it took me no longer than 3 minutes or so to read it. Great article!