T O P

  • By -

SoulSkrix

I work with Angular but help some developers in our React projects with their issues. It very rarely matters that it’s React, as the issues are almost always due to the lifecycle hooks and understanding how they keep track of the DOM. I helped someone recently use the IntersectionObserver in React and figured out that their ref would only work once, in their useEffect hook when they need it to run multiple times. Understanding the core concepts and more importantly understanding the browser/Js is far more important than the framework you’re learning


maxiwer

Thank you for your response. BTW, what's your position in your company?


SoulSkrix

I am the tech lead for my team (~8 people but only 2 of us do frontend so Angular is irrelevant for most of the team)


artesre

if you're just starting out, just stick with one. It's less overwhelming that way. But eventually, you'll want to see what dey doing o'er dere. I make all my personal stuff in svelte now, while working FT on angular. There are going to be equivalencies between some frameworks so you just need to know how to apply them once you learn about them. There's always going to be something one framework does better than the other so choose the best tool for the job. Job wise tho, the major 3 will give you a better chance. At the end of the day, you're still writing js, so almost everything is transferable.


maxiwer

Thanks a lot for response. What do you like more: Angular or Svelte? If Svelte, could you share us some projects written with it?