89 lines
3.4 KiB
HTML
Executable File
89 lines
3.4 KiB
HTML
Executable File
---
|
|
layout: site
|
|
title: Ruby in Ruby is 100% ruby
|
|
---
|
|
|
|
<!-- Pay Off -->
|
|
<div class="row center vspace10">
|
|
<div class="span12">
|
|
<h1><span>Ruby in Ruby. With more ruby and nothing but ruby.</span></h1>
|
|
<p>"Hey crystal, what do you want to be when you grow up". I like pink, i wanna be a ruby.</p>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="row center vspace10">
|
|
<div class="span12">
|
|
<p><span>Ruby in ruby hopes make the the mysterious more accessible, shed light in the farthest (ruby) corners, and above all, <b>empower you</b> </span></p>
|
|
</div>
|
|
<div class="span12">
|
|
<p><span>Three ideas are behind it</span></p>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="row vspace20">
|
|
<div class="span4">
|
|
<h2 class="center"> A better tool, a better job</h2>
|
|
<p>
|
|
Ruby is the better tool to do the job. Any software job that is. We who use ruby daily do so because it is
|
|
more productive, better in almost every way. The only downside is speed and we argue that with cheap resources.
|
|
</p>
|
|
<p>
|
|
Why it has taken this long to even seriously attempt a ruby implementation in ruby is due to the overwhelming
|
|
influence of C (folks).
|
|
</p>
|
|
<p>
|
|
Just a short and subjective list of why ruby is the better tool:
|
|
<ul>
|
|
<li>More fun. Ask anyone</li>
|
|
<li>Lets you focuss on the task</li>
|
|
<li>Elegant, both in syntax and solution</li>
|
|
<li>Understandable</li>
|
|
<li>Much faster to code</li>
|
|
</ul>
|
|
</p>
|
|
</div>
|
|
|
|
<div class="span4">
|
|
<h2 class="center">Use the Rails effect</h2>
|
|
<p>
|
|
Rails has evolved tremendously from what was already a good start. All the development <em>around</em> it has nurtured
|
|
ruby developement in all areas. Rails and all those parts make up the most mature and efficient software system
|
|
i know.
|
|
</p>
|
|
<p> The rails effect is due to the accessibility of the system, imho. Ie it is written in ruby.</p>
|
|
<p> Ruby itself has not enjoyed this rails effect, and that is because it is written in C (or c++) </p>
|
|
<p> It is my firm belief that given a vm in ruby, ruby development will "take off" too. In other words, given an
|
|
easy way to improve his tools, a developer will do so. Easy means understandable and that means ruby for a
|
|
ruby developer
|
|
</p>
|
|
</div>
|
|
|
|
<div class="span4">
|
|
<h2 class="center">Mature</h2>
|
|
<p>
|
|
The first thing any decent comiler does, is compile itself. It is the maturity test of a language to implement
|
|
itself in itself, and it is time for ruby.
|
|
</p>
|
|
<p>
|
|
Having just learned Assembler, which i have successfully avoided for 30 years, i can attest what a great improvement C
|
|
is over Assembler. But that was then and it is not just chance that developemnt has been little in the last 50 years.
|
|
</p>
|
|
<p>
|
|
There is this attitude C believers elude and since they are the gatekeepers of the os,
|
|
everyone is fooled into believing only c is fast. Whereas what is true is that <em>static</em> code is fast.
|
|
</p>
|
|
<p>
|
|
On a very similar note there we are lead to believe that os features must be used from c. Whereas system calls
|
|
are software interrupts and only the c std library makes them look like c functions. But they are not.
|
|
</p>
|
|
<p>
|
|
So now, are we ready to generate some bytes? even if they are Machine Code. And go to the Source? I say we are!
|
|
</p>
|
|
</div>
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|