Forem

The perfect Stack for building type-safe applications in 2025

Anmol Baranwal on February 05, 2025

Trying to pick the best tech stack in 2025 is very hard, especially with all the new frameworks that are getting released. It's more than just typ...

Read full post

Bobby • Feb 5

Nice! Great post as always 👏

Anmol Baranwal • Feb 5

Thanks for reading, Bobby! 🙌 Appreciate it.

Dilpreet Grover • Feb 5

Encore.ts seems a great framework. I will check it. Thanks for sharing ❤️🔥

Anmol Baranwal • Feb 5

Thanks for reading Dilpreet! I was really surprised by how easy the docs are and getting those pre-made instructions for the cursor made life so much easier.

Syakir • Feb 5

Great post, Anmol 🔥

Anmol Baranwal • Feb 5

Thanks Syakir! 🔥 Time to build something nice :)

Steven Ramirez • Feb 7

Good article but, ultimately, I must agree in the negative. Considering the number of well established, properly typed, server side languages, TS seems like the worst choice. And with regards to performance and scalability, anything React related is always a poor choice.

Pakagrong Lebel • Feb 9 • Edited

Is that so? Im quite new to doing full-stack related stuff. Typescript seems to be fine with me but I use it with next.js a lot, not create-react-app anymore. Seems to be bad practice. What else is out there you think might be better? Id like to learn more about it.

Yash Kumar Saini • Feb 7

Great guide Anmol,

Anmol Baranwal • Feb 13

Awesome. Thanks for reading Yash!

Serhiy • Feb 6

Fundamental work! Thanks!

Anmol Baranwal • Feb 13

Thanks for reading man.

Red Ochsenbein (he/him) • Feb 6

Nah, Goth-Stack does it for me

Anmol Baranwal • Feb 13

This is the first time I've heard about it. You can also use Encore.go: encore.dev/go!

I just used TypeScript for the scope of this article (since I'm more inclined towards it).

Growwithninja • Sep 6 • Edited

Great insights on building type-safe applications in 2025—the stack you outlined really emphasizes reliability and scalability. It reminds me of how Shake Shack approaches its menu: consistent quality, carefully sourced ingredients, and attention to detail. Just like type safety reduces hidden risks in development, Shake Shack’s consistency builds trust with its customers. Both are about creating experiences that people can depend on, whether it’s in software or in dining.

Caleb H. • Feb 5

Hot take: anyone looking specifically for a “type-safe” stack should avoid JS/TS on the backend, it’s not truly typed!

Anmol Baranwal • Feb 13

Yeah, Rust or Go can be better, I just covered TS because I'm more inclined towards it. Encore also provides go backend framework if you prefer working with that: encore.dev/go!

Stasi Vladimirov • Feb 6

Similarly anyone looking for reactive stack should avoid react on the frontend since it’s not truly reactive…

Stasi Vladimirov • Feb 6

You lost me at next/react… in 2025… I guess if you are looking for the least performant solution with the worst memory then it’s a decent choice.

Anmol Baranwal • Feb 13

It depends on the context. Some of the points may be valid, but you're choosing raw performance over developer experience.

If performance is the top priority, there are of course better options. But if you're balancing speed, ecosystem and developer experience, this is still a strong choice in 2025.

Stasi Vladimirov • Feb 13 • Edited

What part of the developer experience makes React a strong choice?

Maybe it's the part it's not a framework, but a "library"?
Wait, is it the documentation (:puke)?
Hmm, maybe it's the learning curve? But really?
I guess it's the tooling (vite/vitest)... Oh snap
I got it... It's the rules of react/rules of react state/rules of of react styling/rules of ??, sorry had to double check if they had invented a new rule while I was typing this
PR comment: Don't forget about useCallback and useMemo, useGrandma and please don't ever useGrandpa? What do these actually actually do? And let's not talk about useImperativeHandle.... (background screams)
I am telling you it must be because they are following the web standards. html/templates? Nope jsx. Routing/location? nah, react routing! css/styling? No way, styled components. SSR, how about "use server"..
Perhaps it's the fragmented ecosystem because its always fun to compare class components, server/client components, hooks, observables and 10 other ways you can learn to manage state at your next job.
Must be the typescript support! React must be written in typescript? Right? Right? OK, it doesn't matter. Don't worry, there are dozen of functions like forwardRef that don't support generics.

Wait, what is developer experience? Ahhh, getting paid to know all possible edge cases and write more code than necessary to get the job done... That's why. Now it makes sense!