diff options
author | EuAndreh <eu@euandre.org> | 2023-11-09 07:14:01 -0300 |
---|---|---|
committer | EuAndreh <eu@euandre.org> | 2023-11-09 07:14:01 -0300 |
commit | b77d895cd6dc6316ea6f2f7e783bd5b334c00f5c (patch) | |
tree | 14bc8a6099f71f432213de6d9a5ec33766cc68ad | |
parent | TODOs.md: Add #td-faae1d8e-4015-cb78-0fe9-d003428266c9 (diff) | |
download | papod-b77d895cd6dc6316ea6f2f7e783bd5b334c00f5c.tar.gz papod-b77d895cd6dc6316ea6f2f7e783bd5b334c00f5c.tar.xz |
TODOs.md: Add #td-1045dbb9-fd89-e254-3e9d-642cb112c6ad
-rw-r--r-- | TODOs.md | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -12,6 +12,24 @@ # Decisions +## TODO Encubate dependencies than move them out {#td-1045dbb9-fd89-e254-3e9d-642cb112c6ad} +- DONE in 2023-11-09 + +--- + +In order to achieve the reliability and robustness targets I have, and to build +something that I'd want to personally use deploy, I'll need as few dependencies +as possible. So as papo gets built, I'll need miniscule libraries for web +routing, WebSockets, etc., and as I write those inside papo itself, I'll +eventually pull them out as standalone dependencies. + +So the apparent number of dependencies may seem to grow, but only because +they're being separated from papo itself, so that this repository contains code +relating to chat things, and infrastructure things go to their own repository. +Also despite the apparent dependency count growth, these dependencies are being +bu8ild alongisde papo and with its robustness, reliability and correctness +standard from the beginning, so the mismatch in quality is not a concern. + ## DONE Assume Node.js {#td-faae1d8e-4015-cb78-0fe9-d003428266c9} - DONE in 2023-11-09 |