Rant over, let's have a look at our options. Documentation helps, but there are times when I could not figure out what they expected without reading the source code. Then you look at a python package - what style did this wally use? functional, classes or a - oh, good grief. Everything was a class and everything required the implementation of an interface. Take for example the ease of learning Java. At other times a bunch of functions will do just fine.
ALL THE WAY HOW TO
An elegant class hierarchy can often ease the pain of how to navigate the graph of code before you. Some I know would not allow the overhead of classes - that’s all inheritance and unnecessary complexity. The first editorial decision is often a matter of habit. But let us step back and discuss the editorial decision you make as you design an API. Then greenlets will solve all your problems. Unless, of course, you decide to use the ORM. Now it will be async all the way down to the last turtle. The work they have done is spectacular.įor years I have been using SqlAlchemy with Tornado and have had to resort to a ThreadPoolExecutor to make my queries run in parallel.
ALL THE WAY SERIES
Like the old woman in the story who described the world as resting on a rock, and then explained that rock to be supported by another rock, and finally when pushed with questions said it was "rocks all the way down," he who believes this to be a radically moral universe must hold the moral order to rest either on an absolute and ultimate should or on a series of shoulds "all the way down.".