That is untrue. There are currently two small test failures in IE on master, hence the graph. The library supports IE9+.
Its true then. A failed test on production code means IE isn't supported. If its allowed to go to production with defects for IE, then IE support can't be claimed...
Master is not production. The last release had all tests passing. https://travis-ci.org/developit/preact/builds/180853866
There are tests to validate IE support. The intent is clearly there. Circumstantially this design decision is not met, but it is clearly a bug not some fundamental lack of support.
Please consider how your feedback might affect the people giving their effort to offer an option to the community.
Sure it can. They can just say something like "IE9+ is supported, but features x and y won't work".
There are plenty of libraries that officially support IE, even when there are problems in a few small cases. They usually just make sure these issues are publicized so people won't be surprised them.
You should probably look at the test before making firm opinions on the matter. Do you even know what is failing?
Not necessarily impractical - what about Electron desktop apps and mobile webview-based ones?
Exactly my use case[1]. Switching from React was trivial, and the performance increase was really noticeable.
[1]http://pascalopitz.github.io/unoffical-sonos-controller-for-...
But... its entirely impractical... it supports NO IE (only edge) ... its easy to make a small, fast lib that doesnt have to handle IE at all..