<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Discussing the Future of Programming Languages and IDEs</title>
	<atom:link href="http://blogs.jetbrains.com/idea/2008/06/discussing-the-future-of-programming-languages/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.jetbrains.com/idea/2008/06/discussing-the-future-of-programming-languages/</link>
	<description>tips &#38; tricks, news, how-to's</description>
	<pubDate>Thu, 18 Mar 2010 18:43:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Charles</title>
		<link>http://blogs.jetbrains.com/idea/2008/06/discussing-the-future-of-programming-languages/#comment-59048</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Mon, 09 Jun 2008 01:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/idea/2008/06/discussing-the-future-of-programming-languages/#comment-59048</guid>
		<description>Excellent insight!  I'm glad to hear about language-specific IDE's and debuggers!</description>
		<content:encoded><![CDATA[<p>Excellent insight!  I&#8217;m glad to hear about language-specific IDE&#8217;s and debuggers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendon</title>
		<link>http://blogs.jetbrains.com/idea/2008/06/discussing-the-future-of-programming-languages/#comment-58983</link>
		<dc:creator>Brendon</dc:creator>
		<pubDate>Sun, 08 Jun 2008 13:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/idea/2008/06/discussing-the-future-of-programming-languages/#comment-58983</guid>
		<description>The article was very interesting regarding your position on Scala.  I think Dmitry is right that a lot of us requesting Scala support are requesting it because we won't use Scala without it.  Not because we already use Scala.  It is obviously important for Jetbrains to focus their efforts on supporting viable future technologies.  I can see that Scala might not be the panacea that many people think it might be.  Perhaps it has compromised too much by running on the VM?  Perhaps there too many ambiguities?

But Dmitry never really says what these complexities are.  IntelliJ probably has a better idea than most people whether these "problems" are going to hold the language back or not.  I think it's important that these problems get aired, in specifics, for the benefit of us as people looking to evaluate Scala, for the benefit of Scala itself (who need tooling desperately) and for the benefit of yourselves as the developers justifying a reduced commitment to Scala.

If Dmitry could elaborate on the problems, then perhaps we can get some constructive debate started.

Regards,
Brendon.</description>
		<content:encoded><![CDATA[<p>The article was very interesting regarding your position on Scala.  I think Dmitry is right that a lot of us requesting Scala support are requesting it because we won&#8217;t use Scala without it.  Not because we already use Scala.  It is obviously important for Jetbrains to focus their efforts on supporting viable future technologies.  I can see that Scala might not be the panacea that many people think it might be.  Perhaps it has compromised too much by running on the VM?  Perhaps there too many ambiguities?</p>
<p>But Dmitry never really says what these complexities are.  IntelliJ probably has a better idea than most people whether these &#8220;problems&#8221; are going to hold the language back or not.  I think it&#8217;s important that these problems get aired, in specifics, for the benefit of us as people looking to evaluate Scala, for the benefit of Scala itself (who need tooling desperately) and for the benefit of yourselves as the developers justifying a reduced commitment to Scala.</p>
<p>If Dmitry could elaborate on the problems, then perhaps we can get some constructive debate started.</p>
<p>Regards,<br />
Brendon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
