Hi Merb, SDRuby and Orlando Ruby mailing lists,

I just posted an article covering the Merb
1.0<http://merbist.com/2008/11/09/merb-1-0-released/>release
http://digg.com/programming/Merb_1_0_released_and_approved_by_Matz_Ruby_creator

I'm sorry it took so long to put together, but after 1.0 was released I
spent a lot of time with Yehuda, VM implementors and other lib authors.
RubyConf was awesome and offered me a great opportunity to network.

The Orlando Ruby community was really welcoming and I'm glad Orlando and
Merb will be forever connected via this release.

RubyConf also gave me the opportunity to spend some time with Matz and to
discuss his view on Merb and to talk about some implementation details. It
was great to see Yehuda and Matz talking about the Ruby collector, forking
processes, Ruby 1.9 schedule etc... But don't worry if you missed the
discussion I'll blog about in few days.

Anyway, here is the quote from my interview with Matz:

"Everyone outside of the Ruby community understands that we only have 1 web
application framework, named Rails, but it's not true in any sense. We have
several post-Rails frameworks, which is very good, and I believe in
diversity.

Merb has a bright future for the people who are not satisfied by the fixed
ways in Rails.  I think that that Merb will give users more freedom in a
Ruby-ish way of programming.

I'm not really a web-guy, so i don't judge any of them [frameworks], but
Rails does some kind of drastic change on the language itself like in Active
Support.  But Ruby has its own culture and technological atmosphere in the
language so that keeping that makes me feel easier."


Check out the blog post and maybe even Digg it:
http://digg.com/programming/Merb_1_0_released_and_approved_by_Matz_Ruby_creator
or give it a +1 on reddit: http://www.reddit.com/goto?id=7cecf to share the
Merb love ;)

-Matt

--~--~---------~--~----~------------~-------~--~----~
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
-~----------~----~----~----~------~----~------~--~---

Reply via email to