What web frameworks do you use?
I personally use Svelte(Kit), as it's simple and straightforward. I was planning on learning React, but the fact that it's owned by Meta really holds me back.
> I was planning on learning React, but the fact that it's owned by Meta really holds me back.
May I ask why? React starts there, but it will probably survive Meta. Its a great framework, IMO.
By "web" do you mean "Frontend"?
None. I write my own frontend, backend, db engine, libraries. Not completely of course, like I would still rely on Express and other heavy lifting when doing a node backend. If I need some special feature in the frontend I hunt for a library I can easily copy to my libs/ directory, but half the libraries that are used I wrote myself.
Struts and JSPs with some hand-crafted JS and CSS (no JS frameworks). At least that's what I was using back when I did any semblance of front-end web development. Yes, I'm old and no I don't do it anymore! But I do work with a lot of folks on my team who use React for our web UI.
None currently by my understanding of that, since all my sites are now static and generated by a bunch of makefile/shell/ImageMagick ...
VanillaJS/Angular for frontend, .NET Core/Node for backend.
It shouldn't matter too much if a framework is being backed by Meta. If there's enough support, documentation and easy-to-find-answers for it, then it's probably a good choice. Just make sure the code is readable and the framework's concepts are simple and easy to understand.
astrojs (with some React) for presentation website, nextjs for anything else. For backend, I use Django if the project is complex or Go frameworks for micros.
Probably worth knowing React since there’s such a large install base and work, but Svelte or Solid may be preferable for new or personal projects.
But that’s only frontend, what middleware/backend do you like to pair them with?
Small personal projects, laravel alpine tailwind livewire. Bigger projects, Vue and Go for backend.
Gatsby built and served Netlify. I love how its trivial to make hundreds to thousands of static pages with various react components and templates (mind you static doesn't necessarily mean you can't load outside data with an API)
With just a few Gatsby plugins & some tinkering, you can get a workflow that produces sites where each page has a 100 across the board on lighthouse
Django, vanillajs, react, phaser
Backend is Django whenever a SGBDR-backed model is involved. Sanic otherwise for simple web APIs. Frontend is Unpoly + BS5 or Shoelace.
FastAPI or LiteStar with python
Symfony with PHP
Django checks a lot of boxes for me.
rails for work, axum for side projects
React, Angular, Vue - fight!
Kicking and screaming, I finally succumbed to TS land. I used to do everything with Phoenix or Rails, but nowadays its hard to fight the full-stack type safety (even if its mostly an illusion) of something like Remix/Hono with React + Drizzle/Kysely.
I hate having to wire everything together, but the types won me over.
I’ve used it for nearly 2 years in production
Highly recommend this video if want a good primer on the problem it solves:
https://youtu.be/95B8mnhzoCM?si=EzKwMLbJW2602PJI
It’s built by the team that created the popular react router library, which has over a billion downloads since it was published;
It brought the joy of programming back for me, but more importantly it solves lots of typical headaches in react and helps me ship faster and with right amount of abstraction and levers to pull
If you’ve used react router, all that knowledge transfers over, if you have a react SPA with react router, very little to learn
IMO, it’s quite simple, enough that several SRE & traditionally pure backend teams at my company have adopted it for building their own internal tools & UIs
I use static Svelte(Kit) + TypeScript + Tailwind on the front end, Go and Postgraphile in the middle, and PostgreSQL functions on the backend.
I did write my own PostgreSQL migration tool though, to make it easier to write SQL functions in my IDE: https://github.com/pgpkg/pgpkg
Go/HTMX/Tailwind/SQLite
Nothing better than request latencies measured in microseconds on complex UIs built in an afternoon
Django and FastAPI. Both great for different reasons. Bun has caught my attention lately, though I'm not super familiar with javascript let alone its frameworks and dependency nightmares. Bun seems to fix some of that though, at least at a cursory glance.
FastAPI, Vue, Tailwind CSS. I avoid a database until needed. React and Vue are very similar but find Vue more simple to start with, and I'm happy that it can do more fancy stuff too when time comes.
First Polymer, now Lit. Lightweight library, makes building reusable web components a breeze.
Are you building a highly interaction frontend application? I mean an actual application? Or is it static with some interactive components? CSS can go far these days. And you can always add little interactivity with a script tag on the page.
Django, it does so much out of the box.
React (Next) for work and Solid (SolidStart) for personal projects, Astro for blog and static sites.
I've used React over the years, but now I mainly use Svelte. I like React, but for me, Svelte feels more lean and straightforward. Depending on how Threlte (a 3D library for Svelte) develops, I might switch completely. Additionally, React's Server Side Components are now introducing a paradigm shift, so it might be the right time to make the switch.
Blazor with C#. It allows me to focus at customer problems and easier at real-time functionality in B2B apps. It doesn't distract me with the ever breaking npm ecosystem shenanigans. We only use some gulp to compile sass code and minify a tiny bit of javascript.
Django, mithril.js, and bootstrap.
Django since it's a "batteries included" framework. Mithril.js for react-like features. It's a small framework, so one could easily read through it's code to understand how it works if needed.
I'll swap Django for Flask for smaller/lighter services.
If I was starting a project today, I might use htmx in place of mithril.js, and tailwind in place of bootstrap.
Hugo. I try to stick to HTML, CSS and Markdown. Typically, when you use more than that, you have less to say.
Axum + Leptos: Rust in the frontend, Rust in the backend.
Gin-gonic on Go with nextjs on fe. Moving away from next to htmx at the moment.
EDIT: +grpc for services. Web just happens to be a http translation layer + websocket termination.
At my last job it was all React and I was quite happy with it.
I'm trying to do web game development now and didn't want to fight the reconciler. I'm trying to build out stuff in Rust -> WASM but it's much harder than expected :) Not sure I could recommend it yet.
Scala and Play.
Honestly I don't like Play. I'm looking for a better alternative to it.
Rails and Phoenix when it's up to me, custom Go+React stack at work.
I actually went 3 years building Phoenix projects (2015-2018) and went back to Ruby/Rails, because it's really hard to beat the ergonomics, low ceremony, and expressiveness of the stack.
Might swing back into Elixir world if the right project comes along.
SvelteKit + Prisma + Lucia-auth. I’m hooked,