3 ms·

I totally agree; RubyMine is my 'home base' when working on Rails apps, because its debugger beats anything I've seen for ruby/rails especially, easy to run ser

by veidr 13y ago

I totally agree; RubyMine is my 'home base' when working on Rails apps, because its debugger beats anything I've seen for ruby/rails especially, easy to run server/tests/console under any environment, the best code completion for ruby I've seen, tons of smart navigation options, refactoring right-click 'run this test/spec' feature, etc etc. I still use ST3, TM2, and from time to time other editors whenever I want... but RubyMine, being a complete IDE, does so much more than those tools. Managing your product in RubyMine doesn't preclude using other editors alongside it for more intensive code editing sessions, if desired.

veidr 13y ago
I forgot to add why you would want to do that: because when judged just on the merits of being a well-behaved app that adheres to OS X conventions, it is awfully, terribly, horribly bad (as are most Java GUI apps). Most of its menus are not really OS X menus at all, they are transient floating windows with wrong behavior. It doesn't have normal windows -- some can only be floating windows, but they float over some windows and not others. You can spend hours tweaking the keyboard shortcuts, but you will never get them quite sane. Text drag and drop isn't right. Tools like Typinator and multi-clipboard managers don't tend to work well with it. It doesn't interact with the system pasteboard well. In short, as a Mac app, it's totally gross. But as an IDE, it is very powerful. Using it is a pain if you really want a nice Mac tool, but if you think about it the same way as you think about logging into a remote Linux server to do some work, or doing some task in Windows in VMWare Fusion, it's not that bad. The area where is falls short the most is the actual editing of code, because (at least for me) that is a long, iterative task, where the OS conventions and staying true to the standard ways of doing things are most important.

by veidr 13y ago

veidr 13y ago

I forgot to add why you would want to do that: because when judged just on the merits of being a well-behaved app that adheres to OS X conventions, it is awfully, terribly, horribly bad (as are most Java GUI apps). Most of its menus are not really OS X menus at all, they are transient floating windows with wrong behavior. It doesn't have normal windows -- some can only be floating windows, but they float over some windows and not others. You can spend hours tweaking the keyboard shortcuts, but you will never get them quite sane. Text drag and drop isn't right. Tools like Typinator and multi-clipboard managers don't tend to work well with it. It doesn't interact with the system pasteboard well. In short, as a Mac app, it's totally gross. But as an IDE, it is very powerful. Using it is a pain if you really want a nice Mac tool, but if you think about it the same way as you think about logging into a remote Linux server to do some work, or doing some task in Windows in VMWare Fusion, it's not that bad. The area where is falls short the most is the actual editing of code, because (at least for me) that is a long, iterative task, where the OS conventions and staying true to the standard ways of doing things are most important.