step 1: ask yourself, why am i writing a package manager where there are like 56 other ones out there
step 2: ok but really, is that a good enough reason
step 3: really?
step 4: no, it’s not, stop
step 5: There are now 57 other ones out there lol
First paragraphs in the article
Writing a package manager is not one of the most common programming tasks. After all, there are many out-of-the-box ones available. Yet, somehow I’ve found myself in exactly this situation.
How so?
I’m a big fan of SQLite and its extensions. Given the large number of such extensions in the wild, I wanted a structured approach to managing them. Which usually involves, well, a package manager. Except there is none for SQLite. So I decided to build one!
Having a reason is not the same as having a good reason.
Hence my facetious “but why?” (I had read the article - they don’t justify it well).
