<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jamies888888</author><text>I&amp;#x27;ve written a couple of articles on the proper Gmail API, why doesn&amp;#x27;t this just use that instead of scraping the DOM?&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.sitepoint.com&amp;#x2F;mastering-your-inbox-with-gmail-javascript-api&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.sitepoint.com&amp;#x2F;mastering-your-inbox-with-gmail-ja...&lt;/a&gt;
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.sitepoint.com&amp;#x2F;sending-emails-gmail-javascript-api&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.sitepoint.com&amp;#x2F;sending-emails-gmail-javascript-ap...&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Gmail.js – JavaScript API for Gmail</title><url>https://github.com/KartikTalwar/gmail.js</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nathancahill</author><text>This is a great library. Standardizes most of DOM manipulation&amp;#x2F;action triggering for everything Gmail does. Although Gmail&amp;#x27;s DOM changes sometimes like seibelj pointed out, you&amp;#x27;ll have the same issue if you roll your own implementation, so, for me, this is preferable.&lt;p&gt;If I remember right, it underwent a major rewrite a year or so ago, after which is has been very solid.</text><parent_chain></parent_chain></comment><story><title>Gmail.js – JavaScript API for Gmail</title><url>https://github.com/KartikTalwar/gmail.js</url></story>