Talk:Ruby (programming language): Difference between revisions
imported>Pat Palmer (status of Ruby and how to treat it in this article) |
imported>Pat Palmer |
||
| Line 2: | Line 2: | ||
==About the status paragraph== | ==About the status paragraph== | ||
I don't want to call this section "criticism", or anything like that, but it seems important, given my experience with Ruby so far, to place a limit on the unbridled enthusiasm which so many website express for tools that are not quite (yet) ready for prime time. Many of the tools fulfill about 90% of what a developer might needs, but none seem to be 100% yet. A single set of tools that can install on any OS and provide support for Rails, GUI, and testing has not yet appeared. Granted, many tools ''can be forced'' to work on varioius platforms by near-heroic build efforts. When these tools become, for Ruby, what Netbeans or Eclipse is to Java, or Visual Studio is to C#, then Ruby can grow into the big time. So in case any Ruby lovers are tempted to completely remove that paragraph, which I deem in advance | I don't want to call this section "criticism", or anything like that, but it seems important, given my experience with Ruby so far, to place a limit on the unbridled enthusiasm which so many website express for tools that are not quite (yet) ready for prime time. Many of the tools fulfill about 90% of what a developer might needs, but none seem to be 100% yet. A single set of tools that can install on any OS and provide support for Rails, GUI, and testing has not yet appeared. Granted, many tools ''can be forced'' to work on varioius platforms by near-heroic build efforts. When these tools become, for Ruby, what Netbeans or Eclipse is to Java, or Visual Studio is to C#, then Ruby can grow into the big time. So in case any Ruby lovers are tempted to completely remove that paragraph, which I deem in advance may upset some, please help me find a way to keep sanity about Ruby's current status, as well as hope for it's future. If you disagree, please bring evidence here (or to my talk page) first.[[User:Pat Palmer|Pat Palmer]] 11:28, 11 May 2008 (CDT) | ||
Revision as of 10:29, 11 May 2008
About the status paragraph
I don't want to call this section "criticism", or anything like that, but it seems important, given my experience with Ruby so far, to place a limit on the unbridled enthusiasm which so many website express for tools that are not quite (yet) ready for prime time. Many of the tools fulfill about 90% of what a developer might needs, but none seem to be 100% yet. A single set of tools that can install on any OS and provide support for Rails, GUI, and testing has not yet appeared. Granted, many tools can be forced to work on varioius platforms by near-heroic build efforts. When these tools become, for Ruby, what Netbeans or Eclipse is to Java, or Visual Studio is to C#, then Ruby can grow into the big time. So in case any Ruby lovers are tempted to completely remove that paragraph, which I deem in advance may upset some, please help me find a way to keep sanity about Ruby's current status, as well as hope for it's future. If you disagree, please bring evidence here (or to my talk page) first.Pat Palmer 11:28, 11 May 2008 (CDT)