Terminal integration. Which is invaluable as it's a big waste of time cross referencing your projects acroess different parallel contexes.
What's MacVim give you? I never got the point. Everything I've seen also existed in the terminal with a few simple vimrc config. Mouse/trackpad, clipboard integration, OSX commands.
The experimental renderer in MacVim creates a much more fluid editing experience than Vim, I find. Other than that, I think the only thing I use from time to time that is MacVim-specific is command-S, which aliases nicely to :w or to a file browser where you can enter a file name if the file is unnamed.
MacVim (and GVim on Linux) have better color scheme support. Solarize is great.
MacVim also works with PeepOpen, which was just a jaw-dropping upgrade from tab-completing all my file paths from the project root. It practically reads my mind.
I'm thinking I will give FuzzyFinder a try soonish, though, since it would also work on Linux.
About MacVim vs vim and 'color scheme support' and 'solarize': Actually the issue is with Terminal.app which has some weird setup where changing the background is either impossible or always looks horrible.
Also it's particularly difficult to get Solarized setup in a terminal using 256 colors rather than manually resetting the 16 colors of your terminal to custom values.
If you have a sane terminal, vim works fine with 256 color support. A lot of people on OSX use iTerm 2 which I hear has fine 256 color support. I just use gnome-terminal on Linux that's had support forever and dropped solarized since the maintainer is not interested in making any setup work besides gVim/MacVim it seems.
Also got hooked on vim, and couldn't thank Textmate's inactivity more for I may have never been pushed in the right direction and discovered the wonderful efficiency of the vim paradigm.
If I were to use Textmate now, it would need to be just a faster vim, with a less clunky vimscript, and it'd need to embed in a terminal, as vim made it possible for me to do everything on the command line and truly use working directories as my sole division between contextual workspaces.
First of all, the biggest concern is attack surface. If credit cards went through your server, any complex web application would have a number of locations where the CC would be logged in plaintext. In this case a compromise would not only make it possible to collect new credit cards as they are entered into the system, but also past credit cards in logs. Any of the three options: iframes, hosted pages, and recurly.js, reduce this attack surface, because credit cards never pass through your backend to be logged, and the Recurly backend being PCI level 1, clearly prevents them from ever being logged.
Now, if say your web application was vulnerable to a XSS attack on one of your payment pages, it would be just as easy to replace the iframe src, and spoof the CC processor's hosted page, as it would be to drop in some js that reads the value of input fields and tunnels them out to the attacker. On that note... even an integration as seemingly foolproof as linking to a third party hosted page is vulnerable to the same attack, by replacing the href of the link.
The takeaway is that Recurly.js removes as much of the PCI scope as we possibly could without us building and hosting your entire website. Also, watch out for XSS attacks, and don't let your server get rooted.
I'm the author. I'll be sure to put a notice at the top of the readme that it requires jQuery. Also, I agree with you. The jQuery dependency will be removed eventually. It was a time saver in the short term as we do a lot of DOM manipulation.
I'm a paying recurly customer, and I think depending on jQuery is totally fine; even if we had to include jQuery on a payment page when we didn't use it anywhere else on our site, that wouldn't be any trouble.
Please, use your precious development time on more pressing issues related to making payment's even easier to accept and integrate!
What's MacVim give you? I never got the point. Everything I've seen also existed in the terminal with a few simple vimrc config. Mouse/trackpad, clipboard integration, OSX commands.