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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 11:20:21 AM 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

5 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

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.