ctopher7

I think we don't need to reinvent the wheel for handling user session, especially in web based application. There are common best practices that everybody already know such as using jwt, https and store in http only cookie

are you GPT3 ?

a little bit oot, but just installed tailscale on my dev stack (ec2, bare metal at home and my macbook air). mindblown by its simplicity and "it just works". Use it for logging purposes (ELK is too heavy for free tier ec2) and CI/CD (again, too heavy for my free tier ec2)

I don't hate go for the language itself. I understand the point of using go, especially if you have a company with hundreds or thousands of software engineer. It is really good for building microservices, because to me the learning curve is not steep hence everybody who just learn it, could already make contributions to the codebase.

what I don't understand are the fans who are really trying to overglorify go as "language of the future" that could be a C replacement.

why do you need to run SELECT with a transaction?

how about using rust in cloud native env?

I write in go for a living (my company uses it company wide) but I use rust for my personal project

never had the chance to compare both performance