The State of the RubyAMF State of the Union
I've been slowly considering the use of RubyAMF in a couple of new Rails projects. By "slowly" I mean that there have been some more pressing projects that have prevented me from really "diving in" and experimenting with RubyAMF; only leaving enough time to read some docs and follow the Google Group.
Consider my previously stated credentials when I say that RubyAMF looks great. Given the following recent events it appears that the project has a lot of momentum:
- Restful Rails integration by use of the respond_to block
- Mixbook's adoption (especially the Aaron & Aryk collaboration that led to huge performance gains)
- Peter Armstrong, the author of Flexible Rails has adopted, contributed to, and promoted RubyAMF over WebOrb
- Creation of new Rails generators
- and more I'm not aware of...
The latest RubyAMF blog posting, RubyAMF State of the Union (doubly posted on the Google Group) is basically a well-structured "rally the troops" announcement to the community. The project founder, Aaron, is moving on to some new projects leaving it to the community to keep up the momentum. I'm happy for him. I can't imagine how time consuming the almost-sole development of RubyAMF has been. This is the real test. How will the project fair on the shoulders of the community?
(Remember: I'm not in the know on the project, I'm seeking your thoughts and opinions, and for good times I'll pull out the good ole' "Jump To Conclusions Mat.")
It's too early to tell for sure, but from my point of view I'm a little disappointed (imagine me hypocritically pointing) with the lack of any community responses to either the blog post or the Google Group post. I say, "my point of view" because I'm hoping that there have been responses and things working that I'm unaware of.
One week ago RubyAMF had good momentum with a promising future. Is that still true today? Is it a bad time to start using RubyAMF?
RubyAMF…is that like bowling for jewelry?
@Shane - go stand in the corner.
@Luke RubyAMF works, that’s the thing. We need help from the community to make it work a little cleaner, but Mixbook is already using it in a production app, I’m using it in a production app (the development branch - don’t tell anyone) so it’s really close to being there.
i think rubyAMF came to the party way early. Flex is just now beginning to gain momentum, and rubyAMF gives the growing ruby community an option. BlazeDS will replace Granite, and php already has openAMF. Aaron will be amazed at how popular rubyAMF is at this time next year (maybe it will summon him back). rubyAMF may take a while to find its development community, but I think it has a bright future.