Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<h3>Definitely yes, there is a different reason for the tool disparity</h3> <hr> <p><em><strong>An IDE is more practical to construct for Java</em></strong></p> <p>Java's strict typing and documented grammar make it possible to write language-parsing IDE tools</p> <p>Ruby's duck typing and documented-by-the-Yacc-source grammar make it quite difficult to do so.</p> <p><em><strong>An IDE is more needed for Java</em></strong></p> <p>Java's verbosity makes code-writing and code-rewriting tools desireable.</p> <p>Ruby's extremely terse nature combined with the typically-no-type-declarations (of course they do appear inline with <code>Type.new</code>) make such things optional.</p> <p><em><strong>Combining the two...</em></strong></p> <p>So the combination of <em>really hard to write</em> coupled with <em>not actually needed</em> results in the balance tipping in favor of people's favorite editors.</p> <p>Giving up vi(1) for an IDE is something I would rather not do, but I do with Java because I need the IDE to write my interface implementations and such, and the fact that it parses Java makes it useful in code completion. Since with Ruby it can't and I don't need it anyway, I stick with vi(1) and TextMate.</p> <p><em><strong>Summary</em></strong></p> <p>Since you aren't buried in code, it's possible to refactor with a few reasonable edits. But while on the subject of "other Ruby developers", my Ruby question is: why does everyone (except me it seems) use function parens? Because in a few % of situations they are needed, and so the "inconsistency" is disturbing?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload