HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
burtonator
polar-bookshelf
HISTORICAL RECORD2018–2021
burtonator / polar-bookshelf · Not publicly available

polar-bookshelf

Discover this repository through its Hacker News conversations.

11Distinct people
20Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

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, 5:04:57 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 year20 dated mentions

Observed mentions: 2018-08-13 15:29:17 UTC to 2021-06-28 17:00:54 UTC.

02462018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC716
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC707
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

20 sources
I've migrated to Typescript and have been using it for about 2 years now. Maybe 1.5... TS is the best language I've used. It supports frontend and backend and strict typing and it's scalable so I can refactor and know that my code still works. The one thing its not good at is ML where Python is better but that's mostly because Python has better library support (not language design). Here's the deal. When dealing with a large amount of code 80% of your dev time is spent maintaining code - NOT writing new code. You can save a lot of time now writing new code and not using strict typing. OR you can spend a little bit of time now, maintaining your types, and save a MASSIVE amount of time later. > - TypeScript compile time when changing files takes several minutes, making continuous compiling an excruciatingly slow process I have a HUGE typ
Read the rest
escript repo and using a Macbook Pro from 2015... With --incremental and --watch my build takes like 5 seconds. About 1 minute on the first build then about 5 seconds after that. If your build is taking a long time - you're doing something wrong. > The internal code and runtime TypeScript declarations must be manually kept in sync since the TypeScript Compiler isn’t helpful to generate the d.ts files What? How? That doesn't make any sense. You're doing something wrong here. If all the code is in typescript, you have no additional work to do. If it's in JS you just have to write your own .d.ts files manually. Honestly it seems like this team just needs to sit down and understand how their tools actually work. The one issue where Typescript DOES kind of suck is when dealing with webpack, typemaps, and types. Many older projects just don't publish types and if you rely on them, and they refuse to publish types, you're going to be in a bit of pain. You can write your own types though and we've been doing this internally and for some repos just forking them so it's a bit easier to work with them. They usually lag on publishing their types. If you want to avoid all this pain you can just use webpack for your build system and Typescript for your code. We use lerna to build a multi-module system with --hoist to avoid duplicate dependencies. https://github.com/burtonator/polar-bookshelf ... is the project we're working on if you want to check it out. Our internal build system isn't fully published yet as we're in the process of reworking it but we're open source so you can take a look if you want.
In Deno will stop using TypeScript
We're getting there.. The backend supports it now. If you send me a list of your requirements (just create a github issue here https://github.com/burtonator/polar-bookshelf/issues) I will look at adding the functionality you need. We're adding support for DOI lookup and APIs like Arxiv so you could just add a DOI to polar and it will fetch the PDF and keep the metadata. Will also support export to bibtex too. Our big focus right now is shipping 2.0 so that we have a more modern platform that can scale us moving forward.
In Zotero: Personal Research Assistant
Typescript is absolutely amazing. I've been working with it for the last 8 months. https://getpolarized.io/ and the source is here: https://github.com/burtonator/polar-bookshelf I could have NOT made as much progress just by using JS directly. When you have a large code-base and you're trying to make progress as fast as possible refactoring is needed and the strict typing is invaluable. Honestly, the MAIN issue with TS are issues around webpack + typings for 3rd party and older modules. I'd say 85% of the code I want to use already has types but when they don't it's frustrating to have to pause and write my own types. I have 20 years of Java experience. Used it since 1.0 and for the most part have been unhappy with everything else. I've decided that Node + Typescript is by far the most productive environment for me to switch to. I can co
Read the rest
de elegant apps with both front and backends and I get strict typing. Could NOT have made so much progress without TS.
In Google Feedback on TypeScript 3.5
Also, wanted to thanks all you guys for reviewing Polar and there's a lot of good feedback here. In a nutshell: 1. I'm working on more document formats including Markdown and ePub. 2. I'm working on some preliminary support for reference management so we can lookup the full reference info via DOI and have reference formatters for you to use for your research. Some of the DOI storage is already done. 3. I'm working on a webapp and mobile support. Probably a month away. 4. The captured web content isn't actually converted to PDF - it's actually a cached web archive. Full HTML is kept in your repo. 5. Polar 2.0 will be more web aware. You can annotate anything without actually having to store the full thing in Polar. We will just store a URL. 6. Pagemarks will be improved her shortly so you can toggle them on and off and possibly even hig
Read the rest
hlight through them directly. 7. There are definitely small bugs and fit and finish issue we're working on. If you have an issue please report it: https://github.com/burtonator/polar-bookshelf/issues 8. Yes. Polar isn't fully self hosted but that defeats the point. My cure hypothesis is that knowledge benefits from being social which is the main thing I'm trying to test. By the time I'm done I think 95% of you would agree that keeping it private is insane as you don't benefit from the community. 9. If you like Polar please consider donating. https://opencollective.com/polar-bookshelf ... we've received essentially zero Open Source contributions from the community and very little funding.
In Polar as a Personal Knowledge Repository

Showing the 15 most recent of 20 sources. Enable JavaScript to search and browse every indexed mention.

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.