HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sumatrapdfreader
sumatrapdf
C2016–2026
sumatrapdfreader / sumatrapdf

sumatrapdf

SumatraPDF reader

12Distinct people
21Mentions
0Explicit recommenders
18KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

SumatraPDF reader

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year21 dated mentions

Observed mentions: 2016-03-10 03:16:00 UTC to 2026-04-14 13:51:49 UTC.

024682016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC817
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

What Hacker News says

1 sources
It's probably much less awesome than you think it'll be. The biggest problem working solo (open source or not) is motivation. Many people find it really hard to do the work without the external pressure of bosses and co-workers. Search HN for freelancing thread for some harsh truths. It seems like you plan to contribute to someone else's projects, which is the worst of both worlds. When I do open source (e.g. https://github.com/sumatrapdfreader/sumatrapdf), the biggest advantage is that it is my project, I'm the boss and I make all the rules. I get to decide what is done and how it'll be done. Contributing when other people have a veto over what you do is like having a boss without the benefit of paycheck. For example, recently I noticed a few improvements I could make to libuv. But then I saw how many PR are languishing for days if not w
Read the rest
eeks (https://github.com/libuv/libuv/pulls) and decided I'm not even going to bother. And this is a well known, active project that is better than most at accepting people's changes. I could give you examples of projects with many outstanding PRs without even a comment from the owner. Certainly don't do it if you don't have a project of your own to work on. Possibly don't do it even if you do have a project to work on. You can start by working on open source in your free time. You also didn't mention anything about money - are you independently wealthy to even be able to afford writing code without someone paying you? Roughly speaking, there's no money in open source. As to learning - how much you learn is more about how intentional you are about learning and how you go about it rather than whether you work or do open source. At the very least, you'll learn different things.
In Ask HN: Working on open source full-time vs at a fast growing product company

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.