It would be difficult at best to do these things in racket/gui (to the extent that cocoa/win32/gtk aren't doing them themselves, e.g. diffs between renders I gu

It would be difficult at best to do these things in racket/gui (to the extent that cocoa/win32/gtk aren't doing them themselves, e.g. diffs between renders I guess?), it certainly does have many shortcomings. racket/gui seems primarily designed to accommodate the needs of Dr Racket, and starts to come up short the further you stray from anything Dr Racket does. I think a big part of this comes down to a lack of manpower, which certainly isn't true of Android. However I think it should be possible to design interfaces that make simple things simple while still giving you the flexibility to do complicated things. I think neither Android nor racket/gui has accomplished this, but at least racket/gui is fun rather than tedious. I agree with the article that there's a lack of user-centered design in the Android scene.