Ask HN: What is your go-to stack for the web?
21–30 of 74 posts
Re: Ask HN: What is your go-to stack for the web?
#22React frontend
Re: Ask HN: What is your go-to stack for the web?
#23UI: Django templates, htmx, tailwind, vanilla js or hypersceript, no build, no node, no npm. Avoiding writing js as much as possible.
Background workers: RQ with 3 priority queues
Deployment: Kamal one command deployment with underlying docker
Hosting: Linode server with backups
Storage: Mounted volume on the machine (maybe s3 eventually).
Benefits:
* High speed of iteration
* No boilerplate mess
* No build therefore no dealing with dependencies and npm rabbithole
* Fast deployment with Kamal (a bit of learning curve but once up just works)
* Much cheaper compared to PaaS. At least 50%.
* Multiple websites on the same instance
Of course I know django quite well so the goal is to remove as much friction as possible.
Re: Ask HN: What is your go-to stack for the web?
#24Re: Ask HN: What is your go-to stack for the web?
#25Re: Ask HN: What is your go-to stack for the web?
#26Re: Ask HN: What is your go-to stack for the web?
#27Then we used a common and popular programming language to make them all work together.
It was compatible with everything. Worked everywhere. Interfaced with everything. And was as fast as hell.
No additional thinking or learning required.