<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Faruq Ismael</title>
    <description>The latest articles on DEV Community by Faruq Ismael (@faru5).</description>
    <link>https://dev.to/faru5</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F559989%2F5341e684-de34-4ab7-9d03-cbb3b65b7bbc.png</url>
      <title>DEV Community: Faruq Ismael</title>
      <link>https://dev.to/faru5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/faru5"/>
    <language>en</language>
    <item>
      <title>Vue.js — Considerations and Tricks</title>
      <dc:creator>Faruq Ismael</dc:creator>
      <pubDate>Sat, 23 Jan 2021 04:27:38 +0000</pubDate>
      <link>https://dev.to/faru5/vue-js-considerations-and-tricks-1on9</link>
      <guid>https://dev.to/faru5/vue-js-considerations-and-tricks-1on9</guid>
      <description>&lt;p&gt;Vue.js is great. However, when you start building large scale JavaScript applications, you will start to hit the boundaries of the Vue.js. These boundaries are not really the limitations of the framework; rather these are the important design decisions that Vue.js team had taken from time to time.&lt;/p&gt;

&lt;p&gt;Unlike React or Angular, Vue.js caters to different level of developers. It is friendly, easy-to-use for beginners and equally flexible for experts. It doesn’t try to shy away from DOM. Instead, it plays well with it.&lt;/p&gt;

&lt;p&gt;Having said this, this article is more like a catalog of some of the great discussions, issues and tricks I have come across on my way to Vue.js enlightenment. Understanding these key design aspects helped us while building our large scale web applications.&lt;/p&gt;

&lt;p&gt;Again, these discussion are valid as of today, May 18th, 2018. When framework upgrades, underlying browser and JS API will change, they may not be valid and intuitive&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>vue</category>
      <category>programming</category>
      <category>science</category>
    </item>
  </channel>
</rss>
