355 karma · joined February 28, 2007
Do you have any links to more detailed discussions of this theory?
I haven't heard of any limitations on using custom domains for commercial use, cf. http://groups.google.com/group/google-appengine/browse_threa...
Quoting from page 2 of their 2008 catalogue (http://www.naxos.com/SharedFiles/pdf/NaxosCat2008May.pdf):
More than half of all current Naxos recordings are
included in various editions of the authoritative Penguin
Guide.
Several Naxos recordings have been distinguished with a Rosette or "Key Recording" accolade by the Penguin Guide: http://www.naxos.com/feature/Penguin_Guide_Top.aspThe Folio Fit-to-width functionality (only available in landscape mode) is already able to detect and automatically crop white margins at the top and at the bottom of pages, so why not create a mode that automatically crops all 4 margins in portrait mode?
Another much needed feature is text highlights and text notes. Since Folio already has the ability to select text, it should be no big deal to add this to the app. Make the highlights and notes syncable a-la Kindle, and I'm sold.
One minor nitpick: Most apps seem to place their Back/Up button in the upper left corner. The Folio "Library" button should be on the left and the search button on the right.
These are the books that taught me that Chinese writing is more usable and more adapted to the particular needs of the Chinese language than we in the West tend to believe. In particular, the phonetic element in Chinese characters is much more important than I imagined.
Also, while it is true that the road to fluent reading is much longer for the Chinese than for readers of phonemic scripts, this is partly compensated by the higher reading efficiency of fluent Chinese readers.
One way to look at Chinese writing is to see it as a highly defective phonemic writing system with semantic annotations. In other words, Chinese characters constitute a morphophonemic writing system, much like English (for/four/fore) but with a much stronger emphasis on the morphemic aspect.
1. Django Templates correspond to Rails Views (they both define how data is presented to the client). The biggest difference is that it's easier to include business logic in Rails Views because the Erb template language is as expressive as Ruby itself, while the Django template language is deliberately restrictive.
2. Django Views correspond to Rails Controllers (they both process requests). The biggest difference is that data is passed explicitely from a Django View to its Template, while data is passed implicitely from a Rails Controller to its View.
Douglas Hofstadter's "Gödel, Escher and Bach: An Eternal Golden Braid".
Jared Diamond's "Guns, Germs and Steel: The Fates of Human Societies".
I don't bother teaching coworkers that much about command-line git now, I just point them to GitX, which suffises for 90% of their interactions with git.
One simple thing I'd like to have is the ability to just click a button and pull or push from a remote branch.
Done by professional comedians once in a while it's fun. Done by an entire nation it's disgusting.
Compared to Carr's, Michael Arrington's article on Le Web seemed like a balanced critique, and that's saying something.
This victimization technique should added to the list of Logical Fallacies, if it isn't already there.
box.recall(Comic, lambda c: 'Hob' in c.Title or '#' in c.Title)
Instead of for instance Django's
Comic.objects.filter(Title__contains='Hob') | Comic.objects.filter(Title__contains='#')
I also loved the approach to converting the python queries to SQL code: Dejavu converts the python queries into an AST, which is then deparsed into the desired SQL dialect, an approach that apparently was used long ago by Glorp, a Smalltalk ORM.
Dejavu can also work with non-relational backends, such as flatfiles, LDAP stores, memcache, RAM and even the Python shelve.
In the question round, Robert also showed a very simple syntax for joins:
Table1 & Table2 represents an inner join. Table1 | Table2 represents an outer join. Table1 << Table2 represents a left join.
One question that was left unanswered was whether Dejavu supports the distributed key-value stores that are becoming increasingly popular, such as CouchDB, Amazon S3 and Amazon SimpleDB.
O'Reilly's Programming Python is not bad, but it's not a great book, either for beginners or journeymen.
Python in a Nutshell is more suitable as reference book, although I suppose you could use it to learn Python. For a Python reference book, I found David Beazley's Python Essential Reference to be more informative and better organized: http://www.amazon.com/Python-Essential-Reference-Developers-...
As other people have mentioned, Guido's online tutorial is pretty good, and you don't really much else to start programming in Python: http://docs.python.org/tutorial/index.html
I'm always puzzled by people recommending Mark Pilgrim's Dive into Python. I don't find it a good choice for Python beginners.