2 ms·
DTrace works exactly like mdb, it requires knowledge about V8 internals. The problem is haphazardly upgrading the V8 version without thinking about the consequ
by 4ad 12y ago
DTrace works exactly like mdb, it requires knowledge about V8 internals.
The problem is haphazardly upgrading the V8 version without thinking about the consequences. This is not how you do release engineering, especially since io.js is advertised as stable.
Stable doesn't mean "it works for me", it means you provide some formal guarantees to downstream consumers about the stability of exposed interfaces.
I'm very well aware that some (most?) people don't care about things like good introspection support and stability, but it's pretty pathetic to see factual information being downvoted because people don't agree with the message.
- Joe8Bit 12y agoI think "haphazardly" might be a little harsh, my understanding is that the IO.js core team fully understood the introspection regressions that would occur when bumping V8; but they took the descison that improved runtime performance combined with native support MANY new language features meant the regressions were acceptable. I agree fwiw. They favoured the many (who would use the new V8's features) over the few (who valued DTrace etc) I haven't heard any real claims as to IO.js instability, and have been using it production at scale for several months myself.