![[The AI Show Episode 142]: ChatGPT’s New Image Generator, Studio Ghibli Craze and Backlash, Gemini 2.5, OpenAI Academy, 4o Updates, Vibe Marketing & xAI Acquires X](https://www.marketingaiinstitute.com/hubfs/ep%20142%20cover.png)
![[FREE EBOOKS] The Kubernetes Bible, The Ultimate Linux Shell Scripting Guide & Four More Best Selling Titles](https://www.javacodegeeks.com/wp-content/uploads/2012/12/jcg-logo.jpg){kind=logo}
![From drop-out to software architect with Jason Lengstorf [Podcast #167]](https://cdn.hashnode.com/res/hashnode/image/upload/v1743796461357/f3d19cd7-e6f5-4d7c-8bfc-eb974bc8da68.png?#)
.png?#)
.jpg?#)
 (1).webp?#)
_Christophe_Coat_Alamy.jpg?#)
![Rapidus in Talks With Apple as It Accelerates Toward 2nm Chip Production [Report]](https://www.iclarified.com/images/news/96937/96937/96937-640.jpg)
Short note: Avoid the isomorphic dumpster fire trap - you don't have to use node on the backend for a react app
The reasoning I often hear for why node on backend (besides performance or strong typing) is the front end is using react, so why not use typescript on the backend also? But the more you see libraries and frameworks that are half implemented and later abandoned (e.g. survey the ORM landscape), the more questionable it seems to adopt node instead of established, feature complete ecosystems with lower churn like python, rails, or golang.
The reasoning I often hear for why node on backend (besides performance or strong typing) is the front end is using react, so why not use typescript on the backend also?
But the more you see libraries and frameworks that are half implemented and later abandoned (e.g. survey the ORM landscape), the more questionable it seems to adopt node instead of established, feature complete ecosystems with lower churn like python, rails, or golang.
