Finish post

1 files changed, 8 insertions, 11 deletions

diff --git a/content/posts/2022-01-31-luna-django.md b/content/posts/2022-01-31-luna-django.md
index 7386396..dfa3817 100644
--- a/content/posts/2022-01-31-luna-django.md
+++ b/content/posts/2022-01-31-luna-django.md
@@ -2,7 +2,6 @@
 title: "Using tools with appropriate ability"
 date: 2022-01-31
 lang: en
-draft: true
 categories: [ blog ]
 tags: [luna, django, decision, tools, "use cases"]
 translationKey: "luna-django"
@@ -58,7 +57,8 @@ It doesn't need database handling, or administration, or emailing.  I would
 definitely have no use for most, if not all of `djangoadmin` and `manage.py`
 commands.
 
-Django would be an overkill for Luna.
+Django is an overkill for Luna.  Using a big tool for small task feels very
+clumsy, with all the tools you won't use and tools that you *have to* use.
 
 ## Alternatives
 
@@ -67,14 +67,11 @@ As I get quickly annoyed with the generated `manage.py` and the lengthy
 while, and am planning to drop development if no one else is taking over.
 
 I have also tried to rewrite it in Go, but it seems internationalization
-support for Go is quite lacking.
-
-- Luna: just a frontend (just the view part)
-- overhead (a lot of setting)
-- origin: trying out stuff
-  - try out golang
-    - golang internationalization support feels lacking
-  - back to flask/quart for [Yue][yue], since Jinja supports internationalization well
-    - can use it for back end of another app (pandict).
+support for Go is quite lacking. So, I backed to a more familiar stack using
+Quart (with better support for asynchronous programming, though it might be
+another overkill) and Jinja (which has somewhat matured internationalization
+support) and renamed it to a less common name ([Yue][yue]) to avoid name
+conflict which led me to call Luna's package `lotide_luna`.  I'm less motivated
+than before, and also have less time, so this will move much more slowly.
 
 [yue]: https://sr.ht/~huyngo/Yue/