B
Marcel said:This appears to be the audio of Matz talk at BYU right before RubyConf.
Yes.
The video is available too here: http://www.cs.byu.edu/colloquia/
Bil said:Anyone have the link for the slides? (The movie has very
high compression.)
I like the
DONUTS WILL BE PROVIDED
in a font almost as large and heavy as the title
on the flier,
Yukihiro said:Hi,
In message "Re: Ruby Design Principles"
|Anyone have the link for the slides? (The movie has very
|high compression.)
http://www.rubyist.net/~matz/slides/byu/
but how many lines of C are hidden behind that 'ARGF.each{|line|Joel said:Is it really fair to say that the ruby program
print *ARGF
is the same as /bin/cat? When used interactively they are different:
$ cat cat.rb
print *ARGF
$ ruby cat.rb
1
2
3
1
2
3
$ cat
1
1
2
2
3
3
$ ruby -e 'ARGF.each{|line| print line}'
1
1
2
2
3
3
Also, with a lot of input, the memory usage will be very different,
since 'print *ARGF' slurps all input.
But even 'ARGF.each{|line| print line}' is a lot shorter than 50 lines
of C!
Reid said:Joel VanderWerf wrote: ...
but how many lines of C are hidden behind that 'ARGF.each{|line|
print line}'
For that matter, how many machine instructions behind those 50 lines of
C, and how many femto-turtles carrying out those instructions, and so on
all the way down?
For performance, write it in femto-turtles .
How do you get the dust mites out of the spacetime foam? I can't use itWilson said:I'm writing a DSL to manipulate the spacetime foam directly.
Performance above all!
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.