How far to push behavioural compatibility with native?

[David Gerard]

On 8 July 2010 10:32,  <Joerg-Cyril.Hoehle at t-systems.com> wrote:

> What do you think?
> A) Bug compatibility => Behavioural compatibility => drop existing
>   code and try to mimic native's behaviour as closely as possible.
> B) PAUSE and RESUME is a useful extension not present in native, keep it
>   as long as no app is affected by this difference in behaviour.


Bug-for-bug compatibility with an explanatory note somewhere (wiki
page "BrokenByDesign"?) as to why.

Now you have to write a test for it, of course ... "Fail! Your MIDI works!"


- d.