Anyhow, personal recent experience on using a plugin that is an API to some webservice:
- Lots of static methods
- Code structure is awful
- Documentation is non-existent
... and I rarely use Rails let alone learn Ruby yet I can see how horrible that plugin is.
I heard I'm not alone when it comes to the discussion of the quality of plugins out there.
I don't mean to bad-mouth Rails framework because it is a well-thought project (let's not discuss the internal code). But as many who have been in this industry for a while, we kind of know that this is coming sooner or later.
Python code, in many places, seem to have a good balance of pragmatism, UNIX culture, and discipline.
Having said that, Rails 3.x seems to mark a change in attitude from the Rails core team. They're starting to address issues and stabilize the framework for the better. Let's hope the rest would clean up as well.
Anyhow, personal recent experience on using a plugin that is an API to some webservice:
- Lots of static methods
- Code structure is awful
- Documentation is non-existent
... and I rarely use Rails let alone learn Ruby yet I can see how horrible that plugin is.
I heard I'm not alone when it comes to the discussion of the quality of plugins out there.
I don't mean to bad-mouth Rails framework because it is a well-thought project (let's not discuss the internal code). But as many who have been in this industry for a while, we kind of know that this is coming sooner or later.
Python code, in many places, seem to have a good balance of pragmatism, UNIX culture, and discipline.
Having said that, Rails 3.x seems to mark a change in attitude from the Rails core team. They're starting to address issues and stabilize the framework for the better. Let's hope the rest would clean up as well.