<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Languages and speed of development</title>
	<link>http://blog.go4teams.com/archives/languages-and-speed-of-development/33</link>
	<description>What I Read; What I Have Read; and stuff I pick up and drag along</description>
	<pubDate>Fri, 30 Jul 2010 18:31:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Daniel Tietze</title>
		<link>http://blog.go4teams.com/archives/languages-and-speed-of-development/33#comment-21</link>
		<pubDate>Mon, 22 May 2006 13:25:52 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/languages-and-speed-of-development/33#comment-21</guid>
					<description>Michael -- thanks for the pointers. I'll be sure to print the articles out and read them tonight.

Michiel -- I don't understand Ruby enough to follow these short examples. But from what I understand, this will only give me runtime checking, does not really make types a part of the language definition or class model and is little more than a macro for runtime &quot;asserts&quot; which check the types of the arguments. Or am I missing something?</description>
		<content:encoded><![CDATA[<p>Michael &#8212; thanks for the pointers. I&#8217;ll be sure to print the articles out and read them tonight.</p>
<p>Michiel &#8212; I don&#8217;t understand Ruby enough to follow these short examples. But from what I understand, this will only give me runtime checking, does not really make types a part of the language definition or class model and is little more than a macro for runtime &#8220;asserts&#8221; which check the types of the arguments. Or am I missing something?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Michiel de Mare</title>
		<link>http://blog.go4teams.com/archives/languages-and-speed-of-development/33#comment-20</link>
		<pubDate>Mon, 22 May 2006 12:19:52 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/languages-and-speed-of-development/33#comment-20</guid>
					<description>But the nice thing about dynamic languages is that you can add this yourself. See for instance this article on adding type checking in Ruby:

http://erikveenstra.nl/monitorfunctions/index.html#5.1.0</description>
		<content:encoded><![CDATA[<p>But the nice thing about dynamic languages is that you can add this yourself. See for instance this article on adding type checking in Ruby:</p>
<p><a href='http://erikveenstra.nl/monitorfunctions/index.html#5.1.0' rel='nofollow'>http://erikveenstra.nl/monitorfunctions/index.html#5.1.0</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Michael Schlenker</title>
		<link>http://blog.go4teams.com/archives/languages-and-speed-of-development/33#comment-19</link>
		<pubDate>Mon, 22 May 2006 08:40:04 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/languages-and-speed-of-development/33#comment-19</guid>
					<description>Did you ever read the Ousterhout paper on scripting languages?
http://www.tcl.tk/doc/scripting.html

It really explains what niche you should fill with dynamic languages, and which niche should be done with typed/system languages.

The power of current dynamic languages moves the border somewhat in the direction of the dynamic languages.

Also nice reading:
http://www.equi4.com/moam/doomed.html</description>
		<content:encoded><![CDATA[<p>Did you ever read the Ousterhout paper on scripting languages?<br />
<a href='http://www.tcl.tk/doc/scripting.html' rel='nofollow'>http://www.tcl.tk/doc/scripting.html</a></p>
<p>It really explains what niche you should fill with dynamic languages, and which niche should be done with typed/system languages.</p>
<p>The power of current dynamic languages moves the border somewhat in the direction of the dynamic languages.</p>
<p>Also nice reading:<br />
<a href='http://www.equi4.com/moam/doomed.html' rel='nofollow'>http://www.equi4.com/moam/doomed.html</a>
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
