3 ms·
Years ago I got into an argument about these sorts of "beautiful" and "intuitive" APIs: http://www.reddit.com/r/programming/comments/21pnl/just_say_no_to_ruby_
by ubernostrum 13y ago
Years ago I got into an argument about these sorts of "beautiful" and "intuitive" APIs:
http://www.reddit.com/r/programming/comments/21pnl/just_say_no_to_ruby_on_rails/c21rwo http://www.reddit.com/r/programming/comments/21pnl/just_say_...
I still do not have good answers to the questions I asked in that first comment.
- mpartel 13y agoOne possible answer: static typing + autocompletion. Autocompletion clearly show what you can and can't chain, but admittedly it helps a little less when the DSL asks for a parameter of some type and you don't know how to start building one. Perhaps one way to evaluate the learning curve of an API is to count how many non-standard types appear in the signatures of its methods, excluding the `this` parameter.