Comment by zakirullin
9 hours ago
I believe that not only you should own your data in plain files, but also you should own the software that opens those files.
So that your files and tools can grow together, fully under your ownership, through the ages.
The app can be easily tweaked for your own needs via an LLM - code is optimized for that.
P.S. And Golang seems to be great fit for this kind of software.
What makes Golang a great fit in your opinion?
Server setup before the rewrite:
docker + php-fpm + php7 + larvel + nginx + redis + cron + worker + certbot
Server after the rewrite to Golang:
server, a 15MB no-dependencies binary that has everything.
That's brilliant. Can't beat the convenience of a single-file executable!
That is a pretty strong argument for Go!
1 reply →
Since I plan to use it for the rest of my life, I need the code and infrastructure to be radically simple and easy to maintain.
Like, I should be able to open it even after a few years, and do some fixes or add some features.
Go's ecosystem seems to share this mindset.
You might like what I made for myself https://github.com/pratikdeoghare/brashtag