New IDE: code bubbles

I think there's some really interesting stuff here that should be leveraged. What I like best is that it really focuses your mind on the task at hand. You don't spend a lot of time looking through large amounts of code just to find a few things.

I wouldn't like the UI directly as presented, but there's certainly a starting point there.

Really though, don't know what kind of programmer would accept line wrap on code. Urf.

Looks pretty cool actually. There are often times when I need to see a little bit of code from a number of files, to trace what's happening. Anyone care to make an emacs mode for this?:-)

This is awesome!

I'm kind of a weird mixed-bread developer. I'm now a heavy Vim user, but was once a heavy IntelliJ IDEA user. I'm also currently a heavy Resharper user at work. I understand the importance of really solid, visual tools, but I also understand the importance of simplicity and flexibility. There is a middle ground, I know it.

As an aside, I think that the GUI toolkit confusion is one of the biggest blockers to this sort of innovation. Terminal emulation is just the lowest common denominator. HTML/JS/CSS is the closest thing we have towards a portable, successful GUI toolkit. And it's simply still not quite ready to fight the advanced desktop graphics battle necessary for this sort of new bread of tools.

It's better than normal eclipse for sure - you get the arrow link between related methods, etc.

What I meant is that in Vim I go to a name in ctags. That's what happens - whether I'm in the same file, or different, or I looked at that tag before. Type in tag name -> go - that's all that happens.

With code bubbles, I could have the bubble already open, but just off the screen. Or maybe it's open in another dependency. Or maybe it's not open at all. I have to look at the screen, localise the bubble, make a decision and then do the action (either click existing bubble, or open a new one). Of course it's too early to criticise it, without testing beforehand. But it definitely got my attention, as something I tried to avoid. Having one good way to access stuff == less thinking.

Let's say that Vim is stateless, but bubbles are stateful :)

Interesting idea. Drawing a line between two procedures to find the shortest call path between them could save time navigating an unfamiliar codebase.

Edit: Also interesting - storing an old debug session with state and being able to visually compare that with a debug session made after code changes.