130413
I can delete you - for few secs
130319
experimentalrawconversions96hugezoomcrop2.gif
Yes. Super WMATA. DC Metro rail map Super Mario 3 style by Dave Delisle. It’s available for purchase.
Chicago Digital Humanities Plenary Session
Jon Orwant (Google): More Stuff and more things to do with it. A talk with responses by Neil Fraistat (Maryland), and Jeremy York (Michigan)
Brian Tingle’s notes from Jon’s talk [google doc reader] [publish to the web version]
Two stacks
Computation Stack
Computation |
Query |
Data |
Semantic Stack
ideas |
facts, sentences, quotations |
parts of speech |
structure |
letters, punctuation, symbols |
text, pictures |
pages |
Move computing to the data (too much data to move to each researcher)
ex post facto criteria for google DH grants
Is it feasible?
Is it worthwhile?
Can we provide needed assess?
Does it enable other researchers?
Does it illustrate a new style?
Move up a level in a stack.
Improve level in a stack (reuse-able data set)
Or reasonable using one level as a proxy for a higher level (i.e. structure as a proxy for ideas)
Moving up a level by creating tools (intralanguage translations {early english to modern english})
—
during the comments from the others this was all I wrote down
corpra space design in bamboo
Asaf Hanuka: “Google Monster”
Drawn to scale.
[superpunch.]
The Wall Street Journal added some crucial context to discussion of the revised Google Book Search Settlement announced late Friday: it “would cut the number of works covered by the settlement by at least half by removing millions of foreign works.” (Only works from the United States, the United Kingdom, Australia, and Canada would be included.)
Librarian and consultant Karen Coyle commented, “This greatly changes the value of the institutional subscription for higher education, as well as the value of the ‘research corpus’ (essentially a database of the OCR’d texts that researchers can use for computational research)… As it is, too many Americans are unaware of the world outside of those Anglo-American borders. This will just exacerbate that problem.”
Seen at Library Journal
Mike started the talk by giving the developers a good laugh: it seems that Google manages its kernel code with Perforce. He apologized for that. There is a single tree that all developers commit to. About every 17 months, Google rebases its work to a current mainline release; what follows is a long struggle to make everything work again. Once that’s done, internal “feature” releases happen about every six months.
Seen at LWN.net
Notable comment:
Posted Oct 21, 2009 5:19 UTC (Wed) by bradfitz (subscriber, #4378)
if you’re going to have a blessed “central” repo anyway, who really cares if that repo is actually git, svn, perforce, etc, as long as you can use your DVCS of choice at the edge?
The alternative is changing years of accumulated tools & checks every time a new VCS comes out and you change your master repo’s storage format.
*shrug*
Google is open sourcing a collection of Javascript tools today that will enable developers to build faster, more powerful and more efficient web applications using some of the same code that…