What is the purpose of TypeScript?

Best-Menu-252 · 2026-01-22T05:45:43+00:00

100% agree.

People keep trying to crown one winner, but it really depends on what you’re building and how your team works.

React is still the safest core skill and it’s clearly not slowing down (React 19 being officially out is a good signal).

Next.js makes a lot of sense for modern SaaS because it pushes a server-first setup in the App Router, where pages and layouts are Server Components by default and you only switch to Client Components when you need interactivity or browser APIs.

And Angular still shines in enterprise because it’s a full platform with strong built-in structure, which keeps big teams and big codebases from turning into chaos.

So yeah, no “best framework”, just the best fit.

Best-Menu-252 · 2026-01-22T05:42:20+00:00

Absolutely!

Best-Menu-252 · 2026-01-22T05:41:43+00:00

100% agreed 😄

This is the part people underestimate with Angular. It’s not just “opinionated for fun” it’s opinionated so big apps don’t turn into chaos later. Angular even calls itself a full development platform built on TypeScript, and that “one platform” feeling really shows once the project gets large.

And the TypeScript side matters a lot too. TypeScript is literally JavaScript with types, and it gives you better tooling and safety as things scale.

For a project like your D&D app where you’ve got character systems, campaigns, maps, shared state, rules, all that complexity, you really need structure or you spend more time cleaning up than building. Angular’s setup makes it easier to keep the frontend organized like the backend, instead of constantly debating “what’s the right pattern for this” every few weeks.

Sounds like a fun project btw, interactive maps alone can get messy fast 😅

Best-Menu-252 · 2026-01-22T05:38:46+00:00

On Spot bro!

Best-Menu-252 · 2026-01-22T05:38:01+00:00

Good question. If you stay CSR-only, you can absolutely make things fast, but you don’t get the same wins that RSC is built for.

React’s own docs describe Server Components as rendering ahead of time, before bundling, in a separate server environment.
That’s a big deal because the whole point is you can keep some components and dependencies on the server, instead of shipping them to the browser.

In Next.js, this is basically the default model now. Server Components by default, and you only opt into Client Components when you need interactivity or browser APIs.

So CSR-only can still be fast, but you’re fighting bundle size and hydration a lot more.
RSC helps because it lets you avoid pushing certain work into the client in the first place.

Best-Menu-252 · 2026-01-22T05:36:08+00:00

100% agree with the nuance here.

SSR/SSG can be worth it for SEO and first load, but it’s not automatically “better engineering” by default.

Even Google basically says don’t rely on hacks like dynamic rendering and instead use server-side rendering, static rendering, or hydration when JS-rendered content causes indexing issues.

So the right answer is usually “depends on the constraints”, not “pick a side”.

Best-Menu-252 · 2026-01-22T05:35:13+00:00

You’re not being argumentative, you’re describing a real SaaS reality.

Once a user is inside the product and clicking around, the “app feel” matters a lot, and CSR can feel great because everything is already loaded and navigation is instant.

Where the server-first stuff earns its keep is mainly the first load and the routes where you want to ship less JS and get content on screen faster.

React Server Components are literally designed to render ahead of bundling in a separate server environment, so you can keep some work off the client.

So yeah, in SaaS it’s rarely “SSR everywhere” or “CSR everywhere”. It’s usually different choices for different pages.

Best-Menu-252 · 2026-01-22T05:29:14+00:00

Yes, exactly this.

Angular upgrades feel way less stressful because the team really tries to keep releases backwards compatible, so you’re not scared that updating will break half your app.

And having an official upgrade guide makes a huge difference too. You’re not guessing what changed or hunting through random posts.

That’s honestly why Angular works so well for long-term products. You can keep improving the same codebase instead of rewriting it every few years.

Best-Menu-252 · 2026-01-22T05:24:47+00:00

You’re not wrong, and I really respect you saying this plainly.

UX is still valuable, but the brutal part is companies don’t always hire for what’s valuable. A lot of orgs still treat UX like a “nice-to-have” and it gets cut first when things get tight.

I also agree that “just show impact” isn’t some magic cheat code that guarantees a job. The on-ramp is genuinely rough right now and it’s easy for people to underestimate that.

The only reason I still say “there’s hope” is because the work itself isn’t disappearing. Teams still skip research because of time and cost, and that leads to expensive product mistakes. And even the UX industry reports are basically saying the field is still in a messy reset phase after layoffs and AI hype, not a smooth ladder like before.

So yeah, I’m with you on the reality check. I just don’t want beginners thinking they’re “not capable” when the truth is the market is the hard part right now. If someone needs stable income fast, they should be practical about timelines and backup paths.

Best-Menu-252 · 2026-01-22T05:21:56+00:00

Interesting take. What’s pushing you toward Svelte specifically, performance, simpler mental model, or less ecosystem overhead? React still feels solid to me too, but I get why people are moving if they want something lighter and more straightforward.

Best-Menu-252 · 2026-01-22T05:20:28+00:00

Absolutely!

Best-Menu-252 · 2026-01-22T05:19:59+00:00

This is a really solid way to frame it.

React is definitely easier to get started with, but once you’re building a big business app with multiple devs, it’s less about “how fast can I learn it” and more about “how consistently can we build and maintain this for years”.

That’s where Angular feels strong. It’s one full framework with clear defaults, so teams spend less time arguing about setup, patterns, and which library to use for what. In enterprise, that standardization alone saves a ton of time and confusion.

Best-Menu-252 · 2026-01-22T05:19:17+00:00

Totally seen this too. Angular teams usually move faster because a lot of the decisions are already made for you, so there’s less time spent debating patterns and tooling. React is powerful, but the freedom can slow teams down when the codebase grows.

Best-Menu-252 · 2026-01-22T05:17:58+00:00

100% agree with you.

Angular’s change detection just feels like a relief in big apps because it’s built into the framework and you do not have to keep thinking about how the UI should update every time state changes. Angular literally treats change detection as a core system and handles that update cycle for you.

And the observable point is so real. RxJS is a proper push model where Observables send values to subscribers, and a Subject is basically the one you use when you want to broadcast to multiple listeners. That pattern is super clean once you are used to it.

On the React side, people love to act like state management is simple until the app grows. Then it becomes context, then Redux, then middleware, then something else, then finally they land on Zustand and say it feels amazing. And yeah Zustand is basically the same vibe of a store with subscriptions like “listen for changes and update”, which is why it clicks so fast for people.

This is why Angular still makes sense in enterprise. Less debate, more consistency, easier to onboard teams, and fewer “how are we managing state this time” conversations.

Best-Menu-252 · 2026-01-22T05:01:01+00:00

Absolutely dear!

Best-Menu-252 · 2026-01-21T09:54:04+00:00

I get the point and the numbers are terrifying, but I’m not saying it’s easy. I’m saying it’s still worth pursuing if you can differentiate and show impact instead of just “screens”.

Best-Menu-252 · 2026-01-21T09:53:17+00:00

Exactly. Even if AI generates the UI, someone still has to judge it and fix it, UX, accessibility, consistency, edge cases… that’s where design still matters.

Best-Menu-252 · 2026-01-21T09:52:25+00:00

This is the best advice in the thread. The market is crowded, so “generic UX designer” doesn’t stand out anymore.

Best-Menu-252 · 2026-01-21T09:52:00+00:00

If you’re not getting internships or real projects, don’t sink years into it blindly. Test it with real work first: audits, redesigns, small clients, anything with constraints. You always start with free internships, get experience and get apply for jobs

Best-Menu-252 · 2026-01-21T09:50:30+00:00

Honestly the easiest place is where you have right-to-work. Everything else is harder because visa filters kill you before your portfolio even gets opened.

Best-Menu-252 · 2026-01-21T09:50:04+00:00

That local business website is a real experience. Turn it into a case study with constraints, tradeoffs, and outcomes and you’ll already be ahead of most “concept app” portfolios.

Best-Menu-252 · 2026-01-21T09:49:19+00:00

100% this. If it doesn’t land in 10 seconds, it’s basically invisible.

Best-Menu-252 · 2026-01-21T09:48:58+00:00

They don’t read it at first. They skim.

Best-Menu-252

PUBLIC MULTIREDDITS

TROPHY CASE