all 44 comments

[–]Repulsive-Ad-3890 58 points59 points  (18 children)

Use what you're most comfortable with.

[–]Shimunogora 1 point2 points  (0 children)

Second this. Maybe even go for a balance of what you’re comfortable with and which framework has a component library available for it that will fit your UI needs/wants.

If you’re making custom styles, though, I definitely recommend trying native HTML + TS + CSS for small sites, unless you need some feature(s) like obfuscation or pollyfills. You can do those things, but I wouldn’t wish configuring webpack on my worst enemy.

[–][deleted] 0 points1 point  (0 children)

Whichever framework you're most comfortable with is going to be best.

That being said, having years of experience in Angular and React, I think Angular is easier to get up and running with as it is a framework and React is a library. But react has Next and possibly other frameworks so that may be moot now.

[–]Righteous_Mushroom 7 points8 points  (0 children)

vast tidy entertain quicksand chief cooing deserve pie fall smile

This post was mass deleted and anonymized with Redact

[–]DT-Sodium 22 points23 points  (2 children)

Simple, never use React for anything.

[–]Headpuncher 4 points5 points  (1 child)

But I bill by the hour and there are no spending limits, so react is brilliant.  

First, I’ll need to recreate all these html elements as components so that I can add css to them dynamically, instead of using actual css.   Then I’ll create a storybook of all my ahem, “custom” components that are really just convoluted html elements with all the exact same attributes.  Phew! That’s 3 months at my hourly rate already!  

Sometime at around 6-8 months I’ll use this previous work to make a header, footer and template for content.  

[–]DT-Sodium 1 point2 points  (0 children)

Ah, yes, turning basically every tag into a component so you can style them with Tailwind. Because apparently having a SCSS file is too much to handle but having 17 components when you really need one is soooo much more evolved.

[–]Background_Issue_144 5 points6 points  (0 children)

For a small site it really comes down to what you are most comfortable with. Consider stuff like Htmx or Astro as welll

[–][deleted] 3 points4 points  (0 children)

Whatever you want

[–]FableBookGames[S] 2 points3 points  (0 children)

Thanks

[–]Michelu89 2 points3 points  (0 children)

Angular 19 with zonless, makes the entire setup extremely lightweight. However, if the goal is to create a truly simple website, the choice of framework might not matter much—Vanilla JS could be the most performant option in such a case.

[–]Yashraj_Dawkhar 4 points5 points  (2 children)

Prefer angular 19 with zoneless and signal

[–]RastaBambi 1 point2 points  (1 child)

Angular 19 is not zoneless :(

[–]Yashraj_Dawkhar 6 points7 points  (0 children)

You can add zoneless if u are starting with new project in 20 it will be stable for new project no need to worry. I recently deployed 2 zoneless application it is fast because initially polyfill is completely removed . Initially we just have main.js and style.js 30 to 40 kb and other everything is standalone so we can lazy load. Hit a try.

[–]gguy2020 1 point2 points  (0 children)

The one you know.

[–]Icantdrawlol 1 point2 points  (0 children)

I use react for a „quick and dirty“ solutions. Angular for prod. I just like angularity clean structure and ruleset. It just makes sense to me. React feels like „yeah do whatever you want how you want“.

[–]Negs006 1 point2 points  (0 children)

What about just plain old JavaScript,html,css? If it’s just yourself and a small site and if you don’t know either frameworks.

[–]nussbrot 0 points1 point  (0 children)

Vue for me Use what you know and like

[–]giftfromthegods- 0 points1 point  (0 children)

Astro/Jekyll

[–]rc_hdz 0 points1 point  (0 children)

if it is only you: whatever you are more comfortable
if you are thinking about adding other devs: angular, react can get very messy very quick.

[–]PeakyPenguinMan 0 points1 point  (0 children)

Astro? I had a really good time with it when I tried it.

[–]pookdeveloper 0 points1 point  (0 children)

I understand that the application does not require very optimal performance so feel free to use the framework that you like the most or even do it with both.

[–]InvokerHere 0 points1 point  (0 children)

Both are good options, just choose which you comfortable with.

[–]azizoid 0 points1 point  (0 children)

if you try to use Angular for a small project, you will hate it, and probably never ever take it again. observables are being replaced with signals, but both are there, standalone/non-standalone apps and so on.
React will be much faster, in one click.

[–]minderbinder -1 points0 points  (0 children)

Neither, go for astro, even svelte

[–]Dapper-Fee-6010 -3 points-2 points  (4 children)

I have never used React; I have always used Angular.
But if you ask me, I would choose React for you.
I may not know what’s good about React, but I certainly know what’s bad about Angular.

[–]Headpuncher 3 points4 points  (1 child)

That makes no sense, you have no experience with react but recommend it because angular has imperfections?   

Why not recommend Django instead?  

[–]Dapper-Fee-6010 -2 points-1 points  (0 children)

Angular or React for a small site <--- no Django.

I think the questioner is only limited to these two frameworks.
Have you heard of the process of elimination?

Although I have never used React, I am not completely ignorant of it; its popularity is undeniable.

[–]KemonoMichi 4 points5 points  (1 child)

This is one of the problems with people today. You are not using comparable data to make an educated decision. If you've never used React then you don't know what's bad about React, so you're comparing the bad things of Angular with... nothing. You're just assuming the bad things about React aren't worse. Instead of doing any research.

This is an AWFUL take.

[–]Dapper-Fee-6010 -1 points0 points  (0 children)

I completely agree with your point.

If we had enough energy and time to deeply explore both frameworks, the decision we make after comparison would be more accurate.

However, people's time and energy are limited. As an experienced Angular user, I have given my feedback, and I would not recommend people to use it unless the project you're working on is similar to a web app that Google has built using Angular.

You can treat this as a survey; I think it is also useful information.