5 ms·
Preact is fine.. 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..
by jmcdiesel 10y ago
Preact is fine..
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..
- mmastrac 10y agoNot necessarily impractical - what about Electron desktop apps and mobile webview-based ones?
- pascalo 10y agoExactly 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-linux/ http://pascalopitz.github.io/unoffical-sonos-controller-for-...
- developit 10y agogah this makes me want a sonos
- developit 10y agoThat is untrue. There are currently two small test failures in IE on master, hence the graph. The library supports IE9+.
- jmcdiesel 10y agoIts 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...
- developit 10y agoYou should probably look at the test before making firm opinions on the matter. Do you even know what is failing?
- luhn 10y agoMaster is not production. The last release had all tests passing. https://travis-ci.org/developit/preact/builds/180853866 https://travis-ci.org/developit/preact/builds/180853866
- rpeden 10y agoSure 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.
- DEADB17 10y agoThere 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.