If anything, this merger will actually bring more stability to the API. Regardless, 1.0's API is frozen for at least a while. The way I see it, an API is an adapter between the framework and its users (developers). Therefore it should be trivial to maintain an API to a framework, and version them... thus if your code conforms to the Merb 1.0 API, then Merb 2.0, 3.0, 4.0 (etc) should have a 1.0 compatible API "plugin" to allow it to still work.
That'd be dandy, no? ;-) Julian. On 07/01/2009, at 1:00 PM, Jim Freeze wrote: > Not sure if this was directed in my direction, but for the record, my > comments about the fast changing landscape are from before the merger > was announced. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
