G
Gregory Brown
Okay, the thread on "Why Living Dangerous can be A Good Thing" is
going quite well.
I'd like to start drafting up notes for my article, so I've put them
on a wiki page.
http://tinyurl.com/alaxa
Feel free to add sections, tweak definitions, etc etc and add your own cont=
ent.
However, please be mindful of the fact that this is intended to be a
summary of the community consensus, so please do ask here on RubyTalk
if you have doubts that you're opinion would be at least generally in
line with that of the community before adding it to the notes on the
wiki.
Please do reference any websites you are getting your materials from,
if you do so.
keep in mind, the key issues are:
1. Defining what the open nature of ruby is.
2. Addressing the concerns of those who find ruby 'dangerous'
3. Showing the benefits of ruby's openness and dynamicity.
4. Exposing the potential issues that arise from this, and how to avoid the=
m
As usual, I am overwhelmed by the RubyTalk effect, so please keep
those contributions coming!
going quite well.
I'd like to start drafting up notes for my article, so I've put them
on a wiki page.
http://tinyurl.com/alaxa
Feel free to add sections, tweak definitions, etc etc and add your own cont=
ent.
However, please be mindful of the fact that this is intended to be a
summary of the community consensus, so please do ask here on RubyTalk
if you have doubts that you're opinion would be at least generally in
line with that of the community before adding it to the notes on the
wiki.
Please do reference any websites you are getting your materials from,
if you do so.
keep in mind, the key issues are:
1. Defining what the open nature of ruby is.
2. Addressing the concerns of those who find ruby 'dangerous'
3. Showing the benefits of ruby's openness and dynamicity.
4. Exposing the potential issues that arise from this, and how to avoid the=
m
As usual, I am overwhelmed by the RubyTalk effect, so please keep
those contributions coming!