Thanks Shaloo, excited to see content! I should have some time late tonight to look at the array computing content. I think we should aim also to make that a little more concrete about what the Python landscape looks like.

Thanks @rgommers for the inputs. Does this version look okay? Its easy to cut down content for first two paragraphs - if you think so.

In the array computing page, I plan to add array computing landscape diagram - similar to your deck but a bit more organised around timeline.

In the array computing page, I plan to add array computing landscape diagram - similar to your deck but a bit more organised around timeline.

That sounds great. I think my diagram has all the needed elements, but I wasn't too happy with how it looked - I'm sure you'll be able to make the visuals and clarity much better.

Here is how the latest array landscape looks like...

A few small changes to make, then I'd like to merge this to keep things moving and avoid further merge conflicts. I'd like to help tweak the language on the array computing page a little, but that can be done later - this is a nice first cut.

Also, can you break the lines so they're about 80-100 characters long? That makes it easier to review and read.

Ralf, did you mean line in html sources restricted to 80/100 chars? Done in array computing page src.

Ralf, did you mean line in html sources restricted to 80/100 chars?

Yes, I meant any content, html would be quite useful too. If long paragraphs with links are on a single line, then they're very hard to read in the GitHub interface (in an editor you can at least turn on Word Wrap, but diffs will still be tricky).

Merged, thanks @shaloo!