<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Ruleby - Blog posts</title>
    <link>http://ruleby.org/</link>
    <pubDate>Mon, 03 Sep 2007 14:30:42 GMT</pubDate>
    <description>Ruleby - Blog posts</description>
    <item>
      <title>Blog post - A DSL can change the way you think</title>
      <link>http://ruleby.org/blog/2</link>
      <guid>http://ruleby.org/blog/2</guid>
      <description>&lt;p&gt;A domain specific language (DSL) is often nothing more than a clever API. But in many cases, a DSL redefines how a programmer thinks about a program. That is the goal in the Ruleby project. Ruleby is a rule engine written entirely in Ruby. As such, it supports a DSL that is based on the Ruby language. This DSL gives programmers the ability to think about &amp;#8220;what&amp;#8221; a program is going to do, rather &amp;#8230;&lt;/p&gt;</description>
      <pubDate>Mon, 03 Sep 2007 14:30:42 GMT</pubDate>
    </item>
    <item>
      <title>Blog post - Ruleby: the Rule Engine for Ruby</title>
      <link>http://ruleby.org/blog/1</link>
      <guid>http://ruleby.org/blog/1</guid>
      <description>&lt;p&gt;Good programming depends on selecting the right tool for the job. In most cases imperative languages like Ruby, Java and C++ are good solutions. But they are not perfect. This article will present some of these cases and introduce a new tool that improves one imperative language: Ruby.&lt;/p&gt;


	&lt;h3&gt;Lessons from Dijkstra&lt;/h3&gt;


	&lt;p&gt;Imperative programming often results in complex code with a myriad of state tran&amp;#8230;&lt;/p&gt;</description>
      <pubDate>Mon, 03 Sep 2007 14:25:31 GMT</pubDate>
    </item>
  </channel>
</rss>
