4 Matching Annotations
- Last 7 days
Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.
- explicit interfaces
- maintenance burden to explicitly define/enumerate/hard-code possible options (explicit interface)
- run-time dynamicness/generics vs. having to explicitly list/hard-code all options ahead of time
- being explicit
- component/library author can't consider/know ahead of time all of the ways users may want to use it
- maintenance burden
- Jul 2019
Undo/Redo Have you noticed that Undo support on almost all web applications is either nonexistent or terrible? It's hard to implement, but Core Data solves the problem elegantly. An Undo button encourages users to experiment with the application and not be afraid of making mistakes.
- Feb 2019
And the screens are almost horizontal
It took quite a long time to get to more tactile interfaces, yet still, predominantly (as I am using a laptop right now) interfacing more of a vertical interface.
- Sep 2015