Google Maps Javascript API vs Google Maps Embed API

Well, I found this, but only after stumbling on it. And it still only lists a basic concept of the differences between them. It's helpful-ish, but not really what I would have expected Google to have in their system. So it's a kinda answer.

Basically, the difference is: programming, or not programming:

• Customize a JavaScript API map by writing JavaScript.

• Customize an Embed API map by changing URL parameters.

To quote Google from the FAQ section:

What are the Google Maps APIs?

The Google Maps APIs give developers several ways of embedding Google Maps into web pages, and allows for either simple use or extensive customization. There are now several API offerings:

• Google Maps Javascript API
• Google Static Maps API
• Google Maps Embed API

Depending on your needs, you may find yourself using one or a combination of these APIs.

The API Picker also helps distinguish the JS API and the Embed API at a glance. (Note that the Embed API is not the same as the Static Maps API.)

Update

Go with the Javascript API I think it'll suit your needs, from what I can tell the various APIs are all kinda part of the same thing with slightly different functionality

In a Nutshell: assuming you're using the APIs for webpage design as apposed to some web enabled phone app or something

• Static API returns an image object and can be used in a <img src="..."> tag (my guess is safari compatibility?)
• Embedded API is basically taking a map search that you did on the google site and posting it on your own site within an <iframe src="..."></iframe> tag
• Javascript API gives you a whole JavaScript map object to work with if you want to custom code some of your own controls and/or zoom-clicky event goodness

however for the life of me I still cannot find where/how to make the JS API look'n'feel match the Embedded API