<img src="/images/posts/vorlonjs/vorlonjs.jpg" />
Preface: This is quite an opinionated post, and everything here is said without have had a chat with the team, and is purely based upon the observations I’ve made since the announcement and by following the project. I might be completely wrong in my criticism.
I’ve been following the vorlon.js project for a while now, and recently I’ve started to notice a big amount of work being put into building a “DOM Explorer” and other parts of “DevTools-like front-end”, which trigger this tweet:
<figure> <blockquote class=“twitter-tweet” lang=“en”><p lang=“en” dir=“ltr”><a href=“https://twitter.com/deltakosh”>@deltakosh</a> <a href=“https://twitter.com/meulta”>@meulta</a> <a href=“https://twitter.com/pierlag”>@pierlag</a> Why make <a href=“https://twitter.com/VorlonJS”>@vorlonjs</a>'s own DOM Explorer over Firefox or Chrome DevTools? We already have it :)</p>— Kenneth Auchenberg (@auchenberg) <a href=“https://twitter.com/auchenberg/status/613558197350064129”>June 24, 2015</a></blockquote> </figure>
To me, this particular front-end work seems completely unnecessary as a front-end for this kinda of functionality already exists — and has for years.
Vorlon.js doesn’t bring anything new to the table
Vorlon.js is built on node.js and is using socket.io to manage it’s connections to the browsers and the front-end is simply communicating to the central (local) server that provides an aggregated view of the browser information.
This architecture isn’t new.
This is exactly how the built-in browser DevTools are working in modern browser like Chrome, Firefox and Safari. The front-end is a simply client of a remote debugging server hosted by the browser.
However there’s a difference, and that’s the built-in DevTools doesn’t have a notion of other browsers. But this functionality was explored by Patrick Mueller in the Weinre project. Weinre enabled users to use Safari Web Inspector with other browsers, via a much similar architecture to vorlon.js, as it’s also relied upon a script injection technique to emulate the Webkit remote debugging protocol.
Today the Weinre project is kinda dead, but recently we have also seen commercial solutions like GhostLab which is using a similar approach, to enable Chrome DevTools to be connected to multiple browsers. In my view GhostLab is the new and modern flavour of Weinre.
However vorlon.js adds one new thing to the table, and that’s plugins, that allows developers to write “extensions” in order to inject custom functionality. But this extension layer could easily have been built on top of the existing tooling and protocols, instead of re-inventing everything again.
Re-implementing a front-end that already exists
My first specific criticism of the vorlon.js is that the team currently is re-implementing much of the functionality that already exists inside tools like Chrome DevTools and Firefox DevTools. These projects are both open-source, and hundreds of people has over the last many years, spent I-dont-know-how-many man-hours on tweaking both the UI and the functionality of their “DOM Explores” and “Networking inspectors”
So I simply don’t understand, why you would completely disregard what’s already out there (and work’s pretty damn well), and start rolling your own home-grown front-end.
When taking a look at the current state of the home-rolled front-end in vorlon.js it’s sub-pair with existing tools. It’s even sub-pair with Firebug that was super-seeded by “native’ DevTools years ago. From this point it will take the vorlon.js team considerable time to “catch-up” with even basic functionality like script debugging and editing, which is functionality that most developers, these days take for granted.
For absolutely no reason.
Even Weinre and GhostLab realized that re-implementing the front-end would be massiv task, and probably also a waste of resources, so from the beginning GhostLab is simply re-using Chrome DevTools inside their app, and Weinre is using Safari’s WebInspector. Wise decisions.
The fundamental problem is the viewport sandbox and it’s limitations
This leads me to my second criticism and that’s the basic assumption vorlon.js and similar solutions like Weinre are built upon: They rely on instrumentation of the running application inside the “viewport sandbox” using dynamic script injection.
Let me explain why this is fundamental problem by showing you this illustration:
When running inside the “viewport sandbox” along with the application itself, the debugger/tool is limited by the number of API’s available, and as we speak there isn’t many debugging-focused API’s available for one reason: Security.
Getting access to the memory heap and other internal parts of the runtime won’t be secure with the security model we have on the web.
This means that debugging tools running inside this sandbox has to rely on dynamic code instrumentation that injects observers and other logic in order to “extract” the interesting information from the runtime. This is a lot of work, and by design, we won’t be able to extract much of the “interesting” information thats’ needed for Profilers, Network monitors, Emulators, etc.
This constraint also exists for vorlon.js, and that’s why vorlon.js from the very beginning won’t be able to provide what’s required of a modern remote debugging tool. It’s access to information is simply too limited.
This is also why modern DevTools aren’t relaying on dynamic script injection, but instead is using the remote debugging protocols. These are built into every modern browser, and aren’t limited by the “viewport sandbox”. They provides a much more advanced set of API’s for specifically created debugging and most importantly provided and maintained by the browser vendors.
What should be the focus of vorlon.js
Remote Debugging protocols already exists, and is wildly used by the browsers’s DevTools and other tools such as Adobe Brackets. There’s a proven need for why these protocols and API’s can’t be exposed inside the viewport, and why these are exposed as a separate interface to the browsers.
The focus shouldn’t be re-implementing a front-end that already exists, and spending time re-implementing debugging-API’s that the browser-vendors already provides in their remote debugging protocols.
This is why I find another Microsoft project much more intersting, and that’s the IE Diagnostics Adapter from the IE F12 tools team, who has spent the time building an adaptor that makes it possible to use existing tools like Chrome DevTools and Adobe Brackets with IE. That’s true innovation, and focus where it needs to be.
We as a community, should get out of the not-invented-here-syndrome, and focus on how we can re-use the logic and tools that’s already been built by our wonderful community.
If vorlon.js for example had used the existing Chrome Remote Debugging protocol instead of inventing it’s own socket.io-based thing, and embraced RemoteDebug, tools like Microsoft’s own Visual Studio would work for script debugging (I might be wrong here), and the team wouldn’t have to re-invent the front-end for Console, as Chrome DevTools would work out of the box. That would have given vorlon.js a much better starting point, than starting with nothing.
So to put it on an edge, vorlon.js seems to be yet-another Microsoft project that’s driven by the not-invented-here-syndrome, and that’s a shame.
I sincerely think we can do better. We should focus on real innovation instead of re-inventing wheels.
We desperately a better web development workflow, so let’s built it by keeping our focus on solving the real problems.
That’s it for now.