News for hackers. Stuff that matters.
Re:How JavaScript works: inside the V8 engine by mraleph on Monday August 21, 2017 @04:09PM (#15067436)
> is like IRHydra

It does 'IR' part of the IRHydra, but it does not give you another important feature - ability to see how your function evolved over time and figure out reasons for it. Loading files one by one in search for the right version is pretty cumbersome.

I was always hoping that V8 will eventually get proper Dev Tools integration for compiler / runtime internals - and I think things have finally started happening in that area.

Re:How JavaScript works: inside the V8 engine by mncharity on Monday August 21, 2017 @04:37PM (#15067663)
> cumbersome

Yes, turbolizer currently lacks some of IRHydra/2's mature featurefulness. No pretty "you're deopt is here". I've no idea whether Google would welcome contributions or not.

> I was always hoping that V8 will eventually get proper Dev Tools integration for compiler / runtime internals

Wistful sigh.