2,303 karma · joined April 14, 2021
> is mmaping a file and using it directly from memory what databases should do today
Some do; for example, SQLite: https://www.sqlite.org/mmap.html (the page has pros and cons, and explains how SQLite does memory mapped I/O).
For Python specifically, PEPs are very helpful too: https://www.python.org/dev/peps/
_This_, so much.
If you are a heavy user of a language / library, it's immensely helpful to look at the release notes every once in a while. Even if you don't plan to upgrade now, it gives you an idea of where things are going (and may eventually tip the scales to a "fuck it, it's now worth upgrading" moment).
For Python specifically, PEPs are also a good way to keep track of what's happening (even if some of them don't get accepted): https://www.python.org/dev/peps/ ; there's also an RSS feed: view-source:https://www.python.org/dev/peps/peps.rss/
I'm Adrian, and I'd like to share a side project I've been working on for the past 3 years.
reader is a Python feed reader library – it takes care of the core functionality required by a feed reader, so you can focus on what makes yours different.
reader allows you to:
* retrieve, store, and manage Atom, RSS, and JSON feeds
* mark entries as read or important
* add tags and metadata to feeds
* filter feeds and articles
* full-text search articles
* write plugins to extend its functionality
Part of the reason for this project was to do the best work I could. I spent a lot of time thinking about the API, how to make it nice to use, and how to reduce the likelihood of breaking changes. I've also taken the time to make it maintainable long-term; to this end, the core library is fully typed and has 100% test coverage.
More importantly, I wanted to make a self-hosted feed reader web app – for privacy reasons, and so I can easily change stuff I don't like. The fact that I couldn’t find one extensible enough bugged me so much that I decided to make my own; a few years later, I ended up with what I would’ve liked to use when I first started.
https://reader.readthedocs.io/en/stable/#quickstart gives a quick tour of what the API looks like; the user guide has a more detailed feature-by-feature overview.
There's also a web app (which I use daily for feeds and podcasts); it's somewhat ugly since I don't really care for front-end stuff :) But that's kinda the point – if you want to build your own you can, and you only need to do that; the low level stuff is already taken care of.