Pros and cons of various front-end web frameworks
-
So I want to overhaul one of my personal projects (because it's ugly and I need to make some parts more flexible) and simultaneously want to learn one of the "big-name frontend frameworks" for resume purposes.
Choices seem to be between
- Angular
- React
- Vue
- Maybe Next.js?
Which one of these is least bad?
Constraints--
- This is client-side only. The server does nothing but serve static files. For now, no api calls anywhere. So anything requiring a server-side component to render is out. But that shouldn't be too much of a constraint.
- I'd prefer to not loose too much more sanity. I know, front-end web dev is definitionally insane. But if there are slightly less demonic ends of the pool, I'd prefer to stay there.
- I'm going to be using typescript because that's what the model code I already have is using.
-
If it's static, html does the job really well.
-
@Carnage said in Pros and cons of various front-end web frameworks:
If it's static, html does the job really well.
The files are static. But there's lots of javascript to do calculations and stuff based on user input. None of it goes to the server.
It's effectively a single page app...without a server at all. All the necessary files are packaged in the initial download.
Plus, I do actually want to learn a framework so I can put the "knows X" on my resume without lying more than I already do.
-
@Benjamin-Hall they're all roughly the same. React seems slightly more popular than the others. Therefore, there's no reason to learn anything but React.
-
@Benjamin-Hall said in Pros and cons of various front-end web frameworks:
@Carnage said in Pros and cons of various front-end web frameworks:
If it's static, html does the job really well.
The files are static. But there's lots of javascript to do calculations and stuff based on user input. None of it goes to the server.
It's effectively a single page app...without a server at all. All the necessary files are packaged in the initial download.
Plus, I do actually want to learn a framework so I can put the "knows X" on my resume without lying more than I already do.
Ah. As said already, go with the most popular. They are all shit, but then there are more people suffering with you at least.
A very code hipster option is yewstack/yew rust wasm.
All of the bleeding edge for none of the reasons.
-
I've worked with Angular briefly, and React more extensively. Angular wasn't bad, but React seems more popular.
Next.js is React plus some additional tools. I haven't worked with it much but I think I like what I see. If you really want an SPA it's not the tool for the job; but it might be an easier onboarding for you, and it's probably going to perform better. (And yes, it can be rendered to static HTML/JS. Just one file per page instead of one for the entire site.)
-
You're asking "I wanna play with shit piss and cum what's more fun"? The answer is - rainbow colored pisscumshitball!
I highly recommend learning Next.js. If you take a top down approach to learning a new shiny toy, you will pick up essential parts of React when you learn Nextjs. You will also learn about things like SSR, API routes and such.
This is the super sweet spot between getting some shit done with an SPA framework and resume padding like a boss. I did it not too long ago. Remember to have fun!
-
I like Angular, or really Rxjs (which Angular uses, but you don't need Angular to use it).
-
Okay, so consensus: use a fork of yew.
-
-
If you become proficient with typescript you can chop and change easily enough. I'm not sure about vue and the last one but it underpins the big two and you can sell yourself as an electron app developer too. If you're more prone to startups or trendy places react or vue. Corporate leans more towards angular. It's very eclipse rcp like if you've ever been down that route and it's just as prone to shite you see in enterprise java too.
-
@error said in Pros and cons of various front-end web frameworks:
I like Angular, or really Rxjs (which Angular uses, but you don't need Angular to use it).
Yep. Overall, though, Angular's components seem pretty sane for the most part.
I haven't used React, but what I've read I'm not a fan of. Mainly the way they mix markup and code. But, yeah, I understand it's pretty popular.
-
Is it weird that I like Vue over React because React’s syntax appears to be “well just jam any old shit in here”, where it effortlessly segues between logic and presentation, where Vue at least pretends to separate them somewhat.
-
@Arantor I haven't used either of those but your position sounds pretty unweird to me. One of the things I like about Angular is that they actually separate them.
-
@Arantor PHP PTSD?
-
@Zecc said in Pros and cons of various front-end web frameworks:
@Arantor PHP PTSD?
Not really, I’ve been separating my logic from my presentation layer for years now (nearly 15 years)
I wouldn’t even mind so much if it were syntactically more like PHP, but it has the “let’s type as little as possible” brain measles about it.
Like the first example you get in the docs on JSX:
const element = <h1>Hello, world!</h1>;Couldn’t you at least have quote marks in there to make it clear? (Yes I know that’s not how React works, blah blah virtual DOM but ffs, delineation is good)
-
@Benjamin-Hall react being more popular is a good enough reason to go with it, you get more marketable experience, find solution to your problems and examples easier, etc
next.js is built over react, and it's server side rendering makes search engines index your stuff faster
-
@Arantor said in Pros and cons of various front-end web frameworks:
Is it weird that I like Vue over React because React’s syntax appears to be “well just jam any old shit in here”, where it effortlessly segues between logic and presentation, where Vue at least pretends to separate them somewhat.
A lot of people like Vue over React. One of the largest discount brokers in India that pretty much can be considered No 1 an is the gold standard for trading uses Vue. When I spoke to one of the guys from their team about choosing Vue over React, he told me they wouldn't have been able to move as fast as they are if they'd chosen React over Vue.
I myself am considering using Vue for all my toy/scam products. Can someone with extensive experience in Vue comment? I like NextJS but React is fucking annoying with that JSX bullshit, gives me a headache everytime.
-
@stillwater I won’t claim significant knowledge but I do have a production app that uses Vue 2 (not Vue 3) where its original author did some weird shit around pushing stuff into Vuex for state management, while also having a server session for the same.
Debugging that was hair-tuggingly frustrating. But I learned a good amount about Vue in the process.
-
@stillwater said in Pros and cons of various front-end web frameworks:
I myself am considering using Vue for all my...scam products
Do you have a newsletter I could subscribe to?
-
@boomzilla said in Pros and cons of various front-end web frameworks:
@stillwater said in Pros and cons of various front-end web frameworks:
I myself am considering using Vue for all my...scam products
Do you have a newsletter I could subscribe to?
No need. You'll get the email anyway.
Taxus baccata - Wikipedia
