"The great advantage of using merb now, is that it has a public API so we will be able to easily migrate it to the new 3.0 API."
So, does that mean the team is standing by their commitment to the merb-core public API? I asked some questions in an different thread that were around this issue, and because of the newness of the situation, I got a very vague swath of answers. I am not concerned all about learning a new framework. I know Merb well and don't feel that time is wasted. I also know Rails, and don't feel like I have to learn anything new to go back to using it. I like learning new stuff often, so who knows what is next. What I am concerned about is the libraries and the plugins I was hoping to write from said libraries. Knowing that the public API for merb core will be there would put my mind at ease to keep building these cool things. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
