Comment Re:He is wrong about databases... (Score 1) 150
He IS wrong about databases. "Flat files" are "flat wrong" for an Application Service Provider model. I don't care that FreeBSD doesn't lose your files -- if they're in a half-correct state, your customer is not going to have the experience you want them to have.
We've probably all heard of ACID a million times. Atomic, Consistent, Isolated, Durable. You can do a lot with flat files. Storing them individually, you can isolate errors to one customer's experience. But, you cannot ensure that if your programmer is out for the week and the janitor trips over the power cord, your clients are going to be OK.
He's also wrong about continuation passing. It would be a fantastic model if browsers didn't have a BACK button. LISP has side effects, it's not purely functional. A user cannot rewind a transaction correctly using the back button in many cases, if the transaction is kept in the server as a "hot" continuation. You are by nature storing state at the server at that point.
The REST model is the technically correct model for the web -- if you want to sugar it into looking like continuations, you can in LISP. But, unless your LISP has serializeable continuations, and you keep each version from a transation on the server or try to cram them into a 4K GET string, you're S.O.L. doing it natively.
We've probably all heard of ACID a million times. Atomic, Consistent, Isolated, Durable. You can do a lot with flat files. Storing them individually, you can isolate errors to one customer's experience. But, you cannot ensure that if your programmer is out for the week and the janitor trips over the power cord, your clients are going to be OK.
He's also wrong about continuation passing. It would be a fantastic model if browsers didn't have a BACK button. LISP has side effects, it's not purely functional. A user cannot rewind a transaction correctly using the back button in many cases, if the transaction is kept in the server as a "hot" continuation. You are by nature storing state at the server at that point.
The REST model is the technically correct model for the web -- if you want to sugar it into looking like continuations, you can in LISP. But, unless your LISP has serializeable continuations, and you keep each version from a transation on the server or try to cram them into a 4K GET string, you're S.O.L. doing it natively.
