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.

▲

pspeter3 22 days ago | parent | next [-]

What makes Golang a great fit in your opinion?

▲

zakirullin 22 days ago | parent | next [-]

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.

▲

voidnap 22 days ago | parent | next [-]

Using Go means you are forgoing Docker...? Ok.

Also if you don't need certbot anymore is your service managing its own ssl certs with letsencrypt? Isn't it generally easier to configure with a reverse proxy like nginx or caddy and terminate SSL at the edge? That's literally caddy's whole thing that it does SSL for you so that it doesn't concern your application.

▲

LinuxAmbulance 22 days ago | parent | prev | next [-]

That is a pretty strong argument for Go!

	▲	backscratches 22 days ago \| parent [-]
		This is the reason I like go and rust so much

▲

lioeters 22 days ago | parent | prev [-]

That's brilliant. Can't beat the convenience of a single-file executable!

▲

zakirullin 22 days ago | parent | prev [-]

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.

▲

pratikdeoghare 22 days ago | parent | prev [-]

You might like what I made for myself https://github.com/pratikdeoghare/brashtag