the eternal question
do I hate #icedrs enough to fork it
there are a number of really good design decisions in there (like letting the widget tree borrow from the application struct and making the widget trait generic over the renderer so widgets can depend on renderer-specific features if needed) and a number of REALLY bad ones (the application trait no longer being public as of 0.14, so even if you're advanced enough to be able to understand and use it you can't; methods of the widget trait being more or less completely undocumented; the inexcusable amount of string copying that goes on with every single keystroke in a TextEntry; and the big one, a bunch of different traits in different modules that have the same names, making rustdoc output confusing at best and making imports hellish to organize).
Oh, and ice cold take, Elm architecture sucks to implement.
If the view() method in the app trait took &mut self instead of &self, that alone would open up a ton of possibilities.
Do I care enough to try?





