Re:Expose any Ruby object over the web. An interesting littl...
by cageface on Tuesday November 16, 2010 @11:37AM
(#1910602)
The problem with sharp edges in programming languages is that you might be perfectly sane and careful on your own but you must also trust everybody else you code with to not only exercise the same restraint but to also point their sharp edges in roughly the same direction.
[ Parent
| on HN ]
Re:Expose any Ruby object over the web. An interesting littl...
by ericb on Tuesday November 16, 2010 @12:12PM
(#1910735)
You could argue it pushes the problem up the stack to the hiring stage.
Re:Expose any Ruby object over the web. An interesting littl...
by patio11 on Tuesday November 16, 2010 @02:00PM
(#1911153)
It pushes the problem to the hiring stage at the company which wrote the OSS pulled in by the gem pulled in by the gem pulled in by the update to your Twitter integration plugin.
For kicks, go open script/console, type [].methods.size, and create a passing test for that number. It will fail, eventually. The code that kills it may surprise you.
Re:Expose any Ruby object over the web. An interesting littl...
by ericb on Tuesday November 16, 2010 @05:59PM
(#1912090)
This is an interesting idea, and I will try it. Added methods mainly gets you if there is a name collision, it seems to me. Changing core methods, which is also possible, scares the bejeezus out of me.