Drop polyfill idea?

[Turbo87]

Similar to emberjs/ember-ordered-set#14 it looks like Ember.Map has quite a few API differences to the native Map class. As argued in emberjs/ember-ordered-set#14 (comment) it might make sense to restrict this package to just mirror Ember.Map and not try to polyfill the native Map too. In that case we should drop the -polyfill suffix from the project name though.

[Turbo87]

renaming to @ember/map would also satisfy the new import paths (see https://github.com/ember-cli/ember-rfc176-data/#embermap), though it might create problems for @ember/map/with-default 🤷‍♂️

[Turbo87]

Given emberjs/data#5255 and our discussion on Slack I'll close this issue now because we will archive the project again. By the time Ember.js will drop Ember.Map Ember will be at version 3.x, and at that point all target platforms (even IE11) have support for the native Map class, which is a better migration path than using @ember/map-polyfill.