<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>react on James Alvarez</title><link>https://jamesalvarez.co.uk/tags/react/</link><description>Recent content in react on James Alvarez</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Fri, 05 Jul 2024 00:00:00 +0100</lastBuildDate><atom:link href="https://jamesalvarez.co.uk/tags/react/index.xml" rel="self" type="application/rss+xml"/><item><title>When to use React... maybe never?</title><link>https://jamesalvarez.co.uk/blog/react/</link><pubDate>Fri, 05 Jul 2024 00:00:00 +0100</pubDate><guid>https://jamesalvarez.co.uk/blog/react/</guid><description>&lt;p&gt;I've used React for many projects in my career, and it's a framework I'm quite comfortable with and can develop with
quite quickly, and I do like building things with it! But in every single case I've doubted whether it's the right choice,
and have often ended up believing it has slowed development time down due to making the project tooling over-complex.&lt;/p&gt;
&lt;p&gt;Recently at work I have been debating with my team about whether to use React for a new project, I've been arguing against
it and have compiled a list of links to articles that make the case well:&lt;/p&gt;</description></item></channel></rss>