From the FAQ [L1 ] (escargo 16 Jan 2008 - This gives a file not found error.):
RLH Scales well? In what way?
Ruby doesn't have true threads and is known to have performance issues, a quote from a rant of a long-time Ruby user [L2 ] notes about RoR:
The home page for Ruby is http://www.ruby-lang.org/
Its most articulate advocates write such descriptions as,
A lot of the attention Ruby has gotten lately is due to Ruby on Rails[L3 ].
During Oct 2007, [L4 ] was making "Build Your Own Ruby on Rails Web Applications" available in PDF format for free...
This author summaries Rail's guiding principles as:
There is a Ruby/Tk if you want to bring your Tk skills into a new world:
require 'tk' root = TkRoot.new() { title "Hello, world!" } Tk.mainloop()
(from [L6 ]) More on Ruby/Tk (for MacOS!) appears in the "Ruby/Tk Primer: Creating a cron GUI Interface with Ruby/Tk" [L7 ].
What: Ruby Where: http://www.ruby-lang.org/ http://www.rubycentral.com/book/ext_tk.html http://poignantguide.net/ruby/ Description: Programming language for quick and easy programming. A clean, consistent language design where everything is an object, CLU style iterators, singleton classes/methods, and lexical closures. Makes use of Tk (with bindings similar in concept to Perl/Tk) for its GUI support. Currently at version 1.8.4 . Updated: 08/2003 Contact: mailto:[email protected]
See [L8 ] for more information. (escargo 16 Jan 2008 - This gives a file not found error. This link [L9 ] is about Ruby Tk.)
This [L10 ] review of Ruby Cookbook tries to give a sense for how Ruby feels.
RS: Like Scheme, Ruby has arbitrary-size integers as default - another hint that Tcl should have it too... Octet-packed integers come to mind..
AK: I consider the Octet-packed integers more something of a file-format, and less of an in-memory format. Note aside: In Slim Binaries I refer to the paper about Universal Symbol Files. This paper advances the notion of octet-packed integers too, albeit slightly differently than metakit if I read the code right. - RS: Well, a very simple alternative would be to just keep the string rep and let expr work on that if it runs into a "integer value too large to represent".
NEM notes in Jan 2008 that Tcl 8.5 does indeed now have arbitrary-size integers.
See [L11 ] for one comparison of Ruby to C++, CLOS, Dylan, Java, Objective C, Perl, PHP, Python, Smalltalk,
Ruby vs Tcl:
http://journal.dedasys.com/articles/2006/03/06/ruby-vs-tcl