Angular, React and the Controlled Chaos
At the start of the year we are sitting in the office spinning the wheel of fortune one by one. Everyone hoping they get a nice tech stack to use for their personal projects, and up I go and spin the wheel and seal my fate… C# and React. “Not bad” I think to myself, I have experience with C# but had never touched React in the slightest. I was curious and started researching what exactly React is and how it works.
I was pleasantly surprised to find that React offered a much more modular approach to web development, frontend web development in particular. The more I researched it, the more I wondered why we had never covered it before in university or even had it mentioned as an elective of some sort. Then came the Grad Project, and we found out that we are using Angular for it.
Well that's great because I now get to experience two different frontend frameworks and decide which I would like to work with more. Little did I expect Angular to be so vastly different to React at a surface level. TypeScript makes for a far different experience to what I had experienced so far with React.js (yes, I didn’t realise there was a TS version to React until it was too late).
These simple basic related concepts between the two frameworks made it easy to switch between the two and maintain a basic understanding of logic and flow in the applications. The main differences came into play when you looked at what exactly you needed to achieve and how large the scope was.