Rusty Shackleford wrote:I think it is a non-issue.
It is not that difficult to replicate the contract of any method. Your code is copyrighted, so that will stop most people from copying and pasting your code. The bad guys are almost always terrific programmers so can easily reverse engineer your code no matter what you do or just figure out what a method is doing and just write their own version.
How many millions of dollars does a company like Microsoft spend to try and stop this? Their code is always cracked and broken in short order. All without source code.
Balaji Loganathan wrote:Does E-TextEditor offer Code-Assistance (Ctrl + Space or Ctrl + Shift + Space) if I have installed RoR bundles ?
Balaji Loganathan wrote:Could you please point to download link of GVIM ?
Lasse Koskela wrote:
Frankly, Textmate was the best software purchase I've made in a long time - I would encourage you to try it out.
Agreed. TextMate is a nice editor but it's only available for the Mac. If you happen to be on Windows, you might want to give E-TextEditor a try - it advertises itself as bringing the "power of TextMate on Windows". Apparently it's compatible with TextMate's bundles, too.
hassan bousnguar wrote:Hello,
i really ruby was created for concurrent java and other business application or rubu is a simple scripting language like php, and cannot be used in risked application.
Hassan
Michael Sullivan wrote:
What do you think the optimum size is for a team that uses Ruby as it's primary language? Do you think Ruby has advantages/disadvantages if the team is distributed geographically?
Michael Sullivan wrote:
How can Ruby best practices help large teams create clean code bases?
Michael Sullivan wrote:
Are there best practices that help with deployment, an area that still seems difficult?
Michael Sullivan wrote:
Can best practices mitigate the comparatively slow performance of Ruby?
Michael Sullivan wrote:
Is it possible, with best practices, to maintain an increased level of productivity with Ruby?
Michael Sullivan wrote:
Metaprogramming attitudes at ThoughWorks seemed to trend towards: useful in small doses. Are there best practices to help developers understand how much and how often?
RBP wrote:
My general rule of thumb is to ignore all of these advanced Ruby features until my code
illustrates a need for them. If I write several method calls that appear to do almost the
same thing with a different name, I might be able to leverage method_missing. If I want
to endow certain objects with some handy shortcuts, but leave the option of
instantiating a simple, unadorned core object, I might look into mixing in some sin-
gleton methods using extend. By the end of the day, in a large or complicated applica-
tion, I may end up using a large subset of the techniques dicussed here. But if I started
out by thinking about what dynamic features my code needed rather than what re-
quirements it must satisfy, development would come to a confusing, grinding halt.
So here’s my advice about making use of the information in this chapter: just make a
mental note of what you’ve learned here, and then wait until some code jumps out at
you and seems to be begging to be cleaned up using one of the techniques shown here.
If it works out well, you’ve probably made a good decision. If it seems like more trouble
than it’s worth, bail out and wait for the next bit of code to alert you again. Keep
repeating this process and you’ll find a good balance for how dynamic your code really
needs to be.
Michael Sullivan wrote:
And finally, how do you see Ruby fitting into a Polygot programming model with other languages like Java, C#, shell scripting, etc?
Vamsi S Krishna wrote:For unit testing I tried Shoulda and Rspec
Integration testing - Webrat
code coverage - Rcov
There are so many choices for a testing suite I am wondering which one is the best to choose to have a complete testing (like unit, functional, integration and code coverage).
César Guzmán wrote:Greg
Here's another one, which IDEs do you recommend to work with Ruby on every platform (windows/mac/Linux) and what about working on visual components?
Vyas Sanzgiri wrote:That is interesting what about the learning curve as compared to other languages
Balaji Loganathan wrote:Hi Gregory,
We have been developing Ruby on Rails projects for quite a while and one thing that kind of scare us is "source code exposure". Coming from J2EE background I wasn't much worried about "source code exposure" as Java files were compiled to .classes (and we can further even obfuscate as well).
Could you please suggest me on what could be best approach to protect the ruby/rails source code ? Should we protect or not and so on ?
Thank you.
Regards
Balaji D Loganathan
Balaji Loganathan wrote:Thanks Lasse.
They are all ROR web applications. What i am feeling insecure is ability to see the actual source code by anyone who got access to the server box.
Right now i protect the webapp folder access using Linux user group options.