by - We’ve decided to move all RDBMS development to MySQL. MS Sequel Server was a close second, but since Oracle bought up all the MySQL storage engines of consequence, what could go wrong?!?!
- We’ll be moving all first generation OpenSRF applications to Python, because, well, I was wrong. Whitespace is syntax.
- Also, no more JSON. We’re going RDF all the way, baby!
- I’ve seen the error of my ways with SuperCat. Instead of trying to supply a secure, abstracted, simple interface to the catalog I will simply put a thin XML wrapper on top of the new MySQL database. Sure, there will be security issues if anyone figures out the names of tables containing user data, but how can they know that if I don’t document them. Problem solved!
Ok .. I didn’t even try to make it believable. I was going for a “it’s so crazy it might just work” angle. Eh, eh?
UPDATE: As noticed by Ross, we failed to address the Library 2.0 functionality. To that end we’ll be replacing all subject authority data with user supplied tags. You’ll do our cataloging for us via a Z39.50 interface. What’s more Library 2.0 than that, I ask you!
Hey, you had me at MySQL. 🙂
— Jason
I better start writing version 1 of the in-house RDF parser so that version 3 will be ready by Beta!
Sweet! I can then start using the RDF-powered XUL templates. I hear the error handling for those are the best-est.
— Jason
Why are you wasting your time with all this?
You need to just add some Library 2.0 and Evergreen will be accepted and embraced by all.
Where’s your Library 2.0?!