<?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>Forem: Jules Manson</title>
    <description>The latest articles on Forem by Jules Manson (@julesmanson).</description>
    <link>https://forem.com/julesmanson</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%2F99032%2F33951f65-7498-4b63-9a3e-14b38519568a.jpeg</url>
      <title>Forem: Jules Manson</title>
      <link>https://forem.com/julesmanson</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/julesmanson"/>
    <language>en</language>
    <item>
      <title>Need help finding a very basic vanilla Javascript SPA router tutorial or source code</title>
      <dc:creator>Jules Manson</dc:creator>
      <pubDate>Tue, 08 Jan 2019 19:39:37 +0000</pubDate>
      <link>https://forem.com/julesmanson/need-help-finding-vanilla-javascript-spa-router-tutorial-or-source-code-27ii</link>
      <guid>https://forem.com/julesmanson/need-help-finding-vanilla-javascript-spa-router-tutorial-or-source-code-27ii</guid>
      <description>&lt;p&gt;I am coding a very simple single-page-app (actually just a website with one page) that is responsive to all screen sizes. It won't need to be a Swiss Army Knife like most libraries or apps try to be. I will be using no libraries/frameworks/tools other than Autoprefixer, Normalize, Ionic Icons, Font Awesome, Google Fonts, and other minimal use of miscellaneous libraries or tools.&lt;/p&gt;

&lt;p&gt;Yes you heard it right. There will be no Node or Grunt or React or Vue or Backbone, and certainly no jQuery (goes against every fiber in my body). I am well aware that building even the simplest SPA can be a very daunting challenge but my app will only be a very elementary personal web page to showcase my online portfolio (mechanical engineering) of information about me and projects I have worked on as well as javascript calculators I am developing for solving problems in engineering.&lt;/p&gt;

&lt;p&gt;I will still follow best practices such as accessibility, linting, minimizing, prefixing, tree shaking, W3C and ECMA standards, and compacting all source code but I won't Babel because that is not necessary for my intended purpose. I have the HTML, CSS, Javascript, DOM, BOM, JSON, and AJAX pretty much figured out. It's just the router that I really need help with. I really don't know where to start. A good tutorial, online book, books for purchase, or complete source code in vanilla Javascript would be very helpful. Please no jQuery.&lt;/p&gt;

&lt;p&gt;Thank you for your time.&lt;/p&gt;

</description>
      <category>vanilla</category>
      <category>javascript</category>
      <category>spa</category>
      <category>router</category>
    </item>
    <item>
      <title>RUST IN PEACE, JQUERY</title>
      <dc:creator>Jules Manson</dc:creator>
      <pubDate>Mon, 17 Sep 2018 05:47:39 +0000</pubDate>
      <link>https://forem.com/julesmanson/rest-in-peace-jquery-131o</link>
      <guid>https://forem.com/julesmanson/rest-in-peace-jquery-131o</guid>
      <description>&lt;p&gt;There is a new trend lately. It seems that the web is phasing out jQuery. For example, GitHub no longer uses it. Reason?&lt;/p&gt;

&lt;p&gt;In August 26, 2006 John Resig brilliantly authored and published jQuery 1.0 as a turnkey solution for most browser rendering/behavior inconsistencies which were a serious epidemic in the wild. But all major browsers are now mostly W3C compliant. Secondly, jQuery has grown into a bloated library capable of doing almost everything including ordering Starbucks online. It's true. However most developers only use it for a very limited set of tasks such as DOM manipulation and AJAX calls. &lt;/p&gt;

&lt;p&gt;And lasty, there are now a whole host of new API's available for simplifying tasks like AJAX calls that can now be done with the Fetch API which all major browsers now support.&lt;/p&gt;

&lt;p&gt;Now we must ask, do we still need to learn jQuery? Absolutely! It is still an essential component of backwards compatibility for many libraries and frameworks (for example Bootstrap 4) and will continue this way for the foreseeable future. A better question one might ask is do I still need that library (or framework) for my next shiny new project built from scratch? I highly recommend against it, however if you're a professional frontend developer you should at least understand what you're reading when upgrading existing sites.&lt;/p&gt;

&lt;p&gt;Regardless I still believe jQuery will eventually meet its destined fate sometime in the near future. Rust in Peace jQuery but never forget John Resig for his vision which not only founded the most popular library ever conceived but for also helping to make Javascript the number one programming language in the entire f-ing world.&lt;/p&gt;

&lt;p&gt;Here is an outstanding breakdown of vanilla Javascript DOM manipulations and other important tasks that can be performed without jQuery: &lt;a href="https://github.com/nefe/You-Dont-Need-jQuery" rel="noopener noreferrer"&gt;You Dont Need jQuery&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>jquery</category>
      <category>dom</category>
    </item>
  </channel>
</rss>
