Much prefer your stack, yours operates at a higher level of abstraction, the one which I would consider correct for web services (your website or REST api doesn't need to do syscalls, or allocate memory manually), while not sacrificing too much performance or simplicity.
This has become my go-to stack for playing around with for the last few months. Go/sqlite(bun)/templ/htmx with a sprinkle of proto-actors. Feels pretty close to phoenix framework with a few helper functions honestly but with the benefit of incredibly fast compilation of Go.
Single binary for distribution with assets/migrations embedded. Still need to build something substantial so I am sure there are edge cases/rough edges but so far it feels like a breath of fresh air compared to nodejs ecosystem.
Very interested in this too.. not clear at what point something like Postgres will become necessary.
Just writing a simple hello world in node/express downloads a gazillion dependencies and code that'll all be points of failure or mystery for lack of understanding. To understand them all to be able to write non trivial stuff is likely no different from doing httpd in c on Linux.
I've done stuff in go and it makes it lot easier to code.
doodlesdev|2 years ago
edvinbesic|2 years ago
Single binary for distribution with assets/migrations embedded. Still need to build something substantial so I am sure there are edge cases/rough edges but so far it feels like a breath of fresh air compared to nodejs ecosystem.
whalesalad|2 years ago
kopirgan|2 years ago
Just writing a simple hello world in node/express downloads a gazillion dependencies and code that'll all be points of failure or mystery for lack of understanding. To understand them all to be able to write non trivial stuff is likely no different from doing httpd in c on Linux.
I've done stuff in go and it makes it lot easier to code.