您会开始学习Smalltalk吗? [英] Would you start learning Smalltalk?
问题描述
我的问题很简单！
- 如果有时间，您会开始学习Smalltalk吗?为什么?为什么不呢?
- 您已经了解Smalltalk吗?为什么您会推荐Smalltalk?为什么不呢?
我个人是Ruby on Rails程序员，我真的很喜欢它.但是，我正在考虑Smalltalk，因为我阅读了许多博客，并且有些人称Ruby为"Smalltalk Light"之类的东西.我对Smalltalk感兴趣的第二个原因是海边.
Personally I'm a Ruby on Rails programmer and I really like it. However, I'm thinking about Smalltalk because I read various blogs and some people are calling Ruby something like "Smalltalk Light". The second reason why I'm interested in Smalltalk is Seaside.
也许有人之前做了相同的转换?
Maybe someone has made the same transition before?
编辑:实际上，让我对Smalltalk/Seaside最为兴奋的是以下WebDevRadio情节:
Actually, what got me most excited about Smalltalk/Seaside is the following Episode of WebDevRadio: Episode 52: Randal Schwartz on Seaside (among other things)
推荐答案
如果您喜欢Ruby，则可能会喜欢Smalltalk. IIRC Seaside已被移植到 Gemstone VM ，这是其Gemstone/S OODBMS的一部分.与Ruby相比，它具有更好的线程支持，因此对于大容量系统而言，它是更好的后端.这可能是仔细研究它的好理由.
If you like Ruby you'll probably like Smalltalk. IIRC Seaside has been ported to the Gemstone VM, which is part of their Gemstone/S OODBMS. This has much better thread support than Ruby, so it is a better back-end for a high-volume system. This might be a good reason to take a close look at it.
学习Smalltalk的原因:
Reasons to learn Smalltalk:
-
这是一个非常非常好的编程环境.一旦掌握了这一点(对于习惯于C ++或Java的人来说，这往往会引起文化冲击)，您会发现它是一个非常好的工作环境.我使用的旧Digitalk是一个非常令人愉悦的系统.许多旧的XP和OO专家类型，例如肯特贝克(Kent Beck)和并且偶尔会听到人们对往日美好时光的渴望(感谢Frank Shearer的引文，+ 1)-敏捷开发源于此平台.
It's a really, really nice programming environment. Once you've got your head around it (it tends to be a bit of a culture shock for people used to C++ or Java) you'll find it to be a really good environment to work in. Even a really crappy smalltalk like the Old Digitalk ones I used is a remarkably pleasant system to use. Many of the old XP and O-O guru types like Kent Beck and Martin Fowler cut their teeth on Smalltalk back in the day and can occasionally be heard yearning for the good old days in public (Thanks to Frank Shearer for the citation, +1) - Agile development originated on this platform.
这是历史上生产力最高的开发平台之一.
It's one of the most productive development platforms in history.
存在几种成熟的实现，并且那里有令人惊讶的庞大代码库.一方面，它在金融市场圈中变得非常流行，在这些市场中，开发人员的生产力和上市时间相当重要.直到1990年代中期，如果您想要一种适用于应用程序开发的商业支持的高级语言，那么它大约是该镇唯一的游戏(LISP可能除外).
Several mature implementations exist and there's a surprisingly large code base out there. At one point it got quite trendy in financial market circles where developer productivity and time-to-market is quite a big deal. Up until the mid 1990s it was more or less the only game in town (With the possible exception of LISP) if you wanted a commercially supported high-level language that was suitable for application development.
部署很容易-只需将映像文件放在适当的目录中即可.
Deployment is easy - just drop the image file in the appropriate directory.
并不是真正的原因，但是四本书将Smalltalk用于其中的许多示例.
Not really a reason, but the Gang of Four Book uses Smalltalk for quite a few of their examples.
不学习Smalltalk的原因:
Reasons not to learn Smalltalk:
-
这是一个利基市场.您可能找不到工作.但是，如果您在拥有服务器的地方生产某种 .com应用程序，则可能不是问题.
它被许多人视为传统系统.平台上的新进展相对较少(尽管Seaside似乎正在推动复兴).
It's viewed as a legacy system by many. There is relatively little new development on the platform (although Seaside seems to be driving a bit of a renaissance).
它通常无法与传统的源代码控制系统很好地配合使用(至少在90年代中期我使用它时).
It tends not to play nicely with traditional source control systems (at least as of the early-mid 90's when I used it). This may or may not still be the case.
它有点孤立，喜欢自己玩. Python或Ruby是为从头开始集成而构建的，并且往往更加混杂，因此更易于与第三方软件集成.但是，其他更主流的系统或多或少地受到这种类型的孤立的困扰，似乎并没有太大阻碍.
It is somewhat insular and likes to play by itself. Python or Ruby are built for integration from the ground up and tend to be more promiscuous and thus easier to integrate with 3rd party software. However, various other more mainstream systems suffer from this type of insularity to a greater or lesser degree and that doesn't seem to impede their usage much.
这篇关于您会开始学习Smalltalk吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
