<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>ianb</author><text>Speaking as the principal developer for TogetherJS:&lt;p&gt;In the past we have opted not to work on IE support because we had limited resources, and because we wanted to focus on what we thought were the hard problems: how should the tool act, how do we communicate changes between browsers, how do we integrate with apps, etc.  Supporting Internet Explorer was always something we knew we &lt;i&gt;could&lt;/i&gt; do, it wasn&amp;#x27;t a hard problem, but it still required some effort.  As such it didn&amp;#x27;t feel like it was advancing the project.  It was never meant as any slight towards IE, just an expedient way to save some time.&lt;p&gt;Also, while we do browser sniffing, we only use that to put up a warning for IE users to alert them that it&amp;#x27;s not going to work well.  This was pointed out on Twitter as though we were actively blocking browsers, in part I think a knee-jerk reaction to browser sniffing, but what we&amp;#x27;ve done still seems to me like a reasonable and responsible thing to do – better to admit you don&amp;#x27;t support a browser than just expose people to a crappy experience.&lt;p&gt;Of course times change, and as TogetherJS has become a more mature tool it&amp;#x27;s probably time to revisit our Internet Explorer support.  But on the other hand this isn&amp;#x27;t a commercial tool, so I&amp;#x27;m not entirely sure what resources we as a team will be able to invest in Internet Explorer support.  But it&amp;#x27;s also open source, and we would welcome contributions to fix this.  We&amp;#x27;ll be working on a slightly more structured plan soon.  It might not even be much work, I really don&amp;#x27;t know.&lt;p&gt;Here&amp;#x27;s the bug to watch: &lt;a href=&quot;https://github.com/mozilla/togetherjs/issues/867&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mozilla&amp;#x2F;togetherjs&amp;#x2F;issues&amp;#x2F;867&lt;/a&gt;</text><parent_chain><item><author>mikegioia</author><text>This looks great but it seems they have no plans to support Internet Explorer (&lt;a href=&quot;https://togetherjs.com/docs/#browser-support&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;togetherjs.com&amp;#x2F;docs&amp;#x2F;#browser-support&lt;/a&gt;). That&amp;#x27;s a shame because most of our users who need this level of support all use IE :&amp;#x2F;</text></item></parent_chain></comment><story><title>Introducing TogetherJS</title><url>https://hacks.mozilla.org/2013/10/introducing-togetherjs</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>phowat</author><text>Mozilla has a considerable stake on WebRTC&amp;#x27;s success, and a good way for them to push it&amp;#x27;s adoption is to help make useful web apps which rely on it. It would be counter productive, and a huge amount of wasted work, for them to support non-webrtc enabled browsers. As someone who is also actively working with the technology and betting on it&amp;#x27;s success, I&amp;#x27;m actually happy they don&amp;#x27;t support IE&amp;#x2F;Safari.</text><parent_chain><item><author>mikegioia</author><text>This looks great but it seems they have no plans to support Internet Explorer (&lt;a href=&quot;https://togetherjs.com/docs/#browser-support&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;togetherjs.com&amp;#x2F;docs&amp;#x2F;#browser-support&lt;/a&gt;). That&amp;#x27;s a shame because most of our users who need this level of support all use IE :&amp;#x2F;</text></item></parent_chain></comment><story><title>Introducing TogetherJS</title><url>https://hacks.mozilla.org/2013/10/introducing-togetherjs</url></story>