Live data from Hacker News

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

blogs.msdn.com

11–20 of 39 posts

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

#11
post #10

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. Maybe OP has only watched through season 3

Dude! Spoilers!

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

#12
post #9
post #8

Earlier quoted context omitted.

"You are not ready for immutability."

"What's inside there?" "One moment of perfect Javascript."

"I will not be there to help you when you pollute the global namespace"

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

#17
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.

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

#18
post #16

Anyone know what sort of auth or security provisions are involved? It seems great for developers, but if I were a user, I would worry about giving someone a remote session at my browser's javascript console.

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

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

#19
post #16

Anyone know what sort of auth or security provisions are involved? It seems great for developers, but if I were a user, I would worry about giving someone a remote session at my browser's javascript console.

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."

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

#20

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…

Also, Javascript is basically the Shadows (mordon.js lol).

"I'd like to live just long enough to be there when they cut off your head and stick it on a pike, as a warning to the next ten generations that some languages come with too high a price. I want to look up into your lifeless eyes and wave like this."

Post reply on HN