Thomas Brierley

Hi Frank! I too am interested to see "double dweets" discussed again, and am glad you're the person to resurface it. I have quite a few thoughts on this, so...

> The exact details on how to count is a separate, but important, discussion. I lean in favor of something that is relatively easy to understand in most circumstances when...

Ah i see! So the change could achieve multiple things... we get more characters to play with, the existing uncode packed dweets can be made more accessible by simply replacing...

> Like for example my way of drawing bitmaps on dwitter will no longer work as it uses a similar unicode trick. So, we'd need to find a new way...

I was hoping we wouldn't go too far down this road, it's inevitable as soon as we start to discuss it everyone will have their favourite builtin they want a...

> the unicode compression techniques are no longer viable. this includes the image packing system that I have used. that is a good thing! for example the Mona Dweetsa is...

> I don't think web workers will be fruitful because they are not intended for real time graphics applications. So the video will not be smooth as if using requestAnimationFrame....

> my concern is running at a smooth 60 fps if the dweet runs fast enough to allow it. The only way I've found to run smooth animation in javascript...

I believe this limitation is from the [isPlainObject](//github.com/josdejong/mathjs/blob/8c2f10a8651ed363c37f886ec8e54493c72f7924/lib/utils/customs.js#L134) check, which is currently required for both getting and setting any properties. (class/constructor Instances are not plain objects but `{}` or `Object.create()`ed...

Accessing inherited properties is currently allowed on plain objects, I think it would be a shame to lose that but I'm a bit biased because that is the use case...