Add Dart's interop story to the documentation

[MaryaBelanger]

This issue is so I remember I want to do this, but it's not tied to any release or development work.

@sigmundch described Dart's interop story in a meeting the other day, and I think it would be nice to have a little paragraph or two about it somewhere adjacent to all the interop docs.

The progression of Dart's interop history and the goals it's moving towards are interesting in their own right, but I especially liked how it's also kind of a microcosm of the whole Dart story, i.e. that Dart started with a very specific use case in mind, but we're constantly widening that scope, becoming more applicable to more developers, and always evolving to be as sustainable and well-rounded as possible.

I don't have an idea about exactly what I want to say yet, but these are some notes:

• Dart started as a web language, for use directly in the browser
• Dart is always used "inside" something, called the embedder
• So, emphasis has always been on exposing things from the underlying system
• Examples, like...
  • running in the vm, the embedder is the vm that has access to the local machine,
  • libraries like dart:io give access to the file system,
  • dart:html for access to the browser, etc.
• APIs to access embedder stuff is the focal point
• As we evolved as a system, e.g. incorporating Flutter and now Wasm, we're generalizing the idea that Dart has a core that's independent of where it's embedded
• We're trying to make it easier to access what's there (wherever Dart is embedded), without us having to own every single API
• E.g. ffi came along with goals like: instead of having to write our own network layer as a Dart library, why not just grab a C++ library that does networking, and expose it to Dart using ffi
• And maybe someday dart:html will go away because of a similar interop development
• It's happening with Javascript now, we want to decouple it, but found that the capabilities weren't strong enough, (hence static interop developments)

I like the idea making a top-level interop page, where we can introduce Dart+interop generally, that umbrellas all the existing, more specific interop content. For example, in the left nav, if "Interoperability" was an actual page and not just a nav heading.

(Where it goes and the "umbrella topic page" concept will make more sense with the upcoming site restructure)

---

Linking to #5439

[parlough]

@MaryaBelanger Do you mind if we reposition this issue as a subtask or follow-up of #5439?

That way this issue can be more about the story and historical aspects, which don't necessarily have to be part of the initial version of the new overview page?

Note I love this idea and your discussion of it above!

[MaryaBelanger]

@parlough Yeah definitely, thanks for figuring out how this fits in!