There are publishing venues intended for a lay audience, but most academic publishing is not, they have incompatible goals.
I was talking to a student the other day. He and I took many of the same classes in different semester in which we were assigned to read articles and then present them as part of class discussion. Typically this ends up being a talk all about the figures of the paper. He mentioned that most of the time, with bio papers, you have to read the article at least 3 times before you can start to grasp what is going on with it, not to mention the online methods section that goes on for ~20 printed pages. Often, the figures are quite clever and really do a good job at conveying the data in a great way, but they are presented as 'in-field' and the graphs, the diagrams, the data, etc. will be very very difficult to understand from a 'novice' point of view. For example, they will present the data out in a polar plot where the 360 graph is known in the field to represent only the arc of sensation out of the right 7th whisker of male mice under anesthesia. In that (contrived) example, you really have to dig about in literature to find this out and if you don't know that then you'll end up confused and really frustrated. Essentially, if you are a person that is somewhat interested in a very closely field of research, you have to spend hours upon hours trying to parse out some piddly little paper. It really is that bad. I don't know what that is, but it sure ain't 'science'. A paper in a closely related field should take you no more time to read and understand to the point of being able to tell someone else than the time it takes to eat a sandwich, a bag of chips, and drink a coffee in total.
But too often, the language (both english & mathematical) of research papers is not intended to enhance academic communication. Rather, it's a faux optimization to game peer review or make results look more "technical" in a way that is actually detrimental to communication.
In effect, the language is counterproductive. And the time spent on faux conciseness is wasted; much like that old quote, "I would've written a shorter letter, if only I'd had more time."
In my experience (in type theory / programming languages), the main problem is that a lot of papers are just badly written. Good papers really do use precise language to be easier to digest for other people in the same field.
Works have an impact if I read them - a publication that targets a wide audience and thus by necessity is three times as long and "too introductory", is a publication that won't be read (by other researchers), won't be cited (by other researchers), and thus won't have an impact. If lots of laypeople read and understand it, well, that's nice, that's how textbooks work, but it doesn't help advance the science. A citation in mass media doesn't count as a citation. If someone silently adapts your method in industry, that's nice, but it doesn't really matter as well - that's a sign that your tech is mature, but "impact" measures the impact that your paper has on future progress - if the next thing doesn't rely on your paper, it doesn't have an impact on your research field anymore. Reviewers are actually representative of the intended audience of readers, so targeting for people like them makes sense.
Maybe the "lottery" citation factor isn't worth the extra effort required to normalize in-field shibboleths. Then again, if maximizing citations truly is the overriding publication incentive, I wonder why low h-index researchers don't pursue this route and 'upgrade' their existing papers for a wider audience wherever possible.
I've frequently heard complaints that people in some CS subfields in particular will just add complicated math because they have to rather than because it helps. It sucks because the authors don't have that great a grasp on the math anyway, the readers don't care about the math -- they just care about the intuition and process, and communication suffers overall.
My best papers had at most like two equations, and they were just there to clarify models for fits and the like in case the reader wasn't familiar with terms like "Arrhenius relation". So, you know, to actually make reading it less burdensome rather than just making it look more sophisticated.
[1] http://www.hizook.com/blog/2015/08/10/mobile-robots-and-long...
There are two high level criteria for publication: novelty and difficulty (this is in my field of Programming Languages and Systems so keep that in mind).
The novelty requirement is important and I trust that you satisfied it but (as you pointed out in a child comment) you may not have met the difficulty requirement and the reviewer did their "best" to articulate that in a way that isn't the all together ridiculous "not hard enough".
Naturally we might wonder why "difficulty" is a requirement at all. Shouldn't the importance or impact of the work be the thing that matters regardless of how difficult it was to achieve? The problem is that it's _extremely_ hard to know what work will be impactful and so reviewers, who have to reject something like 90% of submissions, use the heuristic of "difficulty" to estimate.
This is a problem to be sure but I think it would be a problem in other settings as well.
That said, I don't really think this is all that unique to academic publishing. At some point, I think we've all met someone professionally who makes problems sound more difficult than they really are and seen this person rewarded by management because they're the person who can work on really difficult problems.
It's easy to tell that a long-standing open problem is important, but generally these problems are open because they are hard, and consequently the technical sophistication for new attacks on them is generally very high.[] New problems can often be solved with relatively simple techniques, but it's also difficult to tell if a new problem is genuinely important or just some random thing made up for submission.
With a low acceptance rate, PCs tend to favor type (1) papers over type (2) papers, because few people feel comfortable arguing for a paper that might* be doing something important over one that is doing something important. This is widely seen as a failure mode of low acceptance-rate venues.
So over the last several years many of the top PL conferences (such as POPL, LICS and PLDI) have moved to a multiple track format in order to increase the number of papers they accept. This is precisely to give program committees the freedom to take chances on "risky" papers that might become important, or might become footnotes.
[*] Occasionally, someone will solve a difficult open problem with simple techniques, and these papers are immediately accepted with much rejoicing. It's easy to have your cake and eat it, when you have two cakes...
I don't know if we're talking about the same type of difficulty. I don't think program committees see the difficulty of the problem being solved at the core of the paper as a "negative" necessarily?
> The main thing PCs want is for papers which make progress on important problems. Now, you can do this either by (1) attacking existing open problems, or (2) by finding new important problems.
My earlier note aside, I think this is an extremely important point. It seems to support the idea that "impact" is hard to gauge but much easier when the community has already arrived at some form of consensus on the importance of a problem.
Ayup. It's too annoying to translate the academic speak, but you can shortcut it.
For example, anything CS nowadays (I include crypto in this) must be 1) publicly available on the web, 2) come with running code that runs some basic tests, and 3) be limited to a single compilable file. Failure in any of the criteria means I move on. If the source code involves anything like "configure" it's an immediate fail. If the code passes all three of those criteria, it's probably more useful to read the code rather than the paper.
I used to love ISSCC for the reason that they used to demand both A) a die photograph of a chip and B) actual oscilloscope traces. You can't hide when you have to make test equipment produce data. Sadly, they got rid of that requirement in the late 90's, and the information content of the conference suffered correspondingly.
What do you mean by this? Surely some things require some configuration. Don't they?
1) CS papers are normally about a single or logically-related set of concepts. If you can't reduce the code to a single file, the paper is probably too broad or you are trying to hide something.
2) If the author wants me to take time, it has to be really easy to try. "Configuration" is asking me to make choices that I really have no clue about a priori. Now, maybe there is a "heavy duty" version as well. But the "straightforward" version needs to be really straightforward.
And you would be surprised how often you don't need the heavy duty version. A nice example of this in crypto is DJB's "TweetNaCl". It gets you 99% of what you need until you understand what it doesn't get you. And, it's so damn easy to include that you get very little resistance--try using tweetnacl vs libnacl vs libsodium in a project. You'll pull your hair out if there isn't a magic package already for libsodium while tweetnacl can be dumped into embedded microcontrollers without pain.
3) If the author wants longevity, simplicity is his friend. Can you even begin to run a "configure" script from even 5 years ago let alone 10? Yet, I can download an ancient Fortran 77 code file and compile it today pretty easily.
Configuration is not your friend.
Academese exists because it works.
Length restrictions can be a bummer, but if you have a publishable result that you simply can't squeeze into 10-20 pages (depending on the venue), typically you split it in to two or more publications. This has the added advantage of ensuring that each published unit is a smaller, tighter piece of work. I don't think it's just pedantry.
I guess that's the advantage that tenured researchers have over everyone else--you can't run out of career before you published all of your papers.
None of my other publications have taken 10 submissions, so this case is also probably an outlier.
Moreover, there is level of subjectivity in peer review.
https://en.wikipedia.org/wiki/Carl_Sagan
I used to see this with my peers in computer programming in the 1990s. There was a lot of anger and jealousy when everyday normal people started putting up websites. Several of my CS friends were of the opinion that this was almost polluting the WWW with bad code.
Why didn't you place the additional detail in an appendix, so as to not detract from the main points?
(Also: The mathematical underpinnings are related to radar systems, whereas the application is in robotics. The amount of background information to bring a roboticist up to speed would've consumed entire papers or books -- some of which were previously published by myself & other coauthors.)
Curious. Which paper is this?
Direct pdf link: https://arxiv.org/pdf/1507.02373.pdf
I don't get why people would try to publish in high-tier venue. To me it seems much more about polishing one's ego instead of improving the research quality.
This is more about quick-polishing your image than your ego. ;)
Well I really enjoy reading articles from top-tier venues (PL theory). It means that committee does a good work filtering and improving articles, definitely not without mistakes.
I tried (twice!) to publish a paper that was scientifically sound, but written such that it could be understood by a lay audience. It was rejected; quoting a reviewer: "This paper lacks math." That sentiment made me lose a lot of faith in academia. Now, I simply refuse to contribute any more time to writing papers or performing peer review (esp. in non-open publications). I'm sure I'm not alone; I know of at least one "seminal" robotics paper that was rejected from top venues multiple times for "simplicity" (lack of mathematics content) that went on to become a foundational paper in the field after appearing in a lower-tier venue years later.
The irony: it takes researchers a lot of time to make a paper dense & concise. If they "showed all steps", it would probably improve researcher productivity & make the material more approachable to newcomers. Instead publishers enforce length restrictions... for which authors dedicate upto 25% to related work (some of which is useful; much of which is pandering to likely peer reviewers in small, niche fields). Length restrictions seem equally foolish in the age of digital publishing. And again, inadvertent pedantry is the only explanation I can imagine... but happy to be wrong.