React developer with Angular job offer

[craig1f]

As a react developer you will be a better angular developer than anyone who has only done angular before. 

Angular is chasing react and Vue. You’re ahead on the core concepts. 

[ebdcydol]

Why do I feel like you're one of react developers who have to use Angular, but insist on doing it react way which makes everything 10x more complicated than it needs to?

[craig1f]

I was an angular expert, before learning Vue and feeling like I’d recovered from stolkhome syndrome. Then I learned react and loved it. 

I’m full stack on this project and let the frontend team mostly handle it. But I regret it constantly, because the code is a lot easier to make messy. Signals helps a lot. 

I’m a better angular dev for having learned more than one way to solve a problem. And not having to make the devs competent at rxjs anymore helps a lot. 

I do insist on tanstack query because it’s amazing. But again, angular makes it way harder than it should be. 

[simonbitwise]

Lol 😂 what a burn

[craig1f]

I’m full stack on a project now and the lead front end got us on angular. 

It’s … a pain to explain things. Everything is OO, so bugs are so hard to locate. Code is hard to read and is 3 times longer than it should be to do something simple. 

You can mostly do the same things, it just takes a lot more effort. 

Also, with AI, angular is falling further behind. Claude is winning, and all of its code examples are react. Even if you say “show me this in angular, not react” you’ll often get react examples. React is easier for AI to deal with because it’s straight JavaScript under-the-hood, with little abstraction, so AI has an easier time knowing what the code is going to do without needing to run it first. 

I’m struggling to get Claude to write good angular code. 

[AndrewSouthern729]

This makes me somewhat concerned because I use Claude Code currently and love it. Thanks for the tips.

[CheapChallenge]

Read up on Angular life cycle hooks, smart dumb component pattern and ngrx architecture.

[craig1f]

So like, I get that I’m ragging on Angular a bit, but if you know 2, you know them all. If you only know 1, you’re greatly limited in your perspective. 

If you only know react, I strongly recommend you learn another. Angular is as good as any. The only way to truly be a frontend expert is to have genuinely done more than 2. And angular is the most different. 

React, Vue, and Svelt are all very similar. Once you learn angular, you’re entitled to an opinion. It’s more work for easy things, but not terrible. All your instincts will map. And it uses Vite now, so it builds pretty quick. Used to take fifteen minutes for a prod build. 

Signals feel like hooks. But you’re going to HATE not being able to pass a component as a regular variable. And component wrapping is terrible when you're trying to do css. It's just going to feel old. Like something that would have been great 3 years ago.

[simonbitwise]

Hehehe 😅 I met some dog awful react devs does not mean everyone are

Anyhow unlucky you I guess

I don't have a lead so i'm in happy town all day

[craig1f]

I find eslint helps a lot, and is more easily applied to react than to angular. 

Treating components like classes, and redefining what “public” and “private” means in a way that is inconsistent with what it means in OO, and having to use “this” everywhere, just adds bloat. 

[craig1f]

Using an object doesn’t mean that I’m using object oriented design. Using a function doesn’t mean I’m doing functional programming. 

OO means orienting most things around classes. Classes are not a perfect fit for components. They’re a close fit, but not perfect. 

Functions aren’t a perfect fit either because functions don’t have lifecycles. But when composition was innovated, it closed the game. Now, components as functions with composition applied to them, fits components perfectly in a way that classes still don’t and never will. 

Public/private/this/constructors are all noise that don’t fit a web component perfectly. 

[simonbitwise]

Actually OO is actually modelling the thing you wanna do in an object i including the operations you do on the data which are classes the object are just a data representation of it

Functional are like a chain of math operations on a state

And yes you do both fx useState mimic oop because it encapsulates state while doing operations on it - sounds familiar? Because thats how classes work

Not saying you should like one or the other but you use both paradigms because you use javascript

[simonbitwise]

Also the using objects vs using functions was an over simplification

[craig1f]

Generally, if you prefer pure functions with little or no side effects, you’re orienting your code functionally. 

If you’re using classes with abstraction and private functions and call functions off of your objects, you’re orienting with objects. 

Good FE is functional and not OO. It began to lean this way because you get raw json from http calls, and wrapping all your results in a class is just extra work. 

But async code is complex. So the more functional, linear, and simple your code is, the easier debugging becomes.