<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>web framework on chrismoos</title>
    <link>/tags/web-framework/</link>
    <description>Recent content in web framework on chrismoos</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2020 Chris Moos</copyright>
    <lastBuildDate>Tue, 08 Jun 2010 21:12:06 +0000</lastBuildDate><atom:link href="/tags/web-framework/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fastr - A Web Framework for Ruby</title>
      <link>/2010/06/08/fastr-a-web-framework-for-ruby/</link>
      <pubDate>Tue, 08 Jun 2010 21:12:06 +0000</pubDate>
      
      <guid>/2010/06/08/fastr-a-web-framework-for-ruby/</guid>
      <description>Foreword Every month I go on a binge and learn something new. The most recent binge resulted in a new web framework, called fastr.
I&amp;rsquo;ve always used Rails when I needed to create a web application in Ruby, but despite how great it is to code in, the performance and concurrency is not up to par.
Don&amp;rsquo;t get me wrong &amp;ndash; Rails can scale, but it is not inherently very good when it comes to an individual instance&amp;rsquo;s performance.</description>
    </item>
    
  </channel>
</rss>
