We know how slow it is and whether or not it is important.
We're not really worried about it, but we do look forward to upcoming speed increases..
What we are generally interested in is doing things and making things with Ruby 
Focus on that, and you'll find that Ruby is either good or not for you.
People here generally use other languages as well, and are not Ruby only people.
We appreciate Ruby because of other languages in many cases.
There is actually a great deal of pragmatism in the Ruby community.
If there is a better approach that is not Ruby we will recommend it and use it.
So who specifically would my remarks be offending, assuming I was
being less than civil in this thread ?
···
On Sep 25, 2:08 pm, Phlip <phlip2...@gmail.com> wrote:
> Well pardon me for causing "trouble" simply by talking about the
> inefficiencies of Ruby... If the Ruby community weren't so sensitive
> about this sort of topic we might well have a more powerful (faster,
> more efficient) Ruby language to use.(Another trolloid technique is frequently returning to appeasement and
abasement, but I'll make one more attempt at rationality here!)You just said "if the newsgroup weren't so civilized, and demanding of
polite discourse, Ruby might be a better language."That's kind'a silly.
--
Phlip
The feeling that there is only one tool for all tasks generally leads
to the failure to recognize the right tool for the right job.
I have a nice big basket of languages I can draw upon when making
assessments as to which one might be best suited to a particular task
rather than only using one language for everything at the expense of
he who employs me since it can take quite some time to make Ruby work
in place of a better method for coding stored procs such as when SQL
Server 2005 is being used and C# might be a better choice in terms of
runtime performance.
···
On Sep 25, 2:40 pm, John Joyce <dangerwillrobinsondan...@gmail.com> wrote:
We know how slow it is and whether or not it is important.
We're not really worried about it, but we do look forward to upcoming
speed increases..
What we are generally interested in is doing things and making things
with Ruby
Focus on that, and you'll find that Ruby is either good or not for you.
People here generally use other languages as well, and are not Ruby
only people.
We appreciate Ruby because of other languages in many cases.
There is actually a great deal of pragmatism in the Ruby community.
If there is a better approach that is not Ruby we will recommend it
and use it.
> We know how slow it is and whether or not it is important.
> We're not really worried about it, but we do look forward to upcoming
> speed increases..
> What we are generally interested in is doing things and making things
> with Ruby
> Focus on that, and you'll find that Ruby is either good or not for you.
> People here generally use other languages as well, and are not Ruby
> only people.
> We appreciate Ruby because of other languages in many cases.
> There is actually a great deal of pragmatism in the Ruby community.
> If there is a better approach that is not Ruby we will recommend it
> and use it.The feeling that there is only one tool for all tasks generally leads
to the failure to recognize the right tool for the right job.I have a nice big basket of languages I can draw upon when making
assessments as to which one might be best suited to a particular task
rather than only using one language for everything at the expense of
he who employs me since it can take quite some time to make Ruby work
in place of a better method for coding stored procs such as when SQL
Server 2005 is being used and C# might be a better choice in terms of
runtime performance.
Okay, here's where I'm ready to call troll. Compare and contrast the
paragraph above with this quote from a previous message by "Ruby Maniac":
Recently I was given the task of importing data from one SQL Server
2005 database to another and rather than allow a co-worker use C#
to code a faster way to accomplish this I chose to use Ruby even
though the work took weeks to complete and that Moron who wanted to
use C# might have completed the work in less than a day I know Ruby
as a superior language is well worth the weeks of time my team has
invested in the process or doing a rather simple data import task.
Ruby rocks !
Yeah. That'd be a direct contradiction.
*plonk*
--Greg
···
On Wed, Sep 26, 2007 at 10:00:03AM +0900, Ruby Maniac wrote:
On Sep 25, 2:40 pm, John Joyce <dangerwillrobinsondan...@gmail.com> > wrote:
Ruby Manic, it seems every where I look for you I seem to see tendencies for
being a Pain In The Neck. If I could, I'd probably set my MUA to ignore all
threats started by you....
I am usually not one to use the word Troll -- but I think you are getting to
be classifiable as one!
Don't like that Ruby 2.0 is not out yet? Get off your butt and help them.
Think Ruby 1.8.x is to slow? Get over it or don't use it.
Can't stand the possibility of reverse engineering? Then employ an obfuscater
and write a Ruby To Machine Code compiler for the result -- I would love to
use one! Maybe you could even work out a way to use the intermediate
representation to further obfuscate the code.
If you can't stand the way Ruby does things, ether put up or push off. No one
forces you to use Ruby. I doubt many businesses would stipulate it ether
unless they require Rails people.
Even installed YARV for testing yet?
Using one tool for every thing is bad for business. I think it's nice when
some one has a 'Just for fun' moment. Such as doing a project in C they would
usually do in Shell/Batch or vice versa.
I've learned a number of languages, each is useful and worth using at some
point. My new target is Scheme -- I find Ruby works best for most regular
tasks. And has more portability for 'in house' needs here then POSIX Shell
scripting if tasks are more complex then I would care to type into a CLI.
In business, using Ruby in place of C# when the trade off looks like Weeks vs
Days. Is just stupid in my humble opinion from the point of view of people
having to *pay* for such work. When no one is footing the bill for it, it's
ok. Maybe this is why I prefer Vim to Notepad. The effect fullness out ways
the cost of learning.
Don't start threads to whine, poke, or encourage chaos. Ether make do with
what you do have, help make it better, or go troll some other seas.
If Ruby won't cut it for you, maybe you should try Python. But I wouldn't wish
you on the Python community !
TerryP.
···
--
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com