All Questions



What’s everyone’s tech stack?

author James Trimble

Reply
15 Answers

Stackoverflow

writen by Benedikt

Na, kidding, mainly Rust, nginx, docker, PHP, some Javascript or svelte and tailwindcss. Forgot the databases: flat files, SQLite, sometimes MySQL and PostgreSQL

writen by Benedikt

I don’t like to stick to something, but I always end up with Typescript, Node, Supabase, React and React Native. Sometimes Python for complex logic.

writen by Bartolomeu Rodrigues

I usually use PHP+MySQL with some front end like React,Angular or just Knockout or jQuery. I bought Marc Lou’s boiler plate though so I’ll probably try working with that some and see how I like it.

writen by James Trimble

I use Django, Python, PostgreSQL, ReactJS or jQuery, TailwindCSS or Bootstrap, SCSS, nginx, Ansible.

writen by Aidas Bendoraitis

Next.js (on Vercel), Typescript, Postgres (AWS RDS)

writen by Kirill Rogovoy

My tech stack of choice is Laravel, Vue JS and Tailwind. In my day job we also have a React project and a Node project, but for most things we use my preferred stack.

writen by Philip

For database I usually use MySQL, but for my day job we’ve started moving to Postgres as we do a lot of stuff with PostGIS.

writen by Philip

Typescript, Nextjs, ChakraUI. Auth NextAuth for web only projects, Firebase for web and mobile. AWS for lambda functions scheduling. DigitalOcean for PostgreSQL. Render for a nodejs server app easy and quick to start.

writen by Luca Restagno (ikoichi on Twitter)

Luca Restagno (ikoichi on Twitter) Kirill Rogovoy Do you use NextJS for creating API endpoints? I thought NextJS was used for creating static sites, but since your products are dynamic, I probably am misunderstanding the power of NextJS

writen by Philip

WordPress, Airtable, Make/Zapier, Tally

writen by Maxwell Davis

Philip both website and api (via Zod)

writen by Kirill Rogovoy

Philip the nice thing about NextJS is that you can create the frontend and the backend in one single code base. The backend is basically made of serverless functions / endpoints that live close to your frontend, server-side rendering, or statically rendered. Super cool. Of course, it comes with the limitations of serverless (mainly cold start, and execution timeout).

writen by Luca Restagno (ikoichi on Twitter)

Thanks Luca Restagno (ikoichi on Twitter) and Kirill Rogovoy. Thanks for your explanations. It’s definitely a framework that I want to explore more.

writen by Philip

Pythong+react+gcp+netlify

writen by Tiago Ferreira

Do you want to ask a question?


Related Questions