[paulirish]

> If Mozilla truly reverse-engineers Apple's remote debugging protocol it would be a godsend for us.

Google did this a while ago: https://github.com/google/ios-webkit-debug-proxy It works well for connecting Chrome DevTools to Safari, automating Mobile Safari through ChromeDriver, or hooking up your iOS device to a private instance of WebPageTest.

[kibwen]

Thanks, I've never heard of this before and it sounds very useful.

...Or rather, it would be very useful were it not for the fact that it only appears to run on Linux and OS X, whereas my employer-granted computer is running—drumroll, please—Windows XP! And like I said, these are all internal applications, and I don't have the authority to VPN in on any computer that I please.

Ah well. Enterprise bureaucracy strikes again. :\

[robin_reala]

Have you ever thought about quitting and working for a company that doesn’t treat you like a child?

[kibwen]

What, and not get paid to spend half my time on HN while the ravages of Sarbanes-Oxley grind productivity to a halt?

(The funniest thing is that we're not even a public company, and have no shareholders to defraud. That's right, we opt in to Sox-compliance.)

[mercer]

That's interesting. Can you tell us why your company opted in?

[daxelrod]

I've seen companies adopt stricter compliance rules than required by law when their customers demand it. I have no particular knowledge of this specific case.

[magicalist]

That sucks, though it would definitely be much easier to run a virtual linux instance on that box than an OS X one as someone else suggested.

I will say that being able to debug pages in mobile safari directly (via Safari on a mac) makes a huge difference, so if this works even partially as well, it's worth investigating if you can get it running.

[23andwalnut]

There is is a windows version too: https://github.com/artygus/ios-webkit-debug-proxy-win32

[Raphael]

Linux virtual machine.

[campd]

And that work is key to the stuff we're doing. Thanks again, Chrome folks!