Live data from Hacker News

Why we made Vorlon.js and how to use it to debug your JavaScript remotely

blogs.msdn.com

31–39 of 39 posts

Re: Why we made Vorlon.js and how to use it to debug your JavaScript remotely

#31
I cloned the project from https://github.com/MicrosoftDX/Vorlonjs.git to play around with creating a plugin. The code in the plugin TS files (e.g. `Plugins/Vorlon/plugins/sample/sample.ts`) keeps reporting errors like `Cannot find name 'Core'`, `Cannot find name 'RuntimeSide'` etc. Is that expected?

I have run `npm i` from the project root.

  $ node -v && npm -v
  v0.10.36
  1.4.28

Re: Why we made Vorlon.js and how to use it to debug your JavaScript remotely

#32
post #26

I'm disappointed if like it's namesake it doesn't give vague, disturbing, portent information to the console. "If you go to 'undefined', you will die"

Still better than what vogon.js emits, right?

Oh freddled gruntbuggly,

Thy syntax errors are to me

As drunken COBOL coders

On a Brainfuck spree.

Re: Why we made Vorlon.js and how to use it to debug your JavaScript remotely

#33

I cloned the project from https://github.com/MicrosoftDX/Vorlonjs.git to play around with creating a plugin. The code in the plugin TS files (e.g. `Plugins/Vorlon/plugins/sample/sample.ts`) keeps reporting errors like `Cannot find name 'Core'`, `Cannot find name 'RuntimeSide'` etc. Is that expected? I have run `npm i` from the project root. $ node -v && npm -v v0.10.36 1.4.28

Can you please try a npm install at the root folder level?

Re: Why we made Vorlon.js and how to use it to debug your JavaScript remotely

#34

I'm getting the following popup when I visit the page: The page at blogs.msdn.com says: The target of the callback could not be found I really want to like Microsoft, but it's the little things like these that make me uneasy. Especially when you're blogging about debugging javascript.

Really sorry about that. Our blog platform is a crap. You can directly go to www.vorlonjs.com for more info and better web site:)

Re: Why we made Vorlon.js and how to use it to debug your JavaScript remotely

#35
post #19

Earlier quoted context omitted.

It won't have any access the hosting website doesn't already have... It's just interactive instead of strictly the delivered JS.

I'm sure that's the intended state of affairs. But there's a difference -- at once psychological and technical -- between "trusting someone else's application code" and "letting their developers have remote debugging access to your machine."

They don't have any remote debugging access they wouldn't have... the JS still runs in your browser, sandboxed to the window with their website in it... it can't do anything else that any JS could do... it may be a psychological difference, but it's not a technical one...

I've considered a number of times about actually shipping dom-diffs so that support could see what a user is seeing. This technology has been around for a while.

Re: Why we made Vorlon.js and how to use it to debug your JavaScript remotely

#39

Based on this, the second reason is because the Vorlons are one of the wisest and ancient race of the universe and thus, they are helpful as diplomats between younger races. What? No. That's not how the Vorlons worked at all . Also, Javascript is basically the Shadows (mordon.js lol). Wonder what langauges/frameworks map onto other Babylon 5 concepts? Angular -> Earth Alliance? Enterprisey but not super elegant, and…

> What? No. That's not how the Vorlons worked at all.

But it is how they wanted to be perceived. ;)

Granted, Microsoft can quite easily say "We have always been here."

Post reply on HN