I've used Nuxt a few times, but I end up in absolute hell sometimes tracing down bugs and incompatabilities. More so with Nuxt 3. Probably not an issue for more experienced Devs.
I find myself coming back to the simplicity of running a separate backend, even though that reintroduces a lot of the problems that Nuxt alleviates.
svelte front end, golang backend, postgres for database. But it depends on the needs of the project. Choose technology because it's the right fit for the job, not because it's your favorite.
Choose technology because it’s the right fit for the job, not because it’s your favorite.
100000%
React / TypeScript / Vite (sometimes Redux) for the front end, C# .net / SQL for the backend..
Fast-ish to get up and running, scales to a medium-large project with minimal headaches
Yessss.
C#/.Net backends are the best. The long term stability, DevX, and the "it just works" nature of all the tooling makes it a great choice. It's also fast, which makes scaling for most applications a non-issue.
I've switched to postgres for DB from SQL server, have never looked back, would recommend.
Yup all valid points. And I find Nuget to be a heaps less painful package manager than other ecosystems
Vue + Express + Typescript + Postgres
Though I am playing around with Firebase and Firestore at the moment so that simpler projects have less backend overhead
Hanami, Ruby on Rails, Lucky
The database has to be Postgres. I’ve seen too much bizarre 🤬 coming from MySQL and Micro$oft SQL Server.
Honestly I’d love to learn COBOL just for fun but I have to work for a living 🥱
It’s honestly not that hard, the language was made to be simple. The complexity associated with the language largely has to do with the legacy applications the language supports. If you look at a greenfield project (eg CHADstack (it’s a joke project, but pretty fun to get exposure to some esoteric stuff for a couple hours)) you’ll actually pick the language features up pretty quickly.
.Net + EF Core + Vue/TS + Postgres. Redis as needed, Kafka as needed.
I can get applications built extremely quickly, and their maintenance costs are incredibly low. The backends are stable, and can hang around for 5, 10+ years without issue or problems with ecosystem churn.
You can build a library of patterns and reusable code that you can bring to new projects to get them off the ground even faster.
Would recommend.
Typescript, svelte, django, postgresql with a dash of celery, redis and pushpin
I'm seriously very surprised to still see so many relational databases in the top responses... guess I'm just in fantasy land. I hate writing SQL... good at it, but it's not fun (to me).
Use an ORM. With NoSQL on relational data, you're guaranteed going to write a worse, relational solution than what relational databases provide. SQL is shit, but rewriting relational logic is worse.
Except when you're not worried about scale because you're building a small side project... I don't want to pay for a db (or the hardware to host it) for my play projects. My in-home play server is a very old home PC that is very underpowered for today's software.
Not sure I get what you're saying. Sqlite exists and works on very underpowered hardware.
Ah, yes... good old sqlite... I guess the main reason I go the route I go is that I like writing map/ reduce functions... much more than reorganizing tables because I structured them poorly to start.
In fact, the project I'm on right now at paid job has a lot of structure transformation... and I'm enjoying it so much that I'm not even pining for one of my million side projects.
While it's not the most performant way to do things, I feel like data structure manipulation is one of the easiest to read ways to get from point a to point b.
Total beginner here, but I like VueJS with Pug Templating for the front end. I also could go with just HTML/Pug for most of my projects since they are small.
On the backend I only really have experience with NodeJS, but have created small personal applications with the Express, Hapi, and Fastify frameworks. For databases, I have only worked with MariaDB and Sqlite, with Knex/ObjectionJS the only query builder/ORM-like libraries I've utilized thus far. I hear a lot about PrismJS for a full fledged ORM and will probably look into that at some point. I've played around with Postgres, but have yet to build anything using it yet, and have not worked with GraphQL or Redis either.
I'm intrigued by the Python FastAPI and Flask frameworks (no interest in Django tbh). I also am intrigued by Go for servers, but have yet to even write a single line of Go code yet.
On the Front End, I'm looking to learn React next as it's everywhere, but am much more interested in learning Svelte and HTMX.
Depends:
For websites: Htmx + AlpineJs on the front end, ASP.NET Razor Pages and PostegreSQL on the backend.
For Web Apps; Blazor and PostgreSQL
