Turbogears / Rails的优点/缺点？ [英] Pros/Cons of Turbogears/Rails?
问题描述
首先，我不打算将此作为一场火焰战争。 Python
和Ruby是我唯一愿意工作的两种语言
（至少在普通语言中），以及TurboGears和
Rails看起来大致相当。
我对Python有更多的了解，但这是一个轻微的问题
问题 - 我一直在打算无论如何要了解更多Ruby。
以下是我了解并考虑的优点和缺点
重要：
Turbogears：
+ SqlObject允许使用SQL本身使用数据库表而不需要
。
+可能更快，因为据我所知，Python
明显更快。
+轻松访问其他库（如Python）
成像图书馆）Ruby，相对较新的
语言，没有等价物。
+内置的默认SQLite使设置更容易？
（据我所知，Ruby默认需要MySql - 做我不知道这是多么容易改变。）
+我发现模板系统有点清洁;代码在
py：xml命名空间允许纯.html模板，而不是
相当于.rhtml文件。
Ruby：
+更成熟的系统。更稳定？更多功能？
+更好的记录。这是一个很大的问题。
+内置的Rubydoc系统可以更轻松地记录
系统。 （恕我直言，开发人员几乎总是
低估了需要良好的文档，
与系统一起写。）是否有一个
Python doc系统已经收到了Guido的祝福
了吗？ D''氧气似乎是一个明显的选择。
+更好地协调Javascript助手代码？
我最初倾向于Rails因为成熟，
但是最新版本的TurboGears似乎已经修复了很多ad hoc。感觉我从以前的
版本中得到了。但是我仍然在空中。
谢谢，
肯
P.S.如果我想通过直接通过连接流式传输
文件数据来提供图像，而不是通过引用图像文件的
，我该怎么做？我想要b $ b喜欢构建代码，允许将图像组装成单个文件相册（zip或bsddb文件），并且
所以不能将它们称为单独的图像文件。
First, I don''t intend this to be a flame war, please. Python
and Ruby are the only two languages I''d willingly work in
(at least amongst common languages), and TurboGears and
Rails seem roughly equivalent.
I''m much more knowledgable about Python, but that''s a minor
issue--I''ve been intending to learn more Ruby anyway.
Here are the pros and cons that I''m aware of and consider
important:
Turbogears:
+ SqlObject allows working with the DB tables without
using SQL itself.
+ Likely to be faster because as far as I''m aware, Python
is significantly faster.
+ Easy access to other libraries (such as the Python
Imaging Library) that Ruby, being a relatively newer
language, doesn''t have equivalents to.
+ Built-in default SQLite makes it easier to set up?
(as far as I can tell, Ruby requires MySql by default--don''t
know how easy this is to change.)
+ I find the templating system somewhat cleaner; code in
py: xml namespace allows pure .html templates, instead
of equivalent of .rhtml files.
Ruby:
+ More mature system. More stable? More features?
+ Much better documented. This is a biggie.
+ Built-in Rubydoc system would make documenting the
system easier. (IMHO, developers almost always
underestimate the need for good documentation that
is written along withe the system.) Is there a
Python doc system that has received Guido''s blessing
yet? D''oxygen would seem an obvious choice.
+ Better coordination with Javascript helper code?
I was initially leaning towards Rails due to maturity,
but the most recent version of TurboGears seem to have
fixed a lot of the "ad hoc" feeling I got from previous
versions. But I''m still very much up in the air.
Thanks,
Ken
P.S. If I wanted to provide an image by streaming the
file data directly over the connection, rather than by
referring to an image file, how would I do that? I''d
like to build code that would allow images to be assembled
into a single-file photo album (zip or bsddb file), and
so can''t refer to them as individual image files.
推荐答案
ke **************** @ sbcglobal.net 写道：
看起来你在混合比较。
ke****************@sbcglobal.net wrote:
Looks like you mixing comparisons.
Ruby：
+更成熟的系统。更稳定？更多功能？
Ruby:
+ More mature system. More stable? More features?
呃，不，Python早在Ruby之前就好了一点
Rails可能是旧的比起Turbogears，但它仍然只是正式上去了1.0
。
任何定义都不能称之为成熟。
uh, no, Python predates Ruby by a good bit
Rails might be "older" than Turbogears but it still JUST went 1.0
officially.
It can''t be called "mature'' by any defintition.
+更好的记录。这是一个很大的问题。
+ Much better documented. This is a biggie.
Rails没有文档，期限。作者公开承认这个
。
Rails has no documentation, period. The authors acknowledge this
openly.
+内置Rubydoc系统会让
系统更容易记录。 （恕我直言，开发人员几乎总是
低估了需要良好的文档，
与系统一起写。）是否有一个
Python doc系统已经收到了Guido的祝福
了吗？ D''氧气似乎是一个明显的选择。
+ Built-in Rubydoc system would make documenting the
system easier. (IMHO, developers almost always
underestimate the need for good documentation that
is written along withe the system.) Is there a
Python doc system that has received Guido''s blessing
yet? D''oxygen would seem an obvious choice.
Pydoc IS标准。这已经存在了很长时间。
Pydoc IS standard. This has been around for a long time.
+更好地协调Javascript助手代码？
+ Better coordination with Javascript helper code?
再次，这是一篇Python vs Ruby或Turbogears vs Rails帖子，你似乎对语言与框架之间的区别感到非常困惑。
Again, is this a Python vs Ruby or Turbogears vs Rails post, you seem
highly confused on the distinctions between language vs framework.
由于成熟，我最初倾向于Rails，
但是最新版本的TurboGears似乎有
修复了很多ad hoc感觉我从以前的
版本中得到了。但是我仍然非常高兴。
I was initially leaning towards Rails due to maturity,
but the most recent version of TurboGears seem to have
fixed a lot of the "ad hoc" feeling I got from previous
versions. But I''m still very much up in the air.
，根据任何定义，Ruby都不能被认为是''成熟'。
again, Ruby can''t be considered ''mature'' by any definition.
谢谢，
肯
PS如果我想通过直接通过连接流式传输
文件数据来提供图像，而不是通过引用图像文件的
，我该怎么做？我想要b $ b喜欢构建代码，允许将图像组装成单个文件相册（zip或bsddb文件），并且
所以不能将它们称为单独的图像文件。
Thanks,
Ken
P.S. If I wanted to provide an image by streaming the
file data directly over the connection, rather than by
referring to an image file, how would I do that? I''d
like to build code that would allow images to be assembled
into a single-file photo album (zip or bsddb file), and
so can''t refer to them as individual image files.
??????
??????
fuzzylollipop写道：
fuzzylollipop wrote:
呃，不，Python比Ruby早一点
Rails可能是更老的比起Turbogears，但它仍然只是正式推出1.0
。
任何定义都不能称之为成熟。
uh, no, Python predates Ruby by a good bit
Rails might be "older" than Turbogears but it still JUST went 1.0
officially.
It can''t be called "mature'' by any defintition.
但至少在大多数开发人员的认知中，它（不一定是绝对意义上的b $ b，但也许相对于Django或Turbogears）。
介意，它甚至不需要是真的，我们在这里谈论感知
。另外，我不是只谈论Python和/或Ruby开发人员
这里，我说的是一般的开发人员，其中很多是
来了来自Java / .NET背景。
我知道很多人，其中很多人都知道Rails。当你说
Turbogears或Django时，他们会去，什么？。
可悲的是，有更多的Java人知道Ruby比起Python，
尽管Python在Ruby之前已经存在了很多年......
（这肯定是Bruce Tate老兄的错！） />
< snip>
But at least in most developers'' perception, it is (not necessarily in
the absolute sense, but perhaps relative to Django or Turbogears).
Mind, it doesn''t even need to be true, we''re talking of perception
here. Also, I''m not talking about only Python and/or Ruby developers
here, I''m talking about developers in general, a huge bunch of which
comes from Java/.NET background.
I know many of them and a lot of them do know Rails. When you say
Turbogears or Django, however, they go, "what?".
Sadly, there are more Java guys who know about Ruby than Python,
despite the fact that Python predates Ruby by quite a few years...
(this must be that Bruce Tate dude''s fault! )
<snip>
Ray写道：
Ray wrote:
fuzzylollipop写道：
fuzzylollipop wrote:
>呃，不，Python早于Ruby一段时间
Rails可能是旧的比起Turbogears，但它仍然只是正式的1.0
它不能被任何定义称为成熟。
>uh, no, Python predates Ruby by a good bit
Rails might be "older" than Turbogears but it still JUST went 1.0
officially.
It can''t be called "mature'' by any defintition.
但至少在大多数开发人员的认知中，它是（绝对意义上不一定是
，但也许相对于Django或Turbogears）。
介意，它甚至不需要是真的，我们在这里谈论感知
。
But at least in most developers'' perception, it is (not necessarily in
the absolute sense, but perhaps relative to Django or Turbogears).
Mind, it doesn''t even need to be true, we''re talking of perception
here.
你可能是。线程中没有其他人。
-
Robert Kern
我来过相信整个世界都是一个谜，一个无害的谜团，因为我们疯狂地试图解释它，好像它有一个潜在的真相，这让我觉得很可怕。
- Umberto Eco
You might be. No one else in the thread is.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco
这篇关于Turbogears / Rails的优点/缺点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
