<?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: Anil Kushwaha</title>
    <description>The latest articles on DEV Community by Anil Kushwaha (@cloud_developr).</description>
    <link>https://dev.to/cloud_developr</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%2F163905%2Fa3675fdc-6121-4f3b-99b2-a73aa3482020.png</url>
      <title>DEV Community: Anil Kushwaha</title>
      <link>https://dev.to/cloud_developr</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cloud_developr"/>
    <language>en</language>
    <item>
      <title>Error Handling in Nodejs</title>
      <dc:creator>Anil Kushwaha</dc:creator>
      <pubDate>Mon, 25 Nov 2019 17:46:11 +0000</pubDate>
      <link>https://dev.to/cloud_developr/error-handling-in-nodejs-13d8</link>
      <guid>https://dev.to/cloud_developr/error-handling-in-nodejs-13d8</guid>
      <description>&lt;p&gt;If any AsyncHook callbacks throw, the application will print the stack trace and exit. The exit path does follow that of an uncaught exception, but all 'uncaughtException' listeners are removed, thus forcing the process to exit. The 'exit' callbacks will still be called unless the application is run with --abort-on-uncaught-exception, in which case a stack trace will be printed and the application exits, leaving a core file.&lt;/p&gt;

&lt;p&gt;The reason for this error handling behavior is that these callbacks are running at potentially volatile points in an object's lifetime, for example during class construction and destruction. Because of this, it is deemed necessary to bring down the process quickly in order to prevent an unintentional abort in the future. This is subject to change in the future if a comprehensive analysis is performed to ensure an exception can follow the normal control flow without unintentional side effects.&lt;/p&gt;

</description>
      <category>node</category>
    </item>
    <item>
      <title>Features of Node.js</title>
      <dc:creator>Anil Kushwaha</dc:creator>
      <pubDate>Mon, 25 Nov 2019 17:42:32 +0000</pubDate>
      <link>https://dev.to/cloud_developr/features-of-node-js-18ll</link>
      <guid>https://dev.to/cloud_developr/features-of-node-js-18ll</guid>
      <description>&lt;p&gt;Following are some of the important features that make Node.js the first choice of software architects.&lt;/p&gt;

&lt;p&gt;Asynchronous and Event Driven − All APIs of Node.js library are asynchronous, that is, non-blocking. It essentially means a Node.js based server never waits for an API to return data. The server moves to the next API after calling it and a notification mechanism of Events of Node.js helps the server to get a response from the previous API call.&lt;/p&gt;

&lt;p&gt;Very Fast − Being built on Google Chrome's V8 JavaScript Engine, Node.js library is very fast in code execution.&lt;/p&gt;

&lt;p&gt;Single Threaded but Highly Scalable − Node.js uses a single threaded model with event looping. Event mechanism helps the server to respond in a non-blocking way and makes the server highly scalable as opposed to traditional servers which create limited threads to handle requests. Node.js uses a single threaded program and the same program can provide service to a much larger number of requests than traditional servers like Apache HTTP Server.&lt;/p&gt;

&lt;p&gt;No Buffering − Node.js applications never buffer any data. These applications simply output the data in chunks.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why can’t browsers read JSX?</title>
      <dc:creator>Anil Kushwaha</dc:creator>
      <pubDate>Thu, 16 May 2019 10:46:55 +0000</pubDate>
      <link>https://dev.to/cloud_developr/why-can-t-browsers-read-jsx-5boc</link>
      <guid>https://dev.to/cloud_developr/why-can-t-browsers-read-jsx-5boc</guid>
      <description>&lt;p&gt;Browsers can only read JavaScript objects but JSX in not a regular JavaScript object. Thus to enable a browser to read JSX, first, we need to transform JSX file into a JavaScript object using JSX transformers like Babel and then pass it to the browser.&lt;/p&gt;

</description>
      <category>react</category>
    </item>
    <item>
      <title>What is React with JSX, and how are JSX and Babel related?</title>
      <dc:creator>Anil Kushwaha</dc:creator>
      <pubDate>Thu, 16 May 2019 10:40:42 +0000</pubDate>
      <link>https://dev.to/cloud_developr/what-is-react-with-jsx-and-how-are-jsx-and-babel-related-2pcc</link>
      <guid>https://dev.to/cloud_developr/what-is-react-with-jsx-and-how-are-jsx-and-babel-related-2pcc</guid>
      <description>&lt;p&gt;JSX can best be thought of as a markup syntax that very closely resembles HTML.&lt;/p&gt;

&lt;p&gt;React is a library which uses JavaScript functions to generate strings of HTML it inserts into a web page document’s body.&lt;/p&gt;

&lt;p&gt;JSX makes writing React components, the building blocks of React UI, easier by making the syntax developers use for generating these strings of HTML almost identical to the HTML they will inject into the web page.&lt;/p&gt;

&lt;p&gt;Babel parses JSX syntax, which browsers cannot understand, and transpiles your source code into JavaScript that is less human friendly but will run in browsers.&lt;/p&gt;

</description>
      <category>react</category>
    </item>
    <item>
      <title>Is there an alternative to Babel for JSX parsing?</title>
      <dc:creator>Anil Kushwaha</dc:creator>
      <pubDate>Thu, 16 May 2019 10:39:09 +0000</pubDate>
      <link>https://dev.to/cloud_developr/is-there-an-alternative-to-babel-for-jsx-parsing-1o26</link>
      <guid>https://dev.to/cloud_developr/is-there-an-alternative-to-babel-for-jsx-parsing-1o26</guid>
      <description>

</description>
      <category>react</category>
      <category>jsx</category>
    </item>
    <item>
      <title>What is React with JSX, and how are JSX and Babel related?</title>
      <dc:creator>Anil Kushwaha</dc:creator>
      <pubDate>Thu, 16 May 2019 10:36:27 +0000</pubDate>
      <link>https://dev.to/cloud_developr/what-is-react-with-jsx-and-how-are-jsx-and-babel-related-1dj2</link>
      <guid>https://dev.to/cloud_developr/what-is-react-with-jsx-and-how-are-jsx-and-babel-related-1dj2</guid>
      <description>

</description>
      <category>react</category>
    </item>
    <item>
      <title>What is the difference between State and props in ReactJs?</title>
      <dc:creator>Anil Kushwaha</dc:creator>
      <pubDate>Sun, 05 May 2019 07:41:24 +0000</pubDate>
      <link>https://dev.to/cloud_developr/what-is-the-difference-between-state-and-props-in-reactjs-2g42</link>
      <guid>https://dev.to/cloud_developr/what-is-the-difference-between-state-and-props-in-reactjs-2g42</guid>
      <description>&lt;p&gt;State - This is data maintained inside a component. It is local or owned by that specific component. The component itself will update the state using the &lt;code&gt;setState&lt;/code&gt; function.&lt;/p&gt;

&lt;p&gt;Props - Data passed in from a parent component. &lt;code&gt;props&lt;/code&gt; are read-only in the child component that receives them. However, callback functions can also be passed, which can be executed inside the child to initiate an update.&lt;/p&gt;

&lt;p&gt;The difference is all about which component owns the data. State is owned locally and updated by the component itself. Props are owned by a parent component and are read-only. Props can only be updated if a callback function is passed to the child to trigger an upstream change.&lt;/p&gt;

&lt;p&gt;The state of a parent component can be passed a prop to the child. They are referencing the same value, but only the parent component can update it.&lt;/p&gt;

</description>
      <category>react</category>
    </item>
  </channel>
</rss>
