This tutorial gives you complete knowledge starting from basic to
advance. It includes tutorial on Ruby Webservices, Ruby LDPA, Ruby XML,
Ruby/Tk, Ruby/DBI and many more interesting subjects.
If you like it please share it with others: I have put my lot of efforts
to put the things together and make it useful for all Ruby lovers.
This tutorial gives you complete knowledge starting from basic to
advance. It includes tutorial on Ruby Webservices, Ruby LDPA, Ruby XML,
Ruby/Tk, Ruby/DBI and many more interesting subjects.
[…]
For performing the examples discussed in this tutorial, you will need a
Pentium 200-MHz computer with a minimum of 64 MB of RAM (128 MB of RAM
recommended). You also will need the following software:
Linux 7.1 or Windows 95/98/2000/NT operating system
Not wholesale, but several bits from his “Ruby Quick Reference Guide”
are copied from the online versions of “Programming Ruby” (1st ed.)
and “Ruby in a Nutshell” (1st ed.) without attribution. Don’t know if
that’s true for the other sections or not (I didn’t check).
No, but stealing from other authors’ work is. So unless the authors of
“Progamming Ruby” and “Ruby in a Nutshell” have approved this “reuse”
of their work, there’s a problem.
No, but stealing from other authors’ work is. So unless the authors of
“Progamming Ruby” and “Ruby in a Nutshell” have approved this “reuse” of
their work, there’s a problem.
Yes, there’s a problem - however, assuming this is actually edited
into a new coherent whole (I didn’t see if there were new bits, it
looked familiar from many years back) there’s also some amount of work
done. Assuming the author is misguided rather than malicious, we
should applaud him for that work, even if he’s using sources wrongly,
and then try to help him do things in a way that’s more generally
accepted in a copyright-focused world.
I once compiled a kernel whose timestamp was earlier than the
timestamp of the .tgz file from which I’d gotten the source (thanks to
the time difference with Europe
I want to concur. Please remember that most people are NOT malicicious,
and that re-use is a major factor in all the arts and sciences. Finally,
in the course of our general intellectual development, it acquired a
formal name: refactoring. I consider it one of the most important things
we do in cultural evolution. I love the notion of refactoring.
Every day needs its own version of the truth, for it’s a new day.
And yes, giving credit matters. But not as much as being useful.
And…at some point, we all lose contact with our sources. How much can
you carry on YOUR back?
That said…get those sources in order, and make appropriate
attributions. It’s about being respectful, of both sources and readers.
I, too, am writing a Ruby book - but it’s just for me. Some of us just
can’t hold ourselves back.
t.
–
Tom C., MS MA, LMHC
Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website & psychotherapy weblog)
<< sleightmind.wordpress.com >> (mental health issues weblog)
<< directpathdesign.com >> (web site design & consultation)
I’ve gone through 8 books while compiling this content. We are not a
research scholars who do R&D and then write a book. Like other authors,
we also took many things as reference while writing this tutorial.
Anyway, if you did not like it then we are sorry…but I can say there
are few books who gives you clear understanding on Ruby-on-Rails,
Ruby/TK etc. if you have one then pls let me know.
It is a great thing to share knowledge, but copying other peoples work
word-for-word
and then not crediting it to them is dishonest. Just rework the
material you copied a bit
and your tutorial will be much better.
Also, the rails quick guide looks quite useful, thanks for that!
We had put lot of effort to bring this English Ruby tutorial online but
instead of any appreciation people started blaming us. I found out “Ruby
in a Nutshell” on the net and if you see itself is a copy of standard
ruby manual.
I found few pieces copied from this book and according to my fellow
writer he found this content interesting on the net and tried to
incorporate here. So finally I tried to remove that content.
I’ve gone through 8 books while compiling this content. We are not a
research scholars who do R&D and then write a book. Like other authors,
we also took many things as reference while writing this tutorial.
Anyway, if you did not like it then we are sorry…but I can say there
are few books who gives you clear understanding on Ruby-on-Rails,
Ruby/TK etc. if you have one then pls let me know.
No, but stealing from other authors’ work is. So unless the authors of
“Progamming Ruby” and “Ruby in a Nutshell” have approved this “reuse” of
their work, there’s a problem.
Yes, there’s a problem - however, assuming this is actually edited
into a new coherent whole (I didn’t see if there were new bits, it
looked familiar from many years back) there’s also some amount of work
done. Assuming the author is misguided rather than malicious, we
should applaud him for that work, even if he’s using sources wrongly,
and then try to help him do things in a way that’s more generally
accepted in a copyright-focused world.