* Annotated code, line by line, with the relevant commit and comment next to it. Drop an egg in your remote source and go. Results are organized within the file hiercharchy and are collapsible. * When searching for something, you get a full, scrollable preview of the surrounding context of each matching result. It's an undo/redo button on steroids that keeps months of history. * Local file history separate from git history, with fantastic navigation/diffing support.

You will sometimes wonder why your coworkers are struggling to understand code references and then you realize they don't have this power-tool available to them. If you're working on a large, unfamiliar codebase, this is a godsend. Doesn't always work, but even when it doesn't, it usually makes good guesses and lets me select from a list. render() actually calling? Instantly I'm looking inside the relevant function, even if there are hundreds of functions with the same name. * Its uncanny ability to find references and declarations in both Python and JavaScript, even when the references are dynamic. Company performance was atrocious, and that really screwed over people that took part in the employee share program, but they somehow managed to make it over to get acquired by Micro Focus.

They eventually realized that the whole IDE market was dead, so that was spun off into CodeGear, JBuilder was relaunched as an Eclipse distribution with 'premium' extensions, and CodeGear was ultimately sold to Embarcadero, while the rest of the company was trying to refocus on producing software for other parts of the development lifecycle, from requirements management to automated testing and test management (hence Segue) to SCM. Well, until Eclipse came along: within 18 months, JBuilder license sales dropped to essentially zero.

Apparently, JBuiler used to be their #1 cash cow. As a former Borland employee (not for very long, 2006-2009, and actually working in their Austrian offices, which originally became part of the company through the Segue acquisition), I certainly didn't have the complete picture, but our managers, even going as far as those located in Cupertino, and later Austin, were quite open about what Borland's issue was: even with the rise of Java, they thought they could continue in the IDE business like they did before.

Borland jbuilder 9 enterprise