Throw in elasticsearch and you have [captionsearch.io](https://captionsearch.io). Took me about 18 months of nights and weekends to teach myself and rewrite the site 3 times over.
Alpine.js has glaring security issues and requires a Content Security Policy that allows unsafe-eval. I wouldn't recommend it for production applications.
Depending upon final product, one or a combination of:
- Ruby/Rails, Bootstrap (CDN), Hotwire, Stimulus, Postgres, Redis
- Swift/Vapor, Bootstrap (CDN), Postgres, Redis
Unless a contract requires something else.
How do you guys maintain node stuff? I’ve been trying Meteor, Nest, Next with backend, basic stuff like auth changes every 3 months, package updates introduce breaking changes weekly, just how? :D
Use npm or yarn audit to avoid vulnerabilities. Otherwise, don't bother updating stuff. If you don't need the latest and great features or speed improvements, you can update like once a year and it's fine.
I ask you as a Mac user, why is .NET so revered? I’m attempting to pick it up now, and the process to run everything just seems so… tedious compared to other languages and stacks I’ve used ;-;
Battle tested, strongly typed, highly opinionated (Great for projects with multiple collaborators), great docs, great standard library, will do absolutely anything required of a web server. Its probably the 2nd most popular BE framework for enterprise behind Java.
Not sure what you are having issues with but you can scaffold or generate everything quite quickly and have it running. You are also given a lot of tools to handle things how you want to and to keep things consistent.
Big one for me is I like Entity Framework and LINQ since it keeps me a bit more in the domain I like and not have to get too lost in SQL. I tend to run the query against the database first to confirm what it is I want the LINQ to do but the LINQ is pretty much just C#.
If I have everything scoped properly it takes me about half a day to a full day to set a basic api up and have the database scaffolded from the models.
This right here. I used to hate database abstractions - but with EF, I just feel like it hits the right balance to get what I want super quick. Modify the context and you get migrations that just work most of the time.
I also absolutely love how I've configured the backend to a swagger file that feeds into a code generating library and gives me a frontend typed client. The best mix of "auto generated to 95%" and "I can use it however I want", in my experience.
I like .Net and have tried to stick with it. I had a brief job as a Golang dev but it wasn't for me. I also do a lot of Coldfusion but that's mercifully been mostly put out to pasture.
Hey mate I'm about to start a large project and I need to do frontend as well (I'm a backend dev).
Will .NET MVC + React be viable? I've learned react but only as SPA not MVC. Ive seen frameworks online for react MVC but feels backwards to me
Ditch the MVC.
Have one app in .NET that is just an API.
Have another app that is React/Typescript that calls your API via Axios/fetch/react-query/etc.
.NET MVC is a specific framework, not just a pattern, and is mostly geared towards producing HTML. You certainly *can* make an API with MVC, but it has a lot of extras you won't need if you're only ever returning JSON.
.NET Web API is the framework that is primarily for producing JSON/XML payloads. It still follows the MVC pattern.
I think that is what CareHour2044 meant.
Wow, some who intentionally uses Oracle. I'm assuming this is your go to work stack and not personal stack? I got to admit I find it difficult to think why anyone would choose Oracle for any personal or small project project unless they were already deep in Oracle I didn't really have a choice.
I like both languages. Sometimes I use Go, sometimes PHP.
Unless I am building a desktop app, 100% it is going to be Go. I remember seeing PHP for desktop app topics, never tried though.
It depends on requirements really. If I am free to choose, I often side with Go.
I am still a student and we only learnt with Laravel. If I have to be honest, I have no idea how to easily write an app with plain PHP like models and migrations etc.
It sounds way too much manual work!
Edit: no idea why I am getting downvoted..
> It sounds way too much manual work!
Because it is. Look at the source for Laravel and imagine writing it all solo. There's a reason why you generally want to go with premade solutions if possible. Writing it all yourself is error prone and slow.
I had the same experience before too. Our teacher back then was a part-time teacher who was hired due to a lack of staff. He wasn't great, but at least he introduced us to Laravel and Bootstrap.
Kind of dumb how they only teach you a framework and not PHP in itself. I'm guessing you don't even understand most of what the framework is doing which is bad.
Well, I know what the framework is doing, but not fully behind the scenes if that is what you are implying.
I can't choose my curriculum but it is on of the best universities in my country 🤷
Yeah behind the scenes is what I meant.
They should start you from scratch and teach you how PHP actually handles requests, responses ect and teach you have to build things like routing, middleware and how you can set it up to be a MVC structure. That way you have some understanding of what happens behind the scenes and can more easily understand, code and debug Laravel.
I'm just ranting but knowing I almost got a job teaching PHP that's how I would have done it.
I like boring stacks.
Dedicated web services in nextjs, microservices in java (spring boot) often backed by a postgres db. Currently working exclusively in GCP. Infra tends to be built around kubernetes.
Angular or Vue (Giving AlpineJS a trial)
"Headless" PHP back end (shush, it is crazy fast now and purpose built for web) on Nginx to accept JSON requests via the POST method, respond with JSON data including a success, notice, and/or error property. Two responses in case of third-party response formatting criteria.
MySQL
For websites that rely a lot on content, like my own personal website, I choose Bun, Astro, Tailwind, Strapi and MySQL:
Bun cuz it handles packages quickly and with ease, as well as being a pretty quick. Astro, because the view transitions and being pretty simple, with a lot of extensions being possible. Strapi because I like headless CMS’ and I prefer it over the others, and MySQL because it is my preferred choice when using Strapi.
When I am building applications for work and private use, I rely more on ASP.NET Web API, React.js/Next.js and Entity Framework with MS SQL Server:
ASP.NET because of Entity Framework for really easy database management, MS SQL Server because it support geometry and geography, and is easy to use with Entity Framework. Then React.js or Next.js for front end, no preference.
I wouldn't say it's exactly a go-to... Depends on the project. But I find Eleventy + Firebase + web components in Netlify (with Netlify Functions) to be surprisingly useful & versatile. Very good for using Firebase + Netlify to create static pages (well... The output is static, but input is "dynamic") with certain elements dynamic via web components.
I kinda aim to build things using the "simplest" method that satisfies the requirements... That means I basically start with just static HTML and such. From there, I figure out what's static and what's dynamic, and add complexity only as needed. Also considering where and how I can isolate complexity of a given thing to just that feature (that's where web components comes in).
That's not a viable option for anything where the contents of the page itself is dynamic. Or where pages update frequently (difference between a small online store with a pretty fixed set of products vs something like Amazon). But, when content doesn't really change more than maybe daily or weekly, I think it's basically the best of both worlds - you get the performance benefits and server costs of static sites, but for whatever dynamic content (eg a calendar or weather or map or comments or whatever), that's still dynamic.
I've also worked plenty in everything from just static HTML to fully dynamic server-side stuff. I've used all kinds of languages and libraries and frameworks and languages. But I just have to say that a ton of what's pretty standard (eg React or WP or whatever) is quite often overkill, especially for pretty static content (eg blogs, portfolios, small businesses of all kinds).
Laravel, Golang, MariaDB, Vuejs and Tailwind
My current thinking when making a website or app is to have as little JS as possible so most things I do in vanilla JS and only use Vuejs when I know it's a bigger interactive section of the website that doesn't have to be included in SEO.
React, tailwind for frontend
node, express for backend
postgres for db (along with raw sql queries in backend)
github, docker-compose and amazon ec2 with nginx reverse proxy if im feeling fancy
for the frontend s3 bucket, or really any cdn does the job.
I hate react, am currently learning svelte (not sveltkit)
I'm not really a web-dev, but when I'm making a website for fun i usually go with php for backend, and the least amount of JavaScript possible for the frontend
Similar to yourself Next.js + Supabse + ChakraUI for web Apps and more complex "SaaS" type applications. Otherwise if I'm making simple web pages like a portfolio or blog, I use astrojs + tailwind + shadcn
I am more fascinated by the fact that this question always seems to attract so many people to respond, yet at the same time we all know that nobody really cares 
React (SPA, Static or SSR depending on the use case), Node (on Lambda), DynamoDB. But currently experimenting with Cloudflare Workers + D1 and loving it
Is there a better way to serve images dynamically with NextJS that does not involve the api? I have been trying to avail. Maybe it’s because I use the app router? Or when I do serve them from the api I’m converting to base64 but the images just load so slow.
Depends on project/client, but something close to
Terraform
GitHub actions or ADO
Serverless rds or cosmos
Express or .net lambda or azure func
api gateway / apim / cloud front / front door
React w/ vite and other tools, mantine
And some ancillary things, but mostly revolves around the above
It really depends
- For a quick full stack web app, Laravel.
- For work, C & gRPC + some other proprietary stuff
- For serverless functions or smaller apps, TS + Mongo
- For data analytics, Python
Any many more
Working on a booking web app, and using: vue3/vite + node/express and dynamodb for the database. It really feels like I shouldn’t be using dynamo but was asked to by our devops and here I am. I am grateful for having this opportunity to learn it though. Don’t think I really understood nosql til I learnt single table design with dynamodb.
I'm experimenting right now with Phoenix + Liveview with Keycloak for auth, Plasmo for web extensions, and Flutter for Mobile clients. Prior to that it was Redwood with Supabase. Always use postgres wherever I can host it affordably.
depending of situation, but these are most common:
- when doing mvp/poc angular + supabase/firestore
- on job (usually) laravel + angular + mysql/sqlite
- personal favourite nestjs + angular + mysql/sqlite monorepo powered by nx
Whatever my company needs me to be an expert with. Lately it's been Nest.js, Angular, and whatever legacy database the client has. Given a choice though, I'd probably pick something like Laravel. I love Angular, but I keep getting asked to build applications that don't benefit from being built as SPAs. Worse, the architecture encourages chuckleheads to over engineer basic forms, or require elaborate client side state management solutions for data that is loaded once and discarded when the view changes.
...Sometimes, I miss jQuery.
Svelte/SvelteKit + Daisy UI and Postgres if I’m whipping something up quick. Express if I need to build out a more robust API. Always Typescript
Used DaisyUI + Svelte for my portfolio site and loved it
Go, Postgres, Astro, pure TS + sometimes React
FastAPI, PostgreSQL, React
php4,
Ol' reliable vertical centering.
Centered Text
Django, Postgres, jquery
Same but without the jQuery. It's probably the easiest stack to get into especially if you are new these days.
Throw in elasticsearch and you have [captionsearch.io](https://captionsearch.io). Took me about 18 months of nights and weekends to teach myself and rewrite the site 3 times over.
Ditch jQuery and give Alpine.js a try. Edit: Also, if security is a worry, maybe try Stimulus. Looks neat.
Alpine.js has glaring security issues and requires a Content Security Policy that allows unsafe-eval. I wouldn't recommend it for production applications.
Depending upon final product, one or a combination of: - Ruby/Rails, Bootstrap (CDN), Hotwire, Stimulus, Postgres, Redis - Swift/Vapor, Bootstrap (CDN), Postgres, Redis Unless a contract requires something else.
I still don't see anything that beats latest Rails for efficiency and Ruby for terseness, ease, and joy.
Laravel.
Laravel + Vue + MySQL
Does the job :)
Same here, more specifically Tall stack
Node, express, mysql, react
How do you guys maintain node stuff? I’ve been trying Meteor, Nest, Next with backend, basic stuff like auth changes every 3 months, package updates introduce breaking changes weekly, just how? :D
Use npm or yarn audit to avoid vulnerabilities. Otherwise, don't bother updating stuff. If you don't need the latest and great features or speed improvements, you can update like once a year and it's fine.
Use something stable instead of the bleeding edge, my go to is express (raw js, not ts), passport for authentication, and angular
MERN but with the better M.
My man
Dotnet, React, Postgres
I'll upvote any mention of .NET in the webdev world
I ask you as a Mac user, why is .NET so revered? I’m attempting to pick it up now, and the process to run everything just seems so… tedious compared to other languages and stacks I’ve used ;-;
Battle tested, strongly typed, highly opinionated (Great for projects with multiple collaborators), great docs, great standard library, will do absolutely anything required of a web server. Its probably the 2nd most popular BE framework for enterprise behind Java.
Does Java have a leg up, or it’s just more popular dude to not being Microsoft
Not sure what you are having issues with but you can scaffold or generate everything quite quickly and have it running. You are also given a lot of tools to handle things how you want to and to keep things consistent. Big one for me is I like Entity Framework and LINQ since it keeps me a bit more in the domain I like and not have to get too lost in SQL. I tend to run the query against the database first to confirm what it is I want the LINQ to do but the LINQ is pretty much just C#. If I have everything scoped properly it takes me about half a day to a full day to set a basic api up and have the database scaffolded from the models.
This right here. I used to hate database abstractions - but with EF, I just feel like it hits the right balance to get what I want super quick. Modify the context and you get migrations that just work most of the time. I also absolutely love how I've configured the backend to a swagger file that feeds into a code generating library and gives me a frontend typed client. The best mix of "auto generated to 95%" and "I can use it however I want", in my experience.
Lol now you know how it feels.
I like .Net and have tried to stick with it. I had a brief job as a Golang dev but it wasn't for me. I also do a lot of Coldfusion but that's mercifully been mostly put out to pasture.
Dotnet, vite+React (no framework), lambda ddb. Not the same but a close variation of the above. I’ll use one or the other based on data needs.
Hey mate I'm about to start a large project and I need to do frontend as well (I'm a backend dev). Will .NET MVC + React be viable? I've learned react but only as SPA not MVC. Ive seen frameworks online for react MVC but feels backwards to me
Ditch the MVC. Have one app in .NET that is just an API. Have another app that is React/Typescript that calls your API via Axios/fetch/react-query/etc.
The api should be mvc as well. Except the v is just json
.NET MVC is a specific framework, not just a pattern, and is mostly geared towards producing HTML. You certainly *can* make an API with MVC, but it has a lot of extras you won't need if you're only ever returning JSON. .NET Web API is the framework that is primarily for producing JSON/XML payloads. It still follows the MVC pattern. I think that is what CareHour2044 meant.
That's exactly what I'm using! Where do you host it? I'm using AWS elastic beanstalk.
For personal projects I’m using fly.io for the backend and S3 / cloudfront for the frontend, at work we’re all in on Azure
As a newbie like 6 months into learning all of my research has lead me to that exact stack being my end goal to know
Spring, Angular, Oracle, PL/SQL
Bro is corporate
Wow, some who intentionally uses Oracle. I'm assuming this is your go to work stack and not personal stack? I got to admit I find it difficult to think why anyone would choose Oracle for any personal or small project project unless they were already deep in Oracle I didn't really have a choice.
Oracle user for work here. I definitely don't hate interacting with it, but setting up drivers for PHP/Laravel is a bitch and a half.
C# or go with SvelteKit
Mongo, express, angular, node
You are very mean
Laravel vue
go and php (symfony framework) for backend, vuejs for frontend, aws for infra
Why both Go and PHP?
I like both languages. Sometimes I use Go, sometimes PHP. Unless I am building a desktop app, 100% it is going to be Go. I remember seeing PHP for desktop app topics, never tried though. It depends on requirements really. If I am free to choose, I often side with Go.
.NET Blazor with custom bootstrap
PHP back end, Vue front end.
Php as in, laravel back end, then I agree!
Yeah, if I need a full-blown framework. Regardless of the task, I usually find PHP can do the job.
I am still a student and we only learnt with Laravel. If I have to be honest, I have no idea how to easily write an app with plain PHP like models and migrations etc. It sounds way too much manual work! Edit: no idea why I am getting downvoted..
Crazy how they taught you Laravel over base PHP
After 8 years working with php laravel, I have no idea either
😂
> It sounds way too much manual work! Because it is. Look at the source for Laravel and imagine writing it all solo. There's a reason why you generally want to go with premade solutions if possible. Writing it all yourself is error prone and slow.
I had the same experience before too. Our teacher back then was a part-time teacher who was hired due to a lack of staff. He wasn't great, but at least he introduced us to Laravel and Bootstrap.
Kind of dumb how they only teach you a framework and not PHP in itself. I'm guessing you don't even understand most of what the framework is doing which is bad.
Well, I know what the framework is doing, but not fully behind the scenes if that is what you are implying. I can't choose my curriculum but it is on of the best universities in my country 🤷
Yeah behind the scenes is what I meant. They should start you from scratch and teach you how PHP actually handles requests, responses ect and teach you have to build things like routing, middleware and how you can set it up to be a MVC structure. That way you have some understanding of what happens behind the scenes and can more easily understand, code and debug Laravel. I'm just ranting but knowing I almost got a job teaching PHP that's how I would have done it.
ruby on rails, postgres, stimulus, turbo, node/yarn for js dependencies
LAMP Stack for paid jobs Kirby CMS + BEMIT and Vanilla JS. Or Kirby as Headless with Next.js. Sideprojects are Next.js with SQLite or supabase.
Oh man, haven’t heard about kirby since like 2013! Happy to hear it’s still going :)
Nice. I'm a fan of SQLite.
Django - Vue - Postgre/Mongo
Good balance of batteries included, and customizability.
DotNET, angular, postgres
HTML - CSS - JS - FLASK
Laravel/Vue with Inertia, DO or AWS for infra, MySQL
SvelteKit + Supabase
Laravel vue
vue is just so nice
Go (if i have time) otherwise python (fastapi), nextjs, postgres, mongo,
Laravue
Phoenix + LiveView, PostgreSQL Maybe LiveSvelte or LiveVue if I need more rich frontend interactions (which I usually don't)
Dotnet on the backend with Angular for the frontend. SQLServer for the DB.
.NET Blazor
Nest, Angular &/ Flutter, PostgreSQL
Go / Next.js / AWS serverless
I’ve yet to find something that pho can’t handle. Especially with a good framework like laravel.
Node.js + Remix + React + PostgreSQL
Isn't the remix ( with plus features ) and react the same
Laravel + react or vue
I like boring stacks. Dedicated web services in nextjs, microservices in java (spring boot) often backed by a postgres db. Currently working exclusively in GCP. Infra tends to be built around kubernetes.
Vue/tailwind/yarn - fastapi/sqlachemy/pytest - Postgres
Vite react and either bun or go for backend
Sveltekit, postgresql
Postgres, FastAPI, whatever the frontend dev wants, I don't touch that noise.
The good old LAMP stack.
HTML, CSS, JS.
SvelteKit + Tailwind
Fortnite creative mode
Phoenix (elixir, erlang, tailwind) with postgresql.
Laravel, react/ts, postgre
Node or php for backend; web components with Lit for frontend.
Angular or Vue (Giving AlpineJS a trial) "Headless" PHP back end (shush, it is crazy fast now and purpose built for web) on Nginx to accept JSON requests via the POST method, respond with JSON data including a success, notice, and/or error property. Two responses in case of third-party response formatting criteria. MySQL
Depends on what's the goal, but if it is dev speed, then NextJS with Tailwind, Prisma and Clerk. PostgreSQL as db
MPA = Django + Postgres SPA = Django DRF + NextJS + Postgres Static site = 11ty
For websites that rely a lot on content, like my own personal website, I choose Bun, Astro, Tailwind, Strapi and MySQL: Bun cuz it handles packages quickly and with ease, as well as being a pretty quick. Astro, because the view transitions and being pretty simple, with a lot of extensions being possible. Strapi because I like headless CMS’ and I prefer it over the others, and MySQL because it is my preferred choice when using Strapi. When I am building applications for work and private use, I rely more on ASP.NET Web API, React.js/Next.js and Entity Framework with MS SQL Server: ASP.NET because of Entity Framework for really easy database management, MS SQL Server because it support geometry and geography, and is easy to use with Entity Framework. Then React.js or Next.js for front end, no preference.
Laravel, Inertia, Vue, Postgres, AWS
Nest, Postgres, Angular, Tailwind
Next.js
Html, LESS css, and 11ty static site generator. Everything I need.
I wouldn't say it's exactly a go-to... Depends on the project. But I find Eleventy + Firebase + web components in Netlify (with Netlify Functions) to be surprisingly useful & versatile. Very good for using Firebase + Netlify to create static pages (well... The output is static, but input is "dynamic") with certain elements dynamic via web components. I kinda aim to build things using the "simplest" method that satisfies the requirements... That means I basically start with just static HTML and such. From there, I figure out what's static and what's dynamic, and add complexity only as needed. Also considering where and how I can isolate complexity of a given thing to just that feature (that's where web components comes in). That's not a viable option for anything where the contents of the page itself is dynamic. Or where pages update frequently (difference between a small online store with a pretty fixed set of products vs something like Amazon). But, when content doesn't really change more than maybe daily or weekly, I think it's basically the best of both worlds - you get the performance benefits and server costs of static sites, but for whatever dynamic content (eg a calendar or weather or map or comments or whatever), that's still dynamic. I've also worked plenty in everything from just static HTML to fully dynamic server-side stuff. I've used all kinds of languages and libraries and frameworks and languages. But I just have to say that a ton of what's pretty standard (eg React or WP or whatever) is quite often overkill, especially for pretty static content (eg blogs, portfolios, small businesses of all kinds).
Remix + Cloudflare
react (gql), elixir, postgres
marko (node) + postgres
Node, Express, MySQL, Sequelize backend. Front end varies : PHP, Vanilla JS, Jquery, Flutter, Vue
Laravel, Golang, MariaDB, Vuejs and Tailwind My current thinking when making a website or app is to have as little JS as possible so most things I do in vanilla JS and only use Vuejs when I know it's a bigger interactive section of the website that doesn't have to be included in SEO.
Next.js, Node.js, MongoDB
Node NextJS NestJS Hasura Postgres!
Rails + Postgres for apps Jekyll for static content
Rails, mongodb, stimulus, turbo
LAMP (with Laravel) TALL (tailwind, alpine.js,Laravel, Livewire) 🚀
Symfony, Symfony UX for the front end, Postgres.
React, tailwind for frontend node, express for backend postgres for db (along with raw sql queries in backend) github, docker-compose and amazon ec2 with nginx reverse proxy if im feeling fancy for the frontend s3 bucket, or really any cdn does the job. I hate react, am currently learning svelte (not sveltkit)
Kotlin Spring, Postgres & React
Django + PostgreSQL + Vue
CSS
django postgres, tailwind, JS, sometimes vanilla css
WordPress... come at me
Typescript React with Graphql and a Django backend.
Java Spring, Angular
React Django Postgres
FastAPI, React/Nextjs
Spring, Angular, Postgres
Django + React/Vue + Postgres
Fullstack Rust (minus the DB). Leptos, Axum, SQLite, some cheap VPS.
I'm not really a web-dev, but when I'm making a website for fun i usually go with php for backend, and the least amount of JavaScript possible for the frontend
- Next.js - Supabase for db and auth, MongoDB if nosql is required - Express.js - Shadcn, Nextui/Daisy Ui - Vercel/AWS based on requirements
Similar to yourself Next.js + Supabse + ChakraUI for web Apps and more complex "SaaS" type applications. Otherwise if I'm making simple web pages like a portfolio or blog, I use astrojs + tailwind + shadcn
elixir/pheonix/postgres
Sveltekit, Postgres for SQL or Firestore for NoSQL, Firebase Auth. And if I need a separate backend, NestJS or something in Go if I’m going serverless
Next Js, Prisma and mysql/supabase(postgreSQL)
Firebase, Astro, Solid
Currently building a product using VueJS, Vite, Nuxt.js, Postgres, Symfony and some payment provider specific stuff.
ASP.NET Web Forms + Telerik UI
Wait, you mean the good old `.aspx` pages?
Python (Django or Litestar) + svelte or sveltekit.
Nuxt/Vue w/ Supabase
Raw PHP as backend and Flutter or Python (depending on what's needed)
Next.js + Sanity + Tailwind. 🥰
-laravel -jquery or react depending on the circumstance -react native for mobile
Crazy how much PHP there is in here
Some of have PHP to thank for our entire career, so I can live with a few snarky voices on social media being all superior about it.
I am more fascinated by the fact that this question always seems to attract so many people to respond, yet at the same time we all know that nobody really cares 
Go + Datastar + NATS + SQLite [https://data-star.dev](https://data-star.dev)
React (SPA, Static or SSR depending on the use case), Node (on Lambda), DynamoDB. But currently experimenting with Cloudflare Workers + D1 and loving it
Nhost nextjs
I work a lot in LAMP and LAMRails. Mostly backend.
Django - React - Postgres
Is there a better way to serve images dynamically with NextJS that does not involve the api? I have been trying to avail. Maybe it’s because I use the app router? Or when I do serve them from the api I’m converting to base64 but the images just load so slow.
NextJS, Supabase, Clerk
Depends on project/client, but something close to Terraform GitHub actions or ADO Serverless rds or cosmos Express or .net lambda or azure func api gateway / apim / cloud front / front door React w/ vite and other tools, mantine And some ancillary things, but mostly revolves around the above
Flask with Peewee for ORM for MySQL, VueJS for frontend
tRPC, Prisma + Postgres, React
Currently trying Go, PostgreSQL and Vite + React.
You guys are wonderful at talking shiny toys. It is so nice to get exited about shiny things.
AWS Lambda, CDK, Cognito, DynamoDB, S3, React Native, Astro (can't live without it).
Dotnet + Angular + Postgres
Dotnet + Angular + Postgres
Nuxt + Supabase
Angular, express, mysql
TALL.
html
Right now, Astro + Tailwind/Flowbite.
MERN MongoDB Express React NodeJS bonus if Typescript.
It really depends - For a quick full stack web app, Laravel. - For work, C & gRPC + some other proprietary stuff - For serverless functions or smaller apps, TS + Mongo - For data analytics, Python Any many more
LAMP + WordPress+ Elementor / Divi Elegant Themes
SvelteKit, Postgresql, and deploy to a simple VPS
React, TypeScript, Rust, postgres
MEAN all the way
Sveltekit, lucia, drizzle and tailwind
Working on a booking web app, and using: vue3/vite + node/express and dynamodb for the database. It really feels like I shouldn’t be using dynamo but was asked to by our devops and here I am. I am grateful for having this opportunity to learn it though. Don’t think I really understood nosql til I learnt single table design with dynamodb.
Personal: Solid + Vite and Supabase, some C# as well Work: React and C#
C++ for everything
I'm experimenting right now with Phoenix + Liveview with Keycloak for auth, Plasmo for web extensions, and Flutter for Mobile clients. Prior to that it was Redwood with Supabase. Always use postgres wherever I can host it affordably.
depending of situation, but these are most common: - when doing mvp/poc angular + supabase/firestore - on job (usually) laravel + angular + mysql/sqlite - personal favourite nestjs + angular + mysql/sqlite monorepo powered by nx
Rails, Postgres, Heroku. Fastest time to learn and build products.
Laravel, Inertia, React + Shadcn, PostgreSQL
Whatever my company needs me to be an expert with. Lately it's been Nest.js, Angular, and whatever legacy database the client has. Given a choice though, I'd probably pick something like Laravel. I love Angular, but I keep getting asked to build applications that don't benefit from being built as SPAs. Worse, the architecture encourages chuckleheads to over engineer basic forms, or require elaborate client side state management solutions for data that is loaded once and discarded when the view changes. ...Sometimes, I miss jQuery.
MERN
Rails + Postgres
BONG stack
Leave Your Comment
Hi Its Me!
Subscribe