> That is a big problem tho, because it means journalists can't understand the papers. ...
When I thought about this, I immediately thought of a "TL;DR" section for any academic paper... until I realized that that's what the Abstract / Conclusion is sort of meant to be.
> ... the majority of academic CS papers are opaque and inaccessible like most other academic papers I've read.
The majority of CS papers' Abstract / Conclusion are also quite 'opaque and inaccessible'. Having gone through a fair share of CS papers myself (being a part of CS research), trying to get into a new area of CS is really hard when I try to read more recent academic papers, not just because of the technical jargon involved, but because of the unnecessary complex sentences that are required to convey the author(s) idea. A lot of things could be made simpler and easier to grasp. I largely agree with "it is helpful for people to bring this up and make people (especially people in academia) realize that this is a bigger problem than they think."
When I thought about this, I immediately thought of a "TL;DR" section for any academic paper... until I realized that that's what the Abstract / Conclusion is sort of meant to be.
> ... the majority of academic CS papers are opaque and inaccessible like most other academic papers I've read.
The majority of CS papers' Abstract / Conclusion are also quite 'opaque and inaccessible'. Having gone through a fair share of CS papers myself (being a part of CS research), trying to get into a new area of CS is really hard when I try to read more recent academic papers, not just because of the technical jargon involved, but because of the unnecessary complex sentences that are required to convey the author(s) idea. A lot of things could be made simpler and easier to grasp. I largely agree with "it is helpful for people to bring this up and make people (especially people in academia) realize that this is a bigger problem than they think."