Hi!

By way of introduction: I am a registered user. I am grateful that I stumbled on your site when I was going through a period not long ago where I really wanted to start to understand OR mappers and DB abstraction layers, at least at a high level, as I had decided to learn how to do OO development, and not just BS about it, after being an SQL/VBScript web-enable-the-DB guy in monolithic IT shops (Digital, CPQ, HP) for many years - some other cool things here there too like stints @ two VC backed start-ups, one still going strong http://www.ide.com , where I learned a lot about process and dev teams through pain!

Part of this journey is that I have made the change form the Windows IT Stack to LAMP. I took a very modest position at a small, but filled with talent,  consultancy in Cambridge MA http://www.isovera.com , that is entirely focused on app dev using Open Source tools & platforms specifically for non-profits. I am being allowed to work on becoming a competent OOD  and LAMP-skilled person, and until then, they throw all the windows/SQL Server stuff at me and no one seems to complain.

My Question: I want to become a competent developer with OO data tiers & abstraction layers and OO frameworks, and to be able to recognize what make one OR Mapper implementation / or DB abstraction layer superior to another. I understand this is a long-term process. I also understand and have decided that this will require a non-billable project that will command a long-term committment.

I would like to know if you have plans to "port" your work to the LAMP platform, or make it "interoperable" in some way, and/or if you would give consideration to guiding me in the right direction to do the work that would be required to leverage your ORMapper and your ideas to function in a LAMP environment, the back-end DB can stay SQL Server, I like SQL Server!

I do apologize for the length of this email, but i wanted you to know where iwas coming from with my questons. Regards,

Adam