As a guy who does (mainframe) Performance for a living I'd say that if a language is scripting some underlying capabilities you have to think about two things:

• The capabilities' being scripted speeds. For example Java's JNI usually is doing native stuff that might not be possible to speed up.
• The scripting language and code. So, Javascript in most browsers now has good JIT compilation etc. I've not heard of much effort to speed up Python other than PyPy. (I'd love links to discussions on how Python can be sped up.)

But then there's the algorithm. If you wrote bad code (and what is bad code might be environment-specific) you get what you deserve. :-)

@omz really 2 ll's in "gmaill" ?

Could you colour flood fill from the outside and then test pixels? You might need to eliminate e.g. the compass in your example. Though I doubt it adds much to the inaccuracy.

Another approach - one used to estimate Pi - is to generate random points and see if they're inside or outside the building.

The proportion that are to those that aren't can be used with the overall scene's area.

Excellent news! Looking forward to it.

Well I'm using Pythonista on my iPad running an HTTP Server script to serve HTML (also edited in Pythonista) as (localhost) to Safari running in iOS 9 Slide Over mode.

This is functioning as (a basic but) nice sidebar for augmenting text. For example wrapping text in quotes, composing Markdown links from text+URL.

It's basic now; It might not be so basic later on.

Not sure if this counts as the 1 iOS 9 element is I'm targeting Slide Over (which IS new in 9). And I'm doing it from Pythonista.

tvOS is supposed to be based on iOS, not OS X. So I would be more optimistic than some.

If Pythonista or Editorial COULD run on the new Apple TV I could see myself rushing out to buy one. Now how much can I get onscreen on my 65" 4K 3D Sony TV? :-)

Like I say, Workflow put in a Today widget. Might not be desperately useful on an iPhone but being able to launch from all the usual places puts Editorial and Pythonista on an even footing with other orchestrators / launchers.

Not to have one might be "not taking a step forwards when everyone else has".

Which dialect of Markdown is that from? I don’t believe “standard” Markdown has that in. What I use (and in my code process, but that’s a different story) using the <ins> HTML tag. (You can embed HTML in Markdown - for most Markdown processors.)

Typo “ctyles” of any consequence here?

Something for y'all to pick the bits out of...

A reply from @WorkflowHQ on Twitter contained the following...

"Also regarding sending images, Workflow can decode base64 encoded images."

Does this help us here? Can we encode images base64?

All this talk about iCloud illustrates one of the reasons why I'm not looking for a "write to file" solution.

Clipboard would be fine, though "trashing" the clipboard should only be done if necessary. It seems that it is.

To reveal a little more of the picture...

... My idea was to create a graphing Pythonista capability so Workflow might pass a CSV (file) into Pythonista and then do something with the graph (image) returned.

In essence I wanted to add graphing to Workflow. I would expect Pythonista would be a good way to do it.

Would Editorial do this better than Pythonista?

Thanks to all.

Workflow can have an image passed in to a "stage" in its pipeline. And I think it can have a stage output one.

While OK on the clipboard or persistent file front I wondered if the Pythonista stage could ingest and emit images directly.

Those of you who use Workflow know it can handle images.

Any idea how a Pythonista "stage" in the pipeline might pass an image back?

I've not tried it but 1Writer claims javascript support. Some people might like that: http://1writerapp.com/docs/js

Playing Devil's Advocate: What would this bring over existing IDE's on Mac?

Thanks to everybody for your responses so far.

I like the dictionary idea and @ccc had a particularly good thought in terms of stages being in a file, perhaps new line separated.

@ccc I'll be in touch with you during the week as you emailed me. For those who don't know, we both work for IBM - which has a positive stance on Open Source but some governance around it.