I ran a web dev business for 20 years. It includes two sites you probably have visited and bought things from. We used HTML for HTML. CSS for CSS and Javascript for Javascript.
Then 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.
Yes, exactly. And because all of this is bundled in laravel (and at some point I learned working with the framework), I'm using this since years for almost everything.
These days I am doing HPC software development, so not much web development. Over the last few years I used to work as a senior lecturer and then a junior professor at a university, where my group worked with web tech quite a bit.
We used PHP/Laravel for developing a scientific SaaS prototype [1] and Python/Django for teaching web application development [2]. For documentation (including teaching materials, blogging), we had a preference for static site generator (Jamstack) solutions: we used Sphinx and later switched to MkDocs [3, 4].
So far I've been loving it. Simple and easy to get started with. Everything works so well togther and is really easy to deploy as a single executable which can include any asset files with the `//go:embed` directive.
I use .Net & C# for backend development and Vue or Blazor for Frontend.
.Net has great tooling that won't get in your way as you work on the project.
C# has added lots of great features and is blazing fast nowadays with every .Net release being accompanied by a massive blog post describing all the performance improvements to the runtime[1].
I don't know. Is Tomcat some version of Apache server? It says 'apache2' at my localhost while installing the server, and at the webhost I don't know (might be some other server that can run PHP). I usually don't dive deep into server territory, so I'm a lucky guy that I can focus on the design and the webdev.
I have been really impressed with SvelteKit in my production SaaS for about a year now! You can make any type of static/dynamic/combination site, the dev experience is really good, and it feels like it elegantly bridges the front-and-backend (getting data from the back-end, form submission) which is something I've wanted since I started in 2011.
My SaaS uses SvelteKit, SQLite and Sequelize, but I would probably try Drizzle if I was starting today.
Django because in a word of constantly changing frameworks and approaches it’s nice to have something solid. New versions add improvements but Django is basically still the same as it has been for almost 20 years. It’s really fast to build things with as well and the Admin is amazing (just don’t try to overuse it).
Recently HTMX has been a really nice addition, adding some fanciness without writing more JS.
Some bits are just easier to do as full on JavaScript components and for those I use React because I know it and it does the job. Just for bits though (often as small as one component in a otherwise vanilla Django form), SPAs are a pain to write and maintain.
For pure APIs: pyapi-server [0]. For classic Web sites: Starlette [1], with SQLAlchemy Core [2] for database integration. Or, if you prefer something with more batteries included, FastAPI [3].
My personal website uses SvelteKit to glue together HTML, css, and a small bit of JavaScript. Most of the website could easily be extracted and deployed on its own or in another framework. I use Svelte primarily to provide a common nav bar across routes and to execute JavaScript that bundles my blog posts to display by date. I enjoy designing my pages by hand, so I prefer this setup to a static site generator. I vastly prefer it to using something like React. I do want to simplify the setup, but it works well for now.
If I were working on a website that needed a backend, I would use htmx and either flask or Django.
There are a ton of past threads on this, many valuable, and some huge. You can find them by searching [Ask HN web] (or stack or framework, etc.) in the search box at the bottom. Here are some decent-sized ones going back to 2016, but there are many more. I figure if something is recommended a few years ago and also recently, it's probably good, stable, and well-documented.
Ask HN: If you were to build a web app today what tech stack would you choose? https://news.ycombinator.com/item?id=38059036 (92 points by russianbandit 3 months ago | 208 comments)
Ask HN: Web frameworks – which less popular frameworks are you using and why? https://news.ycombinator.com/item?id=31607256 (84 points by vanilla-almond on June 3, 2022 | 147 comments)
I love vanilla Rails (that includes Hotwire) + Postgres + Heroku + Tailwind. I do often use Rubocop and some other rolling, and want to package that as a project starter kit.
I’m looking forward to seeing Rails 8 in action, as is going to make building PWAs easier.
Front-end: A few static sites (i.e. landing page) + Angular.
Back-End: A few C# APIs with Redis for caching.
Database: MongoDB + SQL Server.
Deployment: Docker Containers on Azure via DevOps Pipelines (one-click deployment).
I've moved everything to ASP.Net Core Blazor. I've been developing web apps on Microsoft's stack since Wrox's ASP 3.0 book. It's always been a pleasure.
these days I’m often using Supabase on backend, Nextjs+Vercel frontend
it has increased my speed to market massively. I mostly work on enterprise CRUD apps so getting things like SSO and API for free on Supabase is a great time saver
and then some apps require more specialized functionality and for that I’ll leverage the AWS stack
Honestly? I dislike every single one and I avoid it when possible. It’s a matter of aligning the UX with the client’s preferences and expertise. Last project I used contentful, it has a lot of features, so it’s a good choice for a project which will scale.
Then 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.