I've very recently come to the opinion that it would be useful if merb "1.0", meaning a stable API, doesn't happen for a while longer. There have been lots of changes the last months. Things are just, hopefully, getting stable. After this, it can take many months for other developers to try various use cases (figuring out the most straightforward and efficient use of different components). This will lead to feedback on the API. I realize the core developers feel the API is robust and will serve needs well. But making merb "1.0" with an implication that this freezes the API doesn't provide a gestation period for the much large dev community to find the best use cases and provide useful feedback on the API.
I understand the value and anticipation by the lead devs of merb to want to get to 1.0. But I feel there may be additional value in holding back a bit. thanks, Jon On Oct 12, 11:44 pm, "Michael D. Ivey" <[EMAIL PROTECTED]> wrote: > > I see a lot of flexibility in Merb, and I haven't heard anything that > > suggests that is about to change, but I would sleep better knowing > > that Merb isn't about to get "opinionated" in a way that leaves me out > > in the cold. > > Merb will stay very flexible. The ability to take just the pieces of > the framework that you need and toss the rest is a core principle, and > is very unlikely to change. Staying agnostic to ORM choices is a core > principle. Being really fast is a core principle. > > Also, once Merb 1.0 is released, it should stay very stable in terms > of API for a long time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
