<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>JavaScript Frameworks on Omid Farhang</title><link>https://omid.dev/tags/javascript-frameworks/</link><description>Recent content in JavaScript Frameworks on Omid Farhang</description><image><title>Omid Farhang</title><url>https://omid.dev/images/bio-photo-150x150.jpg</url><link>https://omid.dev/images/bio-photo-150x150.jpg</link></image><generator>Hugo -- 0.163.3</generator><language>en-US</language><copyright>2026 Omid Farhang | All rights reserved.</copyright><lastBuildDate>Sun, 02 Jun 2024 17:17:02 +0330</lastBuildDate><atom:link href="https://omid.dev/tags/javascript-frameworks/index.xml" rel="self" type="application/rss+xml"/><item><title>Is Building Your Own Design System Worth It? Best Practices, Key Considerations and Real-World Example</title><link>https://omid.dev/2024/06/02/is-building-your-own-design-system-worth-it/</link><pubDate>Sun, 02 Jun 2024 17:17:02 +0330</pubDate><guid>https://omid.dev/2024/06/02/is-building-your-own-design-system-worth-it/</guid><description>&lt;p&gt;In the ever-evolving landscape of web development, the question of whether to build and develop your own design system is a common one. As design systems become more integral to creating cohesive, scalable, and efficient applications, it&amp;rsquo;s crucial to weigh the benefits and challenges. This blog post delves into the worthiness of developing a custom design system, best practices for building one, when it&amp;rsquo;s needed, and the role of JavaScript frameworks like Angular. Additionally, we&amp;rsquo;ll explore which development teams should be involved in this process and provide a real-world example for clarity.&lt;/p&gt;</description></item></channel></rss>