memory hierarchy for myself
2004-01-30
orkut is mmorpg
the dotcom lives on
2004-01-28
improper coincidence
Minister: There is nothing improper about coincidence, is there, Bernard?
Bernard: How can a coincidence be improper, Minister? Impropriety postulates intention, which coincidence precludes.
At least back then officials worried about appearance of impropriety, if not impropriety itself....
2004-01-25
2004-01-22
del.icio.us
Why didn't I inline it in the side bar? Because cross-site scripting is not allowed. I could use a third party rss display tool to render rss but it's somewhat cumbersome. Iframe would've worked except for resetting target and inheriting CSS.
2004-01-17
Albania saves me from consumerism
2004-01-16
Salam Pax on Nightline
2004-01-14
turtles all the way down
* Microsoft Virtual PC running Windows XP on top of Mac OS X
* Nokia device emulator on top of WinXP
* Nokia J2ME/MIDP virtual machine on top of Nokia device emulator
* J2ME applications running inside the MIDP VM
[via Erik]
2004-01-11
client vs server side XPath
2004-01-08
what's the difference between a geek, a nerd and a dork?
2004-01-06
hubris and nemesis
2004-01-05
2004-01-04
this year will be better!
Pichinson, a self-described "doctor of reality" who helps liquidate companies, says he wouldn't have moved from Los Angeles to Palo Alto a few months ago had he not smelled more high-tech trouble looming.
"Sadly, it looks like 2004 is going to be another busy year for me," Pichinson said. "There's still another 6,500 to 7,500 companies out there who are among the walking dead."
database as coordination mechanism
The plain truth is, not that many projects really need complex distribution mechanisms. Most apps look a lot like this:
- Read data from a store (db, files, etc)
- Modify data
- Dump data back to the store
I think we have gotten too far away from this wisdom. The typical database has distribution and coordination built in. That means for the most part you get to write your application in isolation. The database also to serves to coordinate the application's own actions.
We need to get back to the future and look at how to simplify coordination and not just message passing. Databases are a coordination mechanism for one or more applications, and one mechanism is better than two.
We know that databases provide concurrency control and transaction management. These features let applications share data -- you can call this coordination at low level. But what about coordination at high level? How can they exchange semantics of data? e.g. "9999-12-31 in date field means now? never? forever in the future?" or "20 point means 20 basis point." (Schemas and constraints can check syntax of data but not the "validity" of data.) Because I don't see how databases provide meaningful (hence ad-hoc) coordination, I don't quite understand Patrick's last sentence above especially the second half.
