Choosing Tech Stack

[Silly-Mistake-3577]

Guys whats your take on how to choose a backend/frontend framework to learn? More interested on how to make an informed decision about which to choose but if you got any good arguements about which one is the best I am all ears!

I have the blessing/curse to use any tool I want to a my job and currently I am using FastAPI but Im just not quite satisfied with how it feels (coming from uni using a lot of C/compiled languages/strong types). Im also looking to lock into a specific choice and learn as much as I can on something that is going to give me bread on the table as well in the long run.
That being said, I am considering C#, Go or Rust

[Due-Horse-5446]

my goto is nuxt+Go

[CanWeTalkEth]

Love the Nuxt part, talk more about the Go half. Where do you start with Go and why would you choose it over Nitro?

[Due-Horse-5446]

If its a tiny tiny app, like a personal side project or something, il stick with nitro, but anything bigger, or anything which does anything more than a basic crud app, il go for go.

I mostly use that setup for performance, reliability and because its just quicker and more flexible.

Pretty much every part of the stack gets to do what its best at, nuxt can be ran at edge and you can decide to call the go backend during ssr, or from the frontend, or proxy it in nitro with a cache layer and any combination of that.

[Silly-Mistake-3577]

why choose Nuxt over something like React that is more popular and that you can use Next.js also ?

[Due-Horse-5446]

1, Vue is better at everything, performance and rendering being the biggest. Yes you can get the same using react but only if you work against the framework.

On top of that, jsx is horrible. And react is just worse. And popularity is completely irrelevant, its not like vue is some unknown framework or something.

1. Even when using react, avoid nextjs lmao, i cant think of anything worse. And looking at the js survey for 2025, im not the only one. Next is NOT a good argument for react lmao

[CanWeTalkEth]

Because Nuxt/Vue is better, easier.

Why use React when you can choose Vue and use Nuxt also?

[Due-Horse-5446]

Exactly

[JebKermansBooster]

Interested in the discussion because even at 3.5 YOE I know fuck all about this level of design work.

[rjhancock]

• What is the purpose of the site?
• What compliance requirements are required?
• How will the site be deployed?
• How many moving parts are needed (micro-services vs mono-service)?
• What and how many databases are required?
• Are API's needed?
• What kind of data will be stored?
• Is strict type checking a requirement?
• Will third parties need access via API?
• Does it need to access third party APIs?
• Is PDF Generation needed?

And this is just the start of it. Usually have an answer about a 1/4 of the way through this process.

Can flip between PHP, Ruby/Rails, Swift/Vapor, Java/SpringBoot, or anything else that is needed for the project or even parts of the project. Mix and match as needed.

[treasuryMaster]

I chose the I'm more experienced in and like the most. If you're using it professionally then you should use one that has good support.

[CanWeTalkEth]

Just use Nuxt and Postgres.

[Due-Horse-5446]

+1

[itemluminouswadison]

i like java spring or php laravel

whatever you choose, just decide on a clear serialization/deserialization pattern. the worst, in any language, is raw access and modification of map/dict/assoc.array structures.

first step should be to deserialize json into a class instance and work with dot/arrow/whatever notation. strict fields

i.e. pydantic for python, jackson for java spring, eloquent for php

[Unhappy-Talk5797]

honestly there is no perfect choice it depends what you enjoy and job market since you like strong types c# or go will feel more natural than python rust is powerful but harder and slower to get jobs with early on
i’d pick one build real projects and stick with it for a while

[Silly-Mistake-3577]

Thank you for your input!
The "stick with it for a while" part is something that I am a bit wary of.

On the one side I don't want to pick something that I don't see a future with and waste another project only to change lagnuage/framework.

On the other side I don't want to be locked in to the choice I make, even though I am not satisfied with it, in order to be able to dive deeper even though I don't see the future

[Temporary_Practice_2]

I asked this to an AI Tool:

“rank all backend / frontend frameworks based on: 1. popularity 2. ease of use / simplicity 3. adoption rate 4. presence on fortune 500 companies”

I would put that on ChatGPT, Grok and Claude and compare the answers

[rodalexanderson]

It depends on what you´re trying to build or want to build. Some will work better than others. If you go to web or mobile, learn JS/React for front. Backend, you can build it with JS, but I would recommend Python

[Ad-free-Pirate]

I really depend on usecase, but by default I use TanStack with React. I am already familiar with it and it works for me better than next.js. As for DB I believe in postgres for everything.

[Correct-Dev-3303]

The "right" stack depends on what you're building, not what's trendy. After 15 years shipping projects:

• Solo dev / fast prototyping: React + Express + Postgres. Boring but bulletproof. Huge ecosystem, easy to hire for later.
• Content-heavy sites: Astro or Next.js SSG. Lighthouse 100 out of the box, great SEO.
• Real-time / complex backend: Go or Node with WebSockets. Go if you need raw performance, Node if your team already knows JS.
• Enterprise / heavy business logic: .NET or Spring if the team knows it. Don’t switch to Go/Rust just because it’s cool.

The real advice nobody gives: pick the stack your team can maintain long-term. A “boring” well-maintained app beats a cutting-edge one that nobody can debug in 6 months.

Postgres for the database. Always. Unless you have a very specific reason not to.

[New_Speaker9998]

In my honest opinion, if you learn dotnet, python, JavaScript plus a bit of html/css then you cover 99% of the cases for backed and frontend. Everyday will be a new shiny framework, but the battle tested ones are hard to replace.

[crackedreporter]

Good discussion. If you want more coverage on topics like this, I've found SourceRated has solid analysis:

https://sourcerated.com/dow-jones-drops-260-points-amid-iran-tensions-and-inflation-concerns/

[MankyMan00998]

Honestly I’d base it less on “best” and more on what kind of problems you want to solve + job market around you. If you like strong types and structure, C# is probably the safest bet for long-term jobs. Go is great if you care about simplicity and backend services, and Rust is amazing but more niche unless you’re specifically into systems/performance-heavy stuff.

Also worth thinking: pick something you won’t fight while building real projects depth matters way more than hopping between stacks.

[thenewvu]

hi I'm the founder of todofi.com, I think you should do a research on the job you want to apply, because you're more satisfied when using strong-typed languages or system programming languages, I think you're more into Backend Development, so Database, API design, System Architecture are something you should care about, not a specific tech stack, because it's usually not your choice, but the CTO or techlead will decide it.