A few months ago, we announced the creation of a “forum” to discuss the future of Rails and what the community is interested in. Since then, many important suggestions/topics were addressed, many features were completed or started.
My goal in this post is to give you a quick overview on the status of the uservoice forum.
##Suggestions mentioned and completed:
Nested Model forms
This is something that was actually started before we put the forum together and this feature is now available since Rails 2.3.x
Olimpiu Metiu already released two issues of his Rails Magazine. The PDF versions are available for free but you can also purchase the print version.
A lot of people have put efforts in building the new wiki and I’m sure a lot more content will be provided. We have also made the wiki available for translation.
This is something that already started in the Rails3 branch, go check the work done by Josh, Yehuda, Carl and others to make Rails perform even better.
Public and plugin API
This is something that’s particularly important for 3rd party developers and therefore plugin users. There is still a lot of work to be done with 3rd party developers and “advanced users” before we can get a fixed API. However, once we will have this API, Rails updates and plugin compatibility should be much smoother.
Rails 2.3 came with the ability to have engines in your plugins and if you were at RailsConf, you might have attended Yehuda and Carl’s talk on mountable apps. Thanks to some work done on the router and Action Controller, you should be able to mount a Rails app inside another one sometime in the future.
Easier to read code
The refactoring has already started and the internal code should be cleaner and easier to read. Remember that Rails is 5 years old, such a task isn’t easy.
Better support for non relational databases
Thanks to Action ORM and some more refactoring, non RDBMS and other data stores will be better supported.
Unbind Test::Unit and Prototype
Agnosticism is a big theme in Rails 3. Even though, Test::Unit and prototype will be the default, Rails won’t make any assumptions about users using one framework or the other. Watch David’s keynote at RailsConf for more information.
Make Action Mailer consistent with regular controllers
This task was started as part of the work done on Abstract Controller.
Don’t forget that you can still make your suggestions and/or pick one that is already listed and start working on it!