Object.assign and browser support: IE11 y/n?

@Alber70g claimed to have used Hyperapp with IE9 without no changes, but I presume he was just lucky. 😄🎉

I am using it with IE11 in production, which is closer to what we really support, although we claim IE10. See also: https://github.com/hyperapp/hyperapp/issues/466

If we drop IE11, we could get rid of the stand-in merge/assign function as well as (potentially) introduce some ES6isms.

function assign(target, source) {
  var result = {}

  for (var i in target) result[i] = target[i]
  for (var i in source) result[i] = source[i]

  return result
}

What do you think?

[SkaterDad]

IE11 is my only supported browser at work for internal apps, so I’d prefer to keep it also. I’m sure I’m not alone.

The fact that I can just drop hyperapp in a script tag and get right to work without polyfills is great.

Edit: I could probably live with needing an Object.assign polyfill, but it will present a potential stumbling block for new folks. Maybe keep the IE11 compatibility for V1 and drop it in v2? Vue is planning on doing something similar for v3, I believe.

[whaaaley]

Personally, I’d like to keep IE11 for now. I don’t care about IE10.