Simon Willison’s Weblog


9 items tagged “joe-gregorio”


CCD. Joe Gregorio on the growingly ubiquitous and disruptive nature of CCDs. If everything has a camera attached to it, what problems can we solve (and what new problems do we introduce)?

# 29th November 2009, 9:08 am / ccd, disruptive, joe-gregorio, sensors

Authority, historically, gets bestowed on the gatekeepers of information, such as Britannica, universities, newspapers, etc. Everything that can be digitized will be digitized, and will then be available over the internet, which is disruptive, not only to business models, but to authority.

Joe Gregorio

# 19th November 2009, 6:53 pm / authority, internet, joe-gregorio, newspapers, wikipedia


Bloom Filter Resources. A continuation of the discussion about how to transfer information about a large number of recently updated resources around in an efficient way, Joe provides working code illustrating a simple approach using bloom filters.

# 19th October 2008, 10:22 pm / bloom-filters, hashing, joe-gregorio, rest

There was a time when you could whip out a parser in lex and yacc, stitch together a naive VM and throw it over the wall and you'd have a new scripting language. Those days are coming to a close and in a few years (if not months) you won't be able get traction with anything unless it does direct threading, is register based, has generational GC, does peephole optimizations, does trace-folding, does type-inferenced inline caching, etc.

Joe Gregorio

# 8th June 2008, 9:36 am / dynamiclanguages, joe-gregorio, scriptinglanguages


The D Language and Server Logs. Neat example of a simple D program for crunching log files.

# 3rd December 2007, 9:02 pm / d, joe-gregorio, logs, programming

RESTify DayTrader. Killer REST case study from Joe Gregorio.

# 21st June 2007, 1:44 pm / daytrader, joe-gregorio, rest

Test stubbing httplib2. Nice demonstration of monkey-patching as part of unit testing in Python.

# 10th May 2007, 11:24 pm / httplib2, joe-gregorio, monkeypatching, python, testing

The upshot is that HTTP does not have everything that REST indicates should be present, and there is the additional problem that while HTTP is the first, and best, implementation of REST, the two are not the same and yet are often confused.

Joe Gregorio

# 17th February 2007, 5 pm / http, joe-gregorio, rest

At some point in the past rolling out an application to 300,000 people was the pinnacle of engineering excellence. Today it means you passed your second round of funding and can move out of your parents garage.

Joe Gregorio

# 1st February 2007, 11 am / joe-gregorio, scaling