5 ms·
It's kind of silly, the major benefit of using Ruby (or JavaScript nowadays) is to iterate quickly. But then, some of their users spend months turning a text ed
by emsy 12y ago
It's kind of silly, the major benefit of using Ruby (or JavaScript nowadays) is to iterate quickly. But then, some of their users spend months turning a text editor into an IDE just to waste precious hours on spelling errors.
- Argorak 12y agoMost text editors have naive autocomplete (using a words list and words they see), which catches 99% of these errors.
- pmontra 12y agoFor example I use pabbrev mode in emacs, which learns what I type. It hints me away from most misspellings because it suggests the correct alternatives before I type them. Most of the long method and variable names for me are a prefix plus a TAB. Nevertheless I'll try this gem.
- emsy 12y agoI have experienced some problems with this kind of autocomplete in a JS project. -Two methods shouldn't have a similar name, so you try to avoid it, possibly leaving you with a worse abstraction. -You usually need to have all files open or at the same location, so modularization is discouraged. -Libraries are usually not picked up by it. -If you make a spelling error on the first usage you now have this spelling error everywhere. Naive autocomplete is much better than none, but it's still not in the same league as context sensitive autocomplete.
- Argorak 12y agoYMMV, but I don't experience any of those problems. Also, I don't see where same names pose any problems. Most advanced language plugins pick up libraries.