News for hackers. Stuff that matters.
Re:Ask HN: How to read CS papers? by WikiPaperGuy on Wednesday December 28, 2016 @09:33PM (#13275318)
Research papers are insanely hard to read.

I currently have a solution to try to fix this, it's still in pre-alpha stage:

www.wikipaper.org

If any HN'ers has time to help me I'd be much appreciative. This is a big problem and can't really be solved via commercial means, it can only work as an open-source project.

There's been many, many attempts to solve this problem in the past but all of them have been fairly limited in featureset & momentum. I currently have a solution to try to fix this, it's still in pre-alpha stage:

www.wikipaper.org

If any HN'ers has time to help me I'd be much appreciative. This is a big problem and can't really be solved via commercial means, it can only work as an open-source project.

There's been many, many attempts to solve this problem in the past but all of them have been fairly limited in featureset & momentum.

Re:Ask HN: How to read CS papers? by WikiPaperGuy on Wednesday December 28, 2016 @09:52PM (#13275371)
Here's the list:

- The lack of an ability to print videos/animations on a piece of paper. Oftentimes, complex concepts require a graphical animation (or video) to be succinctly conveyed.

- Papers are often written in a non-native tongue.

- Overly complex words or inappropriate words to appear more sophisticated. This doesn't necessarily correspond to field jargon.

- "Filler" material added in order to meet the page count recommendation... or conversely, trying to pack too much in.

- Authors not having the mindset of explaining complex details in a straightforward format.

- The "blowing up" of simple equations in order to make them look more complex.