Now that the Rails 3 beta is here, let's take a little straw poll.
现在Rails 3测试版就在这里,让我们进行一些简短的民意调查。
Please tell us briefly what your application does and when you will upgrade it to Rails 3. Or, if you're not planning on upgrading any time soon, tell us what's stopping you.
请简要告诉我们您的应用程序的功能以及何时将其升级到Rails 3.或者,如果您不打算在不久的任何时候进行升级,请告诉我们什么阻止了您。
9 个解决方案
#1
3
Honestly? When developers wake up and start work on Rails 3/Ruby 1.9 in their gems and plugins. They know it's been coming for several months now, and most haven't even bothered to upgrade. One in particular that I'd like to point out is authlogic, one of the most used authentication plugins out there. It still doesn't work for Rails 3.
说实话?当开发人员醒来并开始在他们的宝石和插件中使用Rails 3 / Ruby 1.9时。他们知道现在已经有几个月了,而且大多数人甚至都不愿意升级。我要指出的一个特别是authlogic,这是最常用的身份验证插件之一。它仍然不适用于Rails 3。
Whoops!
#2
2
I'm not planning to. I'm sure I'm in a very small minority, but my big application is still running 1.2.6. Each time I consider making the effort to upgrade it seems Rails changes again.
我不打算。我确信我的人数很少,但我的大应用程序仍在运行1.2.6。每次我考虑努力升级它似乎Rails再次改变。
It does what I want it to do, makes good money, and despite feeling more and more left out in the cold I just don't have a sufficiently compelling reason to update it.
它做了我想要它做的事情,赚了不少钱,尽管感觉越来越多地被冷落,我只是没有足够令人信服的理由来更新它。
#3
2
All my Rails apps are currently running under Rails 2.3.5 and every app has a LOC of 80% or greater. This has always been a key requirement for every product I create for myself or I manage at work.
我的所有Rails应用程序目前都在Rails 2.3.5下运行,每个应用程序的LOC都是80%或更高。这一直是我为自己或在工作中管理的每件产品的关键要求。
Usually, upgrading to a minor/bugfix release is just a matter of a few minutes. Change GEM version, upgrade requirements, run tests, fix issues and commit.
通常,升级到次要/错误修复版本只需几分钟。更改GEM版本,升级要求,运行测试,修复问题和提交。
Rails 3.0 is a major rewrite and the biggest problem is represented by plugin compatibility. Plugins are not under my direct control. This is the same reason why I had hard time trying to upgrade to Ruby 1.9.1.
Rails 3.0是一个重要的重写,最大的问题是插件兼容性。插件不在我的直接控制之下。这就是为什么我很难尝试升级到Ruby 1.9.1的原因。
However, I'm already playing with Rails 3. I want to learn the most important changes of Rails 3 as soon as possible in order to start moving the existing apps to the right directions. Moreover, as a plugin author, it's important to me to start working with Rails 3 in order to make my plugins compatible.
但是,我已经在使用Rails 3.我想尽快学习Rails 3最重要的变化,以便开始将现有应用程序移动到正确的方向。此外,作为一个插件作者,我开始使用Rails 3以使我的插件兼容对我很重要。
Yesterday I start with my most simple app. Well, at least this is what I was used to think about it. Anyway, it is the app with the lower number of external dependencies (less than 3 Gems) and it took about 1 hour to upgrade and 3 hour to figure out why Rails was failing to load my routes. It turned out, the Rails Metal component was fighting with the new Rails 3 stack.
昨天我从最简单的应用程序开始。好吧,至少这是我过去常常想到的。无论如何,它是具有较少外部依赖性(少于3个宝石)的应用程序,升级需要大约1小时,并且为了弄清楚为什么Rails无法加载我的路线需要3个小时。事实证明,Rails Metal组件正在与新的Rails 3堆栈作斗争。
There are some minor issues I have to figure out, but I can say I successfully migrated my first app to Rails 3.
我必须弄清楚一些小问题,但我可以说我成功地将我的第一个应用程序迁移到了Rails 3。
I'm planning to migrate all my Rails apps to Rails 3 as soon as possible, once Rails 3 stable will be available. Or at least, as soon as I can figure out whether the dependencies actually work with Rails 3. Fortunately, a project has been started at http://railsplugins.org/ with the intent of listing all compatible/incompatible Rails plugins.
我计划尽快将所有Rails应用程序迁移到Rails 3,一旦Rails 3稳定可用。或者至少,一旦我弄清楚依赖关系是否真的与Rails 3一起工作,幸运的是,一个项目已经在http://railsplugins.org/开始,目的是列出所有兼容/不兼容的Rails插件。
My remote environment is already compatible with Rails 3, I'm using Passenger with Ruby Enterprise Edition (1.8.7). The only blocking issue are plugins.
我的远程环境已经与Rails 3兼容了,我正在使用带有Ruby Enterprise Edition的乘客(1.8.7)。唯一的阻塞问题是插件。
I guess it would take at least one month before having the major part of my Rails app ready for Rails 3 thought I won't probably start the upgrade until Rails 3 stable is out or I really need the new version for some blocking feature (ex. subdomain-based routing).
我想至少需要一个月的时间才能让我的Rails应用程序的主要部分为Rails 3做好准备,以为我不会开始升级,直到Rails 3稳定出局或我真的需要新版本的某些阻止功能(ex 。基于子域的路由)。
#4
2
I'm not going to upgrade any apps to rails 3.
我不会将任何应用程序升级到rails 3。
However, I just decided that all new projects will be rails3 going forward. The lack of plugin support isn't a big issue as I see it as an opportunity to decouple my apps from plugins so that I can swap them in and out as I please later.
但是,我刚刚决定所有新项目都将成为rails3。缺乏插件支持不是一个大问题,因为我认为这是一个将我的应用程序与插件分离的机会,以便我可以随后将它们交换进去。
I also suspect that the big plugins will upgrade very quickly as they won't want to be left in the dust.
我还怀疑大插件会很快升级,因为他们不想被遗忘。
Keep track of plugin status here.
在此处跟踪插件状态。
#5
1
I've been keeping my apps on the edge of 2.3, but since there's a lot of fundamental changes to Rails in 3, I'll probably install the beta, work on converting them over and hope to be ready by the time it's released as stable.
我一直把我的应用程序放在2.3的边缘,但由于Rails在3中有很多根本性的变化,我可能会安装测试版,努力将它们转换过来并希望在它发布时做好准备。稳定。
I'm also glad there's a lot of lead time before RailsConf so I can really get familiar with the new features of Rails 3 and won't feel lost/overwhelmed there.
我很高兴在RailsConf之前有很多准备时间,所以我可以真正熟悉Rails 3的新功能,并且不会感到丢失/不堪重负。
#6
1
I don't think I'll upgrade any of my applications. It would be a large amount of work compared to what I'd gain from it. Also in some cases the plugins/gems I used in my app are not compatible with Rails 3 so upgrading would be impossible or would require to fork the gems... too time consuming.
我不认为我会升级我的任何应用程序。与我从中获得的相比,这将是一项大量的工作。在某些情况下,我在我的应用程序中使用的插件/宝石与Rails 3不兼容,因此升级是不可能的,或者需要分叉宝石......太耗费时间。
If I had to update, I'd probably wait a bit more for all the gems/plugins to be updated to Rails 3. Of course any new application I'll develop will be done using Rails 3.
如果我不得不更新,我可能会等待更多的所有gems /插件更新到Rails 3.当然,我将开发的任何新应用程序将使用Rails 3完成。
#7
0
I'll answer my own question.
我会回答我自己的问题。
I'm not sure how many betas there are going to be for Rails 3, but I'm going to hold off converting my blog application until the next beta or the final release. I think it's going to be quite a time-consuming process because I have a lot of view helpers that build markup, a lot of named scopes and some quite complicated routing.
我不确定Rails 3会有多少测试版本,但是我会暂时将我的博客应用程序转换为下一个测试版或最终版本。我认为这将是一个非常耗时的过程,因为我有很多构建标记的视图助手,很多命名范围和一些非常复杂的路由。
I want to add page caching first before tackling Rails 3!
我想在处理Rails 3之前先添加页面缓存!
#8
0
After trying out the beta and it not wanting to work with any commands, I have decided to wait until a new beta.
在尝试测试版并且不想使用任何命令后,我决定等到新的测试版。
The ticket has already been opened for the issue.
已经为此问题打开了故障单。
#9
0
After realising that I probably spend more time in Zend Framework and Doctrine getting code to work (fixing framework bugs, annoying language workarounds, and just plain pain), than actually coding features I decided that it's finally time to give RoR a go. Especially as RoR3 is now out with a bunch of documentation.
在意识到我可能花更多时间在Zend Framework和Doctrine上运行代码(修复框架错误,烦人的语言解决方案,并且只是简单的痛苦)之后,实际上编码功能我决定最终给RoR一个时间。特别是因为RoR3现在有很多文档。
5 hours through and it's looking really promising. 1 hour of it was debugging though, some documentation on a plugin was not up to speed, but alas I'm there.
5个小时过去了,它看起来很有前途。虽然调试了1个小时,但是插件上的一些文档还没有达到速度,但是我就在那里。
It's interesting, and does seem to be in a better direction. More time to code on features, and less time coding to debug.
这很有趣,似乎确实朝着更好的方向发展。有更多时间对功能进行编码,减少编写调试的时间。
So the app I'm converting is my premium CMS that is deployed in over 20 websites now, and powers my own balupton.com - so will be interesting, as the CMS is already a complete featured cms.
因此,我正在转换的应用程序是我的高级CMS,现在已部署在20多个网站中,并为我自己的balupton.com提供支持 - 所以将会很有趣,因为CMS已经是一个完整的功能cms。
#1
3
Honestly? When developers wake up and start work on Rails 3/Ruby 1.9 in their gems and plugins. They know it's been coming for several months now, and most haven't even bothered to upgrade. One in particular that I'd like to point out is authlogic, one of the most used authentication plugins out there. It still doesn't work for Rails 3.
说实话?当开发人员醒来并开始在他们的宝石和插件中使用Rails 3 / Ruby 1.9时。他们知道现在已经有几个月了,而且大多数人甚至都不愿意升级。我要指出的一个特别是authlogic,这是最常用的身份验证插件之一。它仍然不适用于Rails 3。
Whoops!
#2
2
I'm not planning to. I'm sure I'm in a very small minority, but my big application is still running 1.2.6. Each time I consider making the effort to upgrade it seems Rails changes again.
我不打算。我确信我的人数很少,但我的大应用程序仍在运行1.2.6。每次我考虑努力升级它似乎Rails再次改变。
It does what I want it to do, makes good money, and despite feeling more and more left out in the cold I just don't have a sufficiently compelling reason to update it.
它做了我想要它做的事情,赚了不少钱,尽管感觉越来越多地被冷落,我只是没有足够令人信服的理由来更新它。
#3
2
All my Rails apps are currently running under Rails 2.3.5 and every app has a LOC of 80% or greater. This has always been a key requirement for every product I create for myself or I manage at work.
我的所有Rails应用程序目前都在Rails 2.3.5下运行,每个应用程序的LOC都是80%或更高。这一直是我为自己或在工作中管理的每件产品的关键要求。
Usually, upgrading to a minor/bugfix release is just a matter of a few minutes. Change GEM version, upgrade requirements, run tests, fix issues and commit.
通常,升级到次要/错误修复版本只需几分钟。更改GEM版本,升级要求,运行测试,修复问题和提交。
Rails 3.0 is a major rewrite and the biggest problem is represented by plugin compatibility. Plugins are not under my direct control. This is the same reason why I had hard time trying to upgrade to Ruby 1.9.1.
Rails 3.0是一个重要的重写,最大的问题是插件兼容性。插件不在我的直接控制之下。这就是为什么我很难尝试升级到Ruby 1.9.1的原因。
However, I'm already playing with Rails 3. I want to learn the most important changes of Rails 3 as soon as possible in order to start moving the existing apps to the right directions. Moreover, as a plugin author, it's important to me to start working with Rails 3 in order to make my plugins compatible.
但是,我已经在使用Rails 3.我想尽快学习Rails 3最重要的变化,以便开始将现有应用程序移动到正确的方向。此外,作为一个插件作者,我开始使用Rails 3以使我的插件兼容对我很重要。
Yesterday I start with my most simple app. Well, at least this is what I was used to think about it. Anyway, it is the app with the lower number of external dependencies (less than 3 Gems) and it took about 1 hour to upgrade and 3 hour to figure out why Rails was failing to load my routes. It turned out, the Rails Metal component was fighting with the new Rails 3 stack.
昨天我从最简单的应用程序开始。好吧,至少这是我过去常常想到的。无论如何,它是具有较少外部依赖性(少于3个宝石)的应用程序,升级需要大约1小时,并且为了弄清楚为什么Rails无法加载我的路线需要3个小时。事实证明,Rails Metal组件正在与新的Rails 3堆栈作斗争。
There are some minor issues I have to figure out, but I can say I successfully migrated my first app to Rails 3.
我必须弄清楚一些小问题,但我可以说我成功地将我的第一个应用程序迁移到了Rails 3。
I'm planning to migrate all my Rails apps to Rails 3 as soon as possible, once Rails 3 stable will be available. Or at least, as soon as I can figure out whether the dependencies actually work with Rails 3. Fortunately, a project has been started at http://railsplugins.org/ with the intent of listing all compatible/incompatible Rails plugins.
我计划尽快将所有Rails应用程序迁移到Rails 3,一旦Rails 3稳定可用。或者至少,一旦我弄清楚依赖关系是否真的与Rails 3一起工作,幸运的是,一个项目已经在http://railsplugins.org/开始,目的是列出所有兼容/不兼容的Rails插件。
My remote environment is already compatible with Rails 3, I'm using Passenger with Ruby Enterprise Edition (1.8.7). The only blocking issue are plugins.
我的远程环境已经与Rails 3兼容了,我正在使用带有Ruby Enterprise Edition的乘客(1.8.7)。唯一的阻塞问题是插件。
I guess it would take at least one month before having the major part of my Rails app ready for Rails 3 thought I won't probably start the upgrade until Rails 3 stable is out or I really need the new version for some blocking feature (ex. subdomain-based routing).
我想至少需要一个月的时间才能让我的Rails应用程序的主要部分为Rails 3做好准备,以为我不会开始升级,直到Rails 3稳定出局或我真的需要新版本的某些阻止功能(ex 。基于子域的路由)。
#4
2
I'm not going to upgrade any apps to rails 3.
我不会将任何应用程序升级到rails 3。
However, I just decided that all new projects will be rails3 going forward. The lack of plugin support isn't a big issue as I see it as an opportunity to decouple my apps from plugins so that I can swap them in and out as I please later.
但是,我刚刚决定所有新项目都将成为rails3。缺乏插件支持不是一个大问题,因为我认为这是一个将我的应用程序与插件分离的机会,以便我可以随后将它们交换进去。
I also suspect that the big plugins will upgrade very quickly as they won't want to be left in the dust.
我还怀疑大插件会很快升级,因为他们不想被遗忘。
Keep track of plugin status here.
在此处跟踪插件状态。
#5
1
I've been keeping my apps on the edge of 2.3, but since there's a lot of fundamental changes to Rails in 3, I'll probably install the beta, work on converting them over and hope to be ready by the time it's released as stable.
我一直把我的应用程序放在2.3的边缘,但由于Rails在3中有很多根本性的变化,我可能会安装测试版,努力将它们转换过来并希望在它发布时做好准备。稳定。
I'm also glad there's a lot of lead time before RailsConf so I can really get familiar with the new features of Rails 3 and won't feel lost/overwhelmed there.
我很高兴在RailsConf之前有很多准备时间,所以我可以真正熟悉Rails 3的新功能,并且不会感到丢失/不堪重负。
#6
1
I don't think I'll upgrade any of my applications. It would be a large amount of work compared to what I'd gain from it. Also in some cases the plugins/gems I used in my app are not compatible with Rails 3 so upgrading would be impossible or would require to fork the gems... too time consuming.
我不认为我会升级我的任何应用程序。与我从中获得的相比,这将是一项大量的工作。在某些情况下,我在我的应用程序中使用的插件/宝石与Rails 3不兼容,因此升级是不可能的,或者需要分叉宝石......太耗费时间。
If I had to update, I'd probably wait a bit more for all the gems/plugins to be updated to Rails 3. Of course any new application I'll develop will be done using Rails 3.
如果我不得不更新,我可能会等待更多的所有gems /插件更新到Rails 3.当然,我将开发的任何新应用程序将使用Rails 3完成。
#7
0
I'll answer my own question.
我会回答我自己的问题。
I'm not sure how many betas there are going to be for Rails 3, but I'm going to hold off converting my blog application until the next beta or the final release. I think it's going to be quite a time-consuming process because I have a lot of view helpers that build markup, a lot of named scopes and some quite complicated routing.
我不确定Rails 3会有多少测试版本,但是我会暂时将我的博客应用程序转换为下一个测试版或最终版本。我认为这将是一个非常耗时的过程,因为我有很多构建标记的视图助手,很多命名范围和一些非常复杂的路由。
I want to add page caching first before tackling Rails 3!
我想在处理Rails 3之前先添加页面缓存!
#8
0
After trying out the beta and it not wanting to work with any commands, I have decided to wait until a new beta.
在尝试测试版并且不想使用任何命令后,我决定等到新的测试版。
The ticket has already been opened for the issue.
已经为此问题打开了故障单。
#9
0
After realising that I probably spend more time in Zend Framework and Doctrine getting code to work (fixing framework bugs, annoying language workarounds, and just plain pain), than actually coding features I decided that it's finally time to give RoR a go. Especially as RoR3 is now out with a bunch of documentation.
在意识到我可能花更多时间在Zend Framework和Doctrine上运行代码(修复框架错误,烦人的语言解决方案,并且只是简单的痛苦)之后,实际上编码功能我决定最终给RoR一个时间。特别是因为RoR3现在有很多文档。
5 hours through and it's looking really promising. 1 hour of it was debugging though, some documentation on a plugin was not up to speed, but alas I'm there.
5个小时过去了,它看起来很有前途。虽然调试了1个小时,但是插件上的一些文档还没有达到速度,但是我就在那里。
It's interesting, and does seem to be in a better direction. More time to code on features, and less time coding to debug.
这很有趣,似乎确实朝着更好的方向发展。有更多时间对功能进行编码,减少编写调试的时间。
So the app I'm converting is my premium CMS that is deployed in over 20 websites now, and powers my own balupton.com - so will be interesting, as the CMS is already a complete featured cms.
因此,我正在转换的应用程序是我的高级CMS,现在已部署在20多个网站中,并为我自己的balupton.com提供支持 - 所以将会很有趣,因为CMS已经是一个完整的功能cms。