From: bonefry Date: 2005-09-30T19:06:45+09:00 Subject: Re: IBM vs. Microsoft vs. ... Ruby? Kev Jackson wrote: > So far I've not been bitten by ruby being too slow, and the good IDE is > nonsense. Ruby is fairly easy to program with a text editor > (vi/emacs/notepad etc). Similar to the person banging on about not > having a debugger - so? I've been programming "enterprise" or rather > server side Java code for 6 years and I've *never* opened a debugger. > Debuggers are not as helpful as a well written unit test (Using TestUnit > for ruby, JUnit for Java etc). Debugers are indeed overrated, but that doesn't mean they aren't usefull. How can a unit test show you why the exit point of your recursive function is not reached for example ? Emacs/VI are good but they have an almoust vertical learning curve. Notepad, I don't think so. And I really miss features of Eclipse like a good file browser, jumping to the class/method declaration, a class hierarchy viewer, code checking while typing, and all those refactoring and code generation tools. And code auto-completion could be made to work where it's possible. Of course, Emacs can be programmed to do all sorts of things, but I ain't going to learn elips just for that. The jEdit plugin also has very good functionality right now but it's far from finished. Anyway, my point was no one can be efficient with Notepad, and Emacs/VI basic functionality. Kev Jackson wrote: > I'm also not exactly sure what enterprise means in this context - I > think the most important parts missing from ruby right now are related > to libraries (for messaging, ESB etc) rather than super IDE/dev tool > support. Unfortunatelly, without a faster VM, we won't have those libraries too soon. Because if they are done in pure Ruby they might get too slow, and if they are done in C, the programmers working on them have to be proeficient with 2 languages. Before having all kinds of usefull libraries, in my oppinion, the VM's speed should increase. I have read comments on this mail list saying that speed can be optimized. Well, sometimes it cannot be optimized. Not all O(n) alghoritms can be optimized to O(1) and not all O(n*n) alghrithms can be optimized to O(n). And AI for example ussually requires backtracking and thats a O(2^n). And Ruby currently chokes on O(n).