Myself and EMW have a site called Rocket Propelled Badger for film reviews.
Its based on Ruby on Rails scripts running from a SQL backend, pretty standard. Matt wrote it a fair while ago, and its been running fine since then.
Our hosting provider has just updated to Ruby on Rails V 2.0.2. This broke our site. Firstly there are some mods you have to make to get an older app running on the new environment. That I don't have a problem with.
What I do have a problem with is that the original RoR offered a "Pagination" method. This automatically split the results of your queries into pages, and damn useful it was too. We used it in a fair few pages.
Pagination is apparently depreciated because it is not the fastest way of achieving these results. However, not only is it depreciated, it has been removed and there are no methods in the stock toolset that can be easily used to achieve the same.
The solution they give?
"Of course, if youâ€™re using, say, pagination, youâ€™ll need to install the classic_pagination plugin"
OK, fine. How do we do that? Well, we can't. It requires terminal access to the server. We can pester 34sp to do it, and to be fair they probably would in realtively short order. What if we didn't have a provider who gives very good support?
Basically we'd either have to turn off pagination or write our own methods.
In my opinion, that is bollocks. I have (politely) told them so.