cli-aws VS invoicer

i dragged my feet on go for a long time. i also thought that skipping go and moving to rust was the play. a few years later, i still write python often, but i don’t build systems with it. python i now use like bash, to glue things together and automate random things. it’s a fantastic language and i will never drop it.

the verbosity of go is the biggest hurdle for a pythonista. the thought of giving up context managers, decorators, iterators, comprehensions, exceptions, coroutines, it’s unthinkable. in comparison go is ugly. your aesthetic mind screams in protest.

write go full time. dive in. as months pass, not only will those aesthetic objections fade, your mental model from python cleanly transforms to go. go is what mypy tried to be. the cost was aesthetic changes. the benefit is worth it.

the zen of python says if it’s easy to explain it might be a good idea. this is go, and it is.

i rebuilt a reasonably sized project from python[1] to go[2] over the last few years. i also have a system that i maintained both python[3] and go[4] implementations for, sharing a test suite in python.

go, like python, is fantastic. use both in whatever amount works for you. don’t read about them, build with them. you won’t regret it.

1. https://github.com/nathants/cli-aws/tree/bb78e529e7d1d3f95ac...

2. https://github.com/nathants/libaws

3. https://github.com/nathants/s4/tree/python

4. https://github.com/nathants/s4

https://github.com/DexterLagan/invoicer

A photo folder organization tool:

https://github.com/DexterLagan/invoicer

Last one I'd consider strictly personal would be Todo Master, an advanced todo with calendar, preset/macro facilities for generating dev reports and tons of other features only I would find a use for: