Joe8Bit

Also based in the UK, and as far as I know you're right. To reiterate, speak to the a solicitor, but I've been told informally by several solicitor acquaintances they're usually unenforceable.

I also suspect the relative ease of relocating a large number Australian's to the UK would have a big impact (ease of getting visa's etc).

I agree, a similar system is put in place at Quibb, it works quite well.

And whoever is running this proxy will _promise_ not to log any sensitive information (API keys not the least) or otherwise use/modify the response for their own ends?

Not to mention that the API endpoint is HTTP only, meaning everything is broadcast in the clear.

Also, cross origin requests are perfectly possible without this library, it's precisely why we use JSONP and CORS.

When it comes to security, this library is a collection of anti-patterns. As well as the JS anti-pattern of not overwriting native objects, such as XMLHttpRequest in this context.

Routing all your x-domain requests through an unknown third part via vanilla HTTP? What could possibly go wrong?

It's interesting, I know several engineers who've worked at (or currently work at) the Mail Online and they all talk about the 'Daily Mail Tax' salary bump they required in order to slice off a little bit of their soul to work there.

Technical recruiters I know talk about it too, how they describe this very cool roll their trying to fill, deliberately obfuscating who it's for, before eventually having to reveal it and usually loosing most of their potentials.

Very sad. Few novels have left such a lasting impression on me, or evidentially many others, as his Culture series.

I agree with you, it SHOULD be open, but there's nothing in the BBC's CURRENT public service charter that would MANDATE it to give preference to open-source eco-systems/platforms. As I said, I happen to agree with you: it SHOULD read that. But it currently doesn't, as far as I'm aware.

Going back to the original point, it's not been suggested this is a POLICY decision on the part of the BBC to prefer one platform over the other (be it open or closed) but rather a pragmatic one based on the technical/test complexity of developing for the Android platform (and supporting MANY devices on it). I can personally attest to this last fact, as anyone can who has built cross-platform native mobile apps.

As far as I've understood it, the BBC isn't ignoring Android, the rollout of new features is simply delayed for a platform that's logistically significantly more complex to roll out multi-device supporting apps too.

Also, I'm not too sure about it being against the BBC's 'contract', could you let me know what you're referring to? As far as I'm aware the BBC has no legislative or regulatory duty to favour open platforms.

Corporate network flagged this domain as blocked for 'phishing', fyi.

"Estimated 21 cores" I have four.

Mine either, Chrome 25 (stable) Mountain Lion.

They also have merit during a 'tour' within your conversion process e.g. emphasising features and value points.

But I agree with the more general principle, if you have to use these to onboard users WITHIN your experience, something has probably gone wrong.

Same here, I ended-up deleting the node in Firebug.

Maybe a naive question, please forgive if it is, but why does using a string make it harder to maintain?

I'm curious about the intended audience for this product: people working professionally in this area are likely to have a predefined workflow that's going to be difficult to fit this into be that: it's 'just not VIM'; it being outside of version control and/or build systems; or any number of other reasons (both with objective and subjective merit).

Is the audience not these professional people? Is it aimed more at the shallower end of the learning curve?

There are a couple of companies that are doing this commercially (TagMan, for instance) who might be a little nervous now that Google has entered the space.

I was going to do something very similar to this, so thanks for saving me the effort! :)

I already built a couple Github jQuery widgets that people in this thread might also find relevant: http://www.joepettersson.com/demo/pretty-gist/ http://www.joepettersson.com/demo/jquery-github-widget/

You can init Sublime (and open/edit files) from the command line relatively easily[1] and there's a plugin that will allow you run shell commands from within Sublime Text[2].

1: http://www.sublimetext.com/docs/2/osx_command_line.html 2: https://github.com/misfo/Shell-Turtlestein (or from Package Control)

EDIT: Ahh I see you edited, nevermind! But you can split the windows easily too!

We use Google Apps for internal email and have nothing but good things to say about it.

We use MailGun for everything else (transactional's and to send from our internal email marketing app). It's cheap'ish, stable, and the API is rock soild. I recommend them to anyone who asks.

No problems for me at all. Chrome 14, Windows 7, nVidia graphics.