blob: 1be54b145f30b25185975b604b547964e9a39d20 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
---
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"
---
As you may have learnt from my previous posts (blog post and fedi posts), I'm
writing a client for [lotide][lotide] named [Luna][luna]. And you
might also have seen me saying it's using Django as framework and my remark on
it being unfitting. I am going to elaborate more on this in this post.
- Django: full-fledged, multi-app web project (view, model, db migration)
- 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).
[lotide]: https://sr.ht/~vpzom/lotide/
[luna]: https://pypi.org/project/lotide_luna/
|
