星期日, 十二月 21, 2008

[Geekland]Tanenbaum V.s. Torvalds Debate(Zh_v0.10)

多少年前的老gabua啊,居然被我翻出来了。^-^

火星四射,一个绵里藏针,一个锋芒毕露,都是角。这里有个解读的版本,可惜不够详细。我愈看愈觉得有趣,下面是个小小的尝试。

Appendix A

The Tanenbaum-Torvalds Debate

What follows in this appendix are what are known in the community as the Tanenbaum/Linus "Linux is obsolete" debates. Andrew Tanenbaum is a well-respected researcher who has made a very good living thinking about operating systems and OS design. In early 1992, noticing the way that the Linux discussion had taken over the discussion in comp.os.minix, he decided it was time to comment on Linux.

{一些背景介绍,1992年在Usenet上的comp.os.minix上面已经充斥着linux的相关讨论了,Tanenbaum 先生为了捍卫自己的领地,决定开火了}

Although Andrew Tanenbaum has been derided for his heavy hand and misjudgements of the Linux kernel, such a reaction to Tanenbaum is unfair. When Linus himself heard that we were including this, he wanted to make sure that the world understood that he holds no animus towards Tanenbaum and in fact would not have sanctioned its inclusion if we had not been able to convince him that it would show the way the world was thinking about OS design at the time.

{我们之所以把这些mail包含在这个附件中,不是想冒犯Tanenbaum 先生,连Linus本人对Tanenbaum 先生怀有极大的敬意}

We felt the inclusion of this appendix would give a good perspective on how things were when Linus was under pressure because he abandoned the idea of microkernels in academia. The first third of Linus' essay discusses this further.

我们只是想说明当时Linus,/社区领袖/,在linux发展的开始时期承受了非常巨大的压力,因为linux不是按照学院派微内核的方式来开始的。

{叛逆,独树一帜,good as we expected}

Electronic copies of this debate are available on the Web and are easily found through any search service. It's fun to read this and note who joined into the discussion; you see user-hacker Ken Thompson (one of the founders of Unix) and David Miller (who is a major Linux kernel hacker now), as well as many others.

{看看还有些谁吧!下面我们也可以看到他们的精彩演出}

To put this discussion into perspective, when it occurred in 1992, the 386 was the dominating chip and the 486 had not come out on the market. Microsoft was still a small company selling DOS and Word for DOS. Lotus 123 ruled the spreadsheet space and WordPerfect the word processing market. DBASE was the dominant database vendor and many companies that are household names today--Netscape, Yahoo, Excite--simply did not exist.

注意,这一切都是在1992年发生的,只有386,486还没有出现,m$只是一家买买dos和word的小公司。应用软件市场被Lotus123,WordPerfect还有DBASE统治。而网络,Netscape,Yahoo,Excite都还没有出现{更别提google了}


{馒头由Tanenbaum引发,主题鲜明,linux是过时的/linux是陈旧的/linux是**}


From: ast@cs.vu.nl (Andy Tanenbaum)

Newsgroups: comp.os.minix
Subject: LINUX is obsolete
Date: 29 Jan 92 12:12:50 GMT 

 

I was in the U.S. for a couple of weeks, so I haven't commented much on LINUX (not that I would have said much had I been around), but for what it is worth, I have a couple of comments now.

最近我在美国呆了几个星期,所以我没有对LINUX发表什么评价,(这不是说我不大来这儿)但是LINUX是值得我来评价一下的,下面就是我个人的几点意见。

{山中无老虎,猴子称大王,现在,我要踏着五彩祥云,穿着金色盔甲,在神的注视下对你们这些****发出秒杀的一击了,来吧...}

As most of you know, for me MINIX is a hobby, something that I do in the evening when I get bored writing books and there are no major wars, revolutions, or senate hearings being televised live on CNN. My real job is a professor and researcher in the area of operating systems.

正如你们大多数人知道的那样,对我而言,MINIX只是一个爱好,只是当我在晚上写书写累了的时候,或者CNN没有直播诸如战争,革命,听证会等等的时候,MINIX是我的一种消遣。我的工作是一名教授,研究方向就是OS。

{教授!懂吗?Prof.¥^%……*摆明身份,拉开距离}

As a result of my occupation, I think I know a bit about where operating are going in the next decade or so. Two aspects stand out:

出于一种职业敏感,对于OS在下一个十年当中如何发展的我多少还知道一点。两个方面:

1. MICROKERNEL VS MONOLITHIC SYSTEM Most older operating systems are monolithic, that is, the whole operating system is a single a.out file that runs in 'kernel mode.' This binary contains the process management, memory management, file system and the rest. Examples of such systems are UNIX, MS-DOS, VMS, MVS, OS/360, MULTICS, and many more. 

1. 微内核 VS 宏内核

大多数老的系统是宏内核的,就是,整个系统就是一个a.out文件运行在‘内核模式’下的。这个二进制文件包含了进程管理,内存管理,文件系统以及其它等等。比如{…}

The alternative is a microkernel-based system, in which most of the OS runs as separate processes, mostly outside the kernel. They communicate by message passing. The kernel's job is to handle the message passing, interrupt handling, low-level process management, and possibly the I/O. Examples of this design are the RC4000, Amoeba, Chorus, Mach, and the not-yet-released Windows/NT. 

另一种就是所谓的微内核系统,OS的大部分都作为内核之外的独立进程运行。他们之间通过message交互,内核的工作主要是处理message传递,中断处理,底层进程管理,也许还有一些I/O处理。例如{...}

While I could go into a long story here about the relative merits of the two designs, suffice it to say that among the people who actually design operating systems, the debate is essentially over. Microkernels have won. The only real argument for monolithic systems was performance, and there is now enough evidence showing that microkernel systems can be just as fast as monolithic systems (e.g., Rick Rashid has published papers comparing Mach 3.0 to monolithic systems) that it is now all over but the shoutin'.

对于两种设计的优劣我可以长篇大论一番,足以那些真正有能力设计OS的人满意。这里我只给出结论,争论已经结束,微内核已经赢了,唯一可以商榷的是宏内核系统具有一些性能方面的优势,但是也有证据表明微内核系统可以跑得和宏内核系统一样快(e.g.,...)

{直接给出结论,微内核更好,为下一波攻击奠定基础}

MINIX is a microkernel-based system. The file system and memory management are separate processes, running outside the kernel. The I/O drivers are also separate processes (in the kernel, but only because the brain-dead nature of the Intel CPUs makes that difficult to do otherwise). LINUX is a monolithic style system. This is a giant step back into the 1970s. That is like taking an existing, working C program and rewriting it in BASIC. To me, writing a monolithic system in 1991 is a truly poor idea. 

MINIX是一个基于微内核的系统。文件系统和内存管理都是单独的进程,运行于内核之外。I/O drivers也是单独的进程(在内核之中,不过要不是脑残的Intel CPUs,也是可以做到的)。而LINUX是一个宏内核系统,这是一个向着1970年代的巨大退步。就像拿BASIC去重写一个现有的,并且可以运行的C程序一样。对我来说,在1991年还是以一个宏内核的方式去写一个OS是一个非常差的主意。

{喝酒吃肉骂娘,把矛头对准商业公司肯定不是一个坏主意

 

我怎么想到了肯尼迪的人类一大步?

}

2. PORTABILITY

Once upon a time there was the 4004 CPU. When it grew up it became an 8008. Then it underwent plastic surgery and became the 8080. It begat the 8086, which begat the 8088, which begat the 80286, which begat the 80386, which begat the 80486, and so on unto the N-th generation. In the meantime, RISC chips happened, and some of them are running at over 100 MIPS. Speeds of 200 MIPS and more are likely in the coming years. These things are not going to suddenly vanish. What is going to happen is that they will gradually take over from the 80x86 line. They will run old MS-DOS programs by interpreting the 80386 in software. (I even wrote my own IBM PC simulator in C, which you can get by FTP from ftp.cs.vu.nl = 192.31.231.42 in dir minix/simulator.) I think it is a gross error to design an OS for any specific architecture, since that is not going to be around all that long. 

2.可移植性

有的一段时间是4004,然后变成了8008,8080。8086,80286,80386...与此同时RISC芯片业出现了,有些已经超过了100MIPS。200MIPS也有望在不久出现。类似的状况不会突然消失。很可能将来会有新的产品取代80x86产品线。他们将不得不从软件上模拟80386来运行老的MS-DO程序(我本人甚至就用C写过IBM PC模拟器,从...得到)我认为设计一个运行在特定硬件架构上的OS是一个根本性的错误,因为任何一个硬件架构不可能永久存在.

MINIX was designed to be reasonably portable, and has been ported from the Intel line to the 680x0 (Atari, Amiga, Macintosh), SPARC, and NS32016. LINUX is tied fairly closely to the 80x86. Not the way to go. 

MINIX的移植性设计合理,已经从Intel产品线移植到了680x0...而LINUX和80x86结合的太紧密了,这条路不大行得通。

Don't get me wrong, I am not unhappy with LINUX. It will get all the people who want to turn MINIX in BSD UNIX off my back. But in all honesty, I would suggest that people who want a **MODERN** "free" OS look around for a microkernel-based, portable OS, like maybe GNU or something like that. 

Andy Tanenbaum (ast@cs.vu.nl)

别误会,我不是对LINUX不爽 。我只是想让试图从MINIX转到BSD UNIX那些人别来烦我。不过我要真诚地对那些希望得到一个**现代的**"自由的"OS的人说,去找一个基于微内核的,可移植的,也许GNU或者类似的东东是一个选择。

 

Andy Tanenbaum (ast@cs.vu.nl)

{ast就是Tanenbaum

可以看出,当时GNU在做了那么多的准备以后,雄心勃勃的准备开发的OS应该是一个微内核的OS,可惜胎死腹中,也许下面的持续讨论会有一点结论

}

P.S. Just as a random aside, Amoeba has a UNIX emulator (running in user space), but it is far from complete. If there are any people who would like to work on that, please let me know. To run Amoeba you need a few 386s, one of which needs 16M, and all of which need the WD Ethernet card.


{Torvalds登场,锵锵锵锵...}


From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Re: LINUX is obsolete
Date: 29 Jan 92 23:14:26 GMT

Organization: University of Helsinki

Well, with a subject like this, I'm afraid I'll have to reply. Apologies to minix-users who have heard enough about linux anyway. I'd like to be able to just "ignore the bait", but ... Time for some serious flamefesting! 

对这样一个主题,我恐怕不能不有所回应了。不管怎样,还是要对那些听够了linux的minix用户致歉。我希望大家能够做到“让狗叫吧”,不过...是时候来点严肃的论证了。

{Torvalds开始谦逊几句,没办法,谁叫那时Torvalds还是小弟呢!不过马上就可以看到他的伶牙俐齿了...}

In article <12595@star.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes:


>>I was in the U.S. for a couple of weeks, so I haven't commented much on
>LINUX (not that I would have said much had I been around), but for what
>it is worth, I have a couple of comments now.
>>As most of you know, for me MINIX is a hobby, something that I do in the
>evening when I get bored writing books and there are no major wars,
>revolutions, or senate hearings being televised live on CNN. My real
>job is a professor and researcher in the area of operating systems. 

You use this as an excuse for the limitations of minix? Sorry, but you loose: I've got more excuses than you have, and linux still beats the pants of minix in almost all areas. Not to mention the fact that most of the good code for PC minix seems to have been written by Bruce Evans.


> ...

你用这个借口来掩饰minix的不足?对不起,你输了:我可以有比你更多的借口,但是linux还是几乎在各个方面都打败了minix。更不要说似乎大部分运行在PC上minix上不错的code都是我的朋友Bruce Evans写的

{首先一样表明态度linux才是赢家,然后打蛇打七寸...教授有什么了不起,还不是不会写代码

Bruce Evans此公也是一角,据说Torvalds从他那里学到了很多Unix的知识}

Re 1: you doing minix as a hobby - look at who makes money off minix, and who gives linux out for free. Then talk about hobbies. Make minix freely available, and one of my biggest gripes with it will disappear. Linux has very much been a hobby (but a serious one: the best type) for me: I get no money for it, and it's not even part of any of my studies in the university. I've done it all on my own time, and on my own machine. 

Re 1:你做minix只是出于爱好 - 看看到底是谁从minix中间收钱吧,而谁又把linux完全免费。说道爱好,让minix完全免费,那么我最大的一个桎梏就会消失。Linux对我而言,很大程度上是一种爱好(不过是认真的:最好的一种):我没有从中得到经济利益,甚至都不是我大学学习课程的一部分。我完全用个人时间,在我个人机器上完成的

Re 2: your job is being a professor and researcher: That's one hell of a good excuse for some of the brain-damages of minix. I can only hope (and assume) that Amoeba doesn't suck like minix does.

Re 2:你的工作是教授和研究员:这倒是minix有些脑残的好借口。我所能期望的是Amoeba不要像minix那么稀烂。


>1. MICROKERNEL VS MONOLITHIC SYSTEM

True, linux is monolithic, and I agree that microkernels are nicer. With a less argumentative subject, I'd probably have agreed with most of what you said. From a theoretical (and aesthetical) standpoint linux looses. If the GNU kernel had been ready last spring, I'd not have bothered to even start my project: the fact is that it wasn't and still isn't. Linux wins heavily on points of being available now.

>1. 微内核 VS 宏内核
诚然,linux是宏内核的,我也认可微内核的优美性。作为一个较少争议的话题,我会同意大部分你说的。从理论角度上(以及美学角度),linux输了。如果GNU内核去年春天就已经就备的话,我是不会开始我的项目的:事实是它没有而且至今没有。在可用性上Linux赢了很多分。

{不是说GNU吗,不过还没有呢。minix?我提都不提,为什么,接着看}


> MINIX is a microkernel-based system. [deleted, but not so that you
> miss the point ] LINUX is a monolithic style system. 

If this was the only criterion for the "goodness" of a kernel, you'd be right. What you don't mention is that minix doesn't do the micro-kernel thing very well, and has problems with real multitasking (in the kernel). If I had made an OS that had problems with a multithreading filesystem, I wouldn't be so fast to condemn others: in fact, I'd do my damndest to make others forget about the fiasco.


>MINIX是一个基于微内核的系统。[删掉吧,...]LINUX是一个宏内核系统。

如果说,这是判别OS“好坏”的唯一标准,你就是对的。你怎么不提minix实际上的微内核做的不是那么好呢,并且在真正多任务(在内核中)上面有很大的问题。如果我的OS在多线程FS上面有问题,我不会那么着急的去骂别人的OS的:实际上,我把我的咒骂送给那些让别人忘记这一点的人。

[ yes, I know there are multithreading hacks for minix, but they are hacks, and bruce evans tells me there are lots of race conditions ]

[是的,我知道有很多针对minix多线程的hack,不过那些只是hacks,bruce evans还告诉我有很多资源竞争]

{译的不好,这一段火星四射,看看原文的语气和出现的单字吧。

虽然承认微内核更优美,但是指出minix做的并不好,关键是指出了minix自身技术上的缺点,这一点从后面其他人的发言可以得到验证

}


>2. PORTABILITY 

"Portability is for people who cannot write new programs" -me, right now (with tongue in cheek)


>2. 可移植性

“可移植性是为那些不会写新程序的人准备的”

-我, 现在(以调侃的语气)

The fact is that linux is more portable than minix. What? I hear you say. It's true - but not in the sense that ast means: I made linux as conformant to standards as I knew how (without having any POSIX standard in front of me). Porting things to linux is generally /much/ easier than porting them to minix.

事实上linux的移植性比minix要好。什么?我似乎听见你说。不过这是真的 - 不过不是在ast所说的意义上:我让linux兼容于我知道的正确(?)标准(没有任何POSIX标准在我面前)。比起minix,向linux移植软件通常/非常/容易。

{Prof.? 我就叫你ast}

I agree that portability is a good thing: but only where it actually has some meaning. There is no idea in trying to make an operating system overly portable: adhering to a portable API is good enough. The very /idea/ of an operating system is to use the hardware features, and hide them behind a layer of high-level calls. That is exactly what linux does: it just uses a bigger subset of the 386 features than other kernels seem to do. Of course this makes the kernel proper unportable, but it also makes for a /much/ simpler design. An acceptable trade-off, and one that made linux possible in the first place.

我认同可移植性是个好东西:但是这只在它确实能够有作用的地方。让一个OS过度的支持移植性是没有意义的:保持一个可移植得API足矣。OS的一个重要/观点/就是充分使用硬件的能力,并把硬件隐藏于一层高层调用的后面。这正是linux所作的:比起其他OS,看起来它使用386一个大得多的特性子集。当然使内核不大具有可移植性,不过这也使设计要简单/很多/。可接受的交换,并且可能使linux处于较好的位置。

I also agree that linux takes the non-portability to an extreme: I got my 386 last January, and linux was partly a project to teach me about it. Many things should have been done more portably if it would have been a real project. I'm not making overly many excuses about it though: it was a design decision, and last april when I started the thing, I didn't think anybody would actually want to use it. I'm happy to report I was wrong, and as my source is freely available, anybody is free to try to port it, even though it won't be easy.

Linus

我也认可linux把不可移植性带到了一个极端:去年一月我拿到了386,linux项目部分的让我意识了这一点。在一个真正的项目中间,让它具有移植请之前有很多事情要做。我不是找借口:这是一个设计决策,去年4月我开始时,我没有想到有谁真的想用它。我很高兴宣称我错了,不过既然我的源码公开,任何人想移植它都是可以的,尽管这可能不容易。

Linus

{这一大段,Torvalds讨论可移植性,首先表明写code才是王道,移植性再好,也意味着要写新code。进一步表明,移植性保持接口一致就OK。同时表明自己的理由,充分利用硬件的能力。最后说明linux是open source的,在接口一致的情况下,要移植谁都可以改它丫的

}

PS. I apologise for sometimes sounding too harsh: minix is nice enough if you have nothing else. Amoeba might be nice if you have 5-10 spare 386's lying around, but I certainly don't. I don't usually get into flames, but I'm touchy when it comes to linux :)

PS. 有些话可能有些刺耳,我为此道歉:如果你什么都没有,minix足够好了。如果你有5-10个空闲的386,Amoeba也很好。我平时不大发火,涉及到linux我有点暴躁 :)

{Torvalds现在都知道他大嘴了,不过那时还是小弟,还是小弟

Torvalds这封信逐条反驳,特别是从一些纯技术的角度指出了一些问题,不像Tanenbaum第一封邮件那样光说不练

}


{ast反击的号角}


From: ast@cs.vu.nl (Andy Tanenbaum)
Subject: Re: LINUX is obsolete
Date: 30 Jan 92 13:44:34 GMT 

In article <1992Jan29.231426.20469@klaava.Helsinki.FI> torvalds@klaava.Helsinki. FI (Linus Benedict Torvalds) writes:


>You use this [being a professor] as an excuse for the limitations of minix?

The limitations of MINIX relate at least partly to my being a professor: An explicit design goal was to make it run on cheap hardware so students could afford it. In particular, for years it ran on a regular 4.77 MHZ PC with no hard disk. You could do everything here including modify and recompile the system. Just for the record, as of about 1 year ago, there were two versions, one for the PC (360K diskettes) and one for the 286/386 (1.2M). The PC version was outselling the 286/386 version by 2 to 1. I don't have figures, but my guess is that the fraction of the 60 million existing PCs that are 386/486 machines as opposed to 8088/286/680x0 etc is small. Among students it is even smaller. Making software free, but only for folks with enough money to buy first class hardware is an interesting concept.


>你用这个(教授)作为minix的借口?

minix的局限性至少部分地应该归因于我是一个教授:最主要的设计目标就是让minix运行在便宜的硬件上,以便学生也能负担。具体点说,这么多年来minix可以运行在没有硬盘的4.77MHz的机器上。你能做的是任何事情,包括修改和重新编译整个系统。准确起见,大约1年前,minix有两个版本,一个用于PC(360k磁盘空间),一个用于286/386(1.2M)。PC版本买的更多,而286/386版本大概是二比一。我手边没有数据可查,我估计在6000w台PCs比起8088/286/680x0等等,386/486是很少的,在学生中他们可能会更少。让软件免费,但是这只是为那些有钱买得起第一流的硬件的人提供,这可真是个好主意。

{表明因为自己是个教授,minix主要用于学生,同时嘲讽linux虽然免费,但是它其实要求的硬件配置太高,大家实际上还是玩不起。

这里Tanenbaum老先生似乎对摩尔定律估计不足,而且软件开发比起硬件来,是个本质上困难的问题}

Of course 5 years from now that will be different, but 5 years from now everyone will be running free GNU on their 200 MIPS, 64M SPARCstation-5.

当然,5年之后情况将会截然不通。不过5年之后每个人都会在他们的200MIPS,64M的SPARC station-5机器上运行自由的GNU了。

{也表明自己的态度,相信免费是最终的方向,不过要在5年以后}


>Re 2: your job is being a professor and researcher: That's one hell of a
>good excuse for some of the brain-damages of minix. I can only hope (and
>assume) that Amoeba doesn't suck like minix does. Amoeba was not designed to run on an 8088 with no hard disk. 
>If this was the only criterion for the "goodness" of a kernel, you'd be
>right. What you don't mention is that minix doesn't do the micro-kernel
>thing very well, and has problems with real multitasking (in the >kernel). If I had made an OS that had problems with a multithreading
>filesystem, I wouldn't be so fast to condemn others: in fact, I'd do my
>damndest to make others forget about the fiasco.

A multithreaded file system is only a performance hack. When there is only one job active, the normal case on a small PC, it buys you nothing and adds complexity to the code. On machines fast enough to support multiple users, you probably have enough buffer cache to insure a hit cache hit rate, in which case multithreading also buys you nothing. It is only a win when there are multiple processes actually doing real disk I/O. Whether it is worth making the system more complicated for this case is at least debatable.


>...(引一大段话)

多线程FS的问题只需要一个性能上的hack。再说在性能受限的PC上,通常只有一个job是激活的,多线程FS除了在code上带来复杂之外,不会带来什么。而在机器足够快的足以支持多用户的系统之上,可能有足够大的缓冲区来保证缓存命中率,在这种情况下多线程也不会带来什么。唯一有用的情况是,多个进程确实在磁盘I/O。在这种情情况下,让系统变得更加复杂是否是值得的至少是有争议的。

{Tanenbaum轻描淡写的反驳了一番Torvalds指出的minix中的问题,得出不是个真正问题的结论。从后面将看到,这是一个失败的策略,从其他人的反馈来看,这是让Tanenbaum在后面的辩论中占据不利地位的一个因素}

I still maintain the point that designing a monolithic kernel in 1991 is a fundamental error. Be thankful you are not my student. You would not get a high grade for such a design :-)

我依然坚持在1991年依然设计一个宏内核的系统是一个根本性的错误。感谢老天你不是我的学生,要不然这样一个设计是不会得到高分的:)

{坚持基本观点,不过还是光说不练,保持了一种轻松的心态,似乎认为自己必胜。并且终于忍不住露出了学霸的嘴脸;-}


>The fact is that linux is more portable than minix. What? I hear you
>say. It's true - but not in the sense that ast means: I made linux as
>conformant to standards as I knew how (without having any POSIX standard
>in front of me). Porting things to linux is generally /much/ easier
>than porting them to minix.

MINIX was designed before POSIX, and is now being (slowly) POSIXized as everyone who follows this newsgroup knows. Everyone agrees that user-level standards are a good idea. As an aside, I congratulate you for being able to write a POSIX-conformant system without having the POSIX standard in front of you. I find it difficult enough after studying the standard at great length.


>...

MINIX在POSIX之前设计,在这个新闻组中的人也都知道,minix正在(缓慢的)POSIX化。任何人都认同在用户层面的标准是个好东东。说句题外话,恭喜你有能力在POSIX标准出来以前,就能写与POSIX兼容的系统。您别说,在学习标准标准一段时间后,我发现它还是很难的。

{haha,Flame真的是蛮有意思的,看看骂人觉得挺过瘾,Tanenbaum呢是老派绅士的讥讽,Torvalds呢就是新时代青年的怒火,原文二人的语气和用词遣句都可以参悟参悟,绝对提升功力}

My point is that writing a new operating system that is closely tied to any particular piece of hardware, especially a weird one like the Intel line, is basically wrong. An OS itself should be easily portable to new hardware platforms. When OS/360 was written in assembler for the IBM 360 25 years ago, they probably could be excused. When MS-DOS was written specifically for the 8088 ten years ago, this was less than brilliant, as IBM and Microsoft now only too painfully realize. Writing a new OS only for the 386 in 1991 gets you your second 'F' for this term. But if you do real well on the final exam, you can still pass the course.

Prof. Andrew S. Tanenbaum (ast@cs.vu.nl)

对于重新写一个与一个硬件架构紧密地联系的 OS,特别是Intel这样一个奇怪的产品线,我的观点是,这是根本错误的。一个OS自身应能够容易的移植到新的硬件平台上。在25年前,IBM 360选择用汇编在编写OS/360,他们可能还有借口。10年前MS-DOS只为8088写,这就要逊很多了。而IBM和M$现今也只能痛苦的面对现实。在1991年只为386重新写一个OS,会让你在这门课上得到第二个‘F’。不过如果你在期末考试中表现出色,你还是可以通过的。

Prof. Andrew S. Tanenbaum (ast@cs.vu.nl)

 

{又一次露出了学霸的面目

咦,怎么落款也变了?前面多了什么?}



From: feustel@netcom.COM (David Feustel)
Subject: Re: LINUX is obsolete
Date: 30 Jan 92 18:57:28 GMT
Organization: DAFCO - An OS/2 Oasis 

ast@cs.vu.nl (Andy Tanenbaum) writes:


>I still maintain the point that designing a monolithic kernel in 1991 is
>a fundamental error. Be thankful you are not my student. You would not
>get a high grade for such a design :-) 

That's ok. Einstein got lousy grades in math and physics.

{这是来打酱油的}


From: pete@ohm.york.ac.uk (-Pete French.)
Subject: Re: LINUX is obsolete
Date: 31 Jan 92 09:49:37 GMT
Organization: Electronics Department, University of York, UK 

In article <1992Jan30.195850.7023@epas.toronto.edu>, meggin@epas.utoronto.ca (David Megginson) says:>
> In article <1992Jan30.185728.26477feustel@netcom.COM> feustel@netcom.COM (David
> Feustel) writes:
>>
>>That's ok. Einstein got lousy grades in math and physics.
>> And Dan Quayle got low grades in political science. I think that there
>> are more Dan Quayles than Einsteins out there... ;-) 

What a horrible thought ! 

But on the points about microkernel v monolithic, isnt this partly an artifact of the language being used ? MINIX may well be designed as a microkernel system, but in the end you still end up with a large monolithic chunk of binary data that gets loaded in as "the OS". Isn't it written as separate programs simply because C does not support the idea of multiple processes within a single piece of monolithic code. Is there any real difference between a microkernel written as several pieces of C and a monolithic kernel written in something like OCCAM ? I would have thought that in this case the monolithic design would be a better one than the micorkernel style since with the advantage of inbuilt language concurrency the kernel could be made even more modular than the MINIX one is. 

Anyone for MINOX :-) 

-bat.

{来挺Torvalds,认为宏内核和微内核在实现上区别有限,甚至宏内核是一个更好的选择}


{肯爷爷也来了...}


From: kt4@prism.gatech.EDU (Ken Thompson)
Subject: Re: LINUX is obsolete
Date: 3 Feb 92 23:07:54 GMT
Organization: Georgia Institute of Technology 

viewpoint may be largely unrelated to its usefulness. Many if not most of the software we use is probably obsolete according to the latest design criteria. Most users could probably care less if the internals of the operating system they use is obsolete. They are rightly more interested in its performance and capabilities at the user level. 

有用性是与我们{**研究和开发人员**}所应该秉持的观点很大程度上是不相干的。根据最新的设计标准,如果不是大部分,至少是很多我们使用得软件都是过时的。大多数用户是不会关注他们正在使用的OS的内核是否过时,他们只会关注用户层面的性能和能力。

{用户体验才是王道,而不是设计理念。隐约批评了Tanenbaum,不过在第一句,肯爷爷就说有用没用不要紧,哈~~

后面大部分人会支持这个观点}

I would generally agree that microkernels are probably the wave of the future. However, it is in my opinion easier to implement a monolithic kernel. It is also easier for it to turn into a mess in a hurry as it is modified.

Regards, Ken

我同意在一般意义上微内核是未来的发展趋势。但是,我个人以为实现一个宏内核要更容易一点。但是宏内核在需要修改的时候也更容易掉进泥潭。

Regards, Ken

{看看,什么叫两边都不得罪,什么叫和稀泥,看不出来肯爷爷居然这种主,话说得是真有水平啊,都快赶上领导了}



From: kevin@taronga.taronga.com (Kevin Brown)
Subject: Re: LINUX is obsolete
Date: 4 Feb 92 08:08:42 GMT
Organization: University of Houston 

In article <47607@hydra.gatech.EDU > kt4@prism.gatech.EDU (Ken Thompson) writes:
>viewpoint may be largely unrelated to its usefulness. Many if not
>most of the software we use is probably obsolete according to the
>latest design criteria. Most users could probably care less if the
>internals of the operating system they use is obsolete. They are
>rightly more interested in its performance and capabilities at the
>user level.
>
>I would generally agree that microkernels are probably the wave of
>the future. However, it is in my opinion easier to implement a
>monolithic kernel. It is also easier for it to turn into a mess in
>a hurry as it is modified. 

How difficult is it to structure the source tree of a monolithic kernel such that most modifications don't have a large negative impact on the source? What sorts of pitfalls do you run into in this sort of endeavor, and what suggestions do you have for dealing with them? 

I guess what I'm asking is: how difficult is it to organize the source such that most changes to the kernel remain localized in scope, even though the kernel itself is monolithic? 

I figure you've got years of experience with monolithic kernels :-), so I'd think you'd have the best shot at answering questions like these. 

Kevin Brown



From: rburns@finess.Corp.Sun.COM (Randy Burns)
Subject: Re: LINUX is obsolete
Date: 30 Jan 92 20:33:07 GMT
Organization: Sun Microsystems, Mt. View, Ca. 

In article 12615@star.cs.vu.nl ast@cs.vu.nl (Andy Tanenbaum) writes:
>In article <1992Jan29.231426.20469@klaava.Helsinki.FI > torvalds@klaava.Helsinki.
>FI (Linus Benedict Torvalds) writes:  
>Of course 5 years from now that will be different, but 5 years from now
>everyone will be running free GNU on their 200 MIPS, 64M SPARCstation-5. Well, I for one would _love_ to see this happen.  
>>The fact is that linux is more portable than minix. What? I hear you
>>say. It's true - but not in the sense that ast means: I made linux as
>>conformant to standards as I knew how (without having any POSIX standard
>>in front of me). Porting things to linux is generally /much/ easier
>>than porting them to minix.

.........
>My point is that writing a new operating system that is closely tied to any
>particular piece of hardware, especially a weird one like the Intel line,
>is basically wrong.

First off, the parts of Linux tuned most finely to the 80x86 are the Kernel and the devices. My own sense is that even if Linux is simply a stopgap measure to let us all run GNU software, it is still worthwhile to have a finely tuned kernel for the most numerous architecture presently in existance. 


> An OS itself should be easily portable to new hardware
>platforms.

Well, the only part of Linux that isn't portable is the kernel and drivers. Compare to the compilers, utilities, windowing system etc. this is really a small part of the effort. Since Linux has a large degree of call compatibility with portable OS's I wouldn't complain. I'm personally very grateful to have an OS that makes it more likely that some of us will be able to take advantage of the software that has come out of Berkeley, FSF, CMU etc. It may well be that in 2-3 years when ultra cheap BSD variants and Hurd proliferate, that Linux will be obsolete. Still, right now Linux greatly reduces the cost of using tools like gcc, bison, bash which are useful in the development of such an OS.


{Torvalds再度出击}


From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Re: LINUX is obsolete
Date: 31 Jan 92 10:33:23 GMT
Organization: University of Helsinki 

In article <12615@star.cs.vu.nl > ast@cs.vu.nl (Andy Tanenbaum) writes:
>The limitations of MINIX relate at least partly to my being a professor:
>An explicit design goal was to make it run on cheap hardware so students
>could afford it. 

All right: a real technical point, and one that made some of my comments inexcusable. But at the same time you shoot yourself in the foot a bit: now you admit that some of the errors of minix were that it was too portable: including machines that weren't really designed to run unix. That assumption lead to the fact that minix now cannot easily be extended to have things like paging, even for machines that would support it. Yes, minix is portable, but you can rewrite that as "doesn't use any features", and still be right.

>...

什么都对:一个真正的技术观点,这使我的批评无可置疑。你正是搬起石头砸了自己的脚:现在你承认minix的问题在于它太可移植了一点:甚至包括了那些根本就不打算运行Unix的机器 。这个假设必定使minix不容易扩展到诸如支持分页,甚至是打算支持分页的机器上。是的,minix可移植,你可以用“不使用任何{**新硬件**}features”的方式来重写,这依然是对的。


>A multithreaded file system is only a performance hack. 

Not true. It's a performance hack /on a microkernel/, but it's an automatic feature when you write a monolithic kernel - one area where microkernels don't work too well (as I pointed out in my personal mail to ast). When writing a unix the "obsolete" way, you automatically get a multithreaded kernel: every process does it's own job, and you don't have to make ugly things like message queues to make it work efficiently.


> ...

这不对。这是一个在/微内核/上的性能hack,但是在宏内核上这是一个自然而然的feature - 这是一个微内核做的很差的一个地方(正如在我写给ast的私人邮件里那样)。按照“过时的”方式写的unix,你自然而然的会得到一个多线程的内核:每个进程都有自己的工作,你不需要诸如消息队列这样丑陋的东西来让一切工作的更有效。

{继续抓住技术问题,穷追猛打}

Besides, there are people who would consider "only a performance hack" vital: unless you have a cray-3, I'd guess everybody gets tired of waiting on the computer all the time. I know I did with minix (and yes, I do with linux too, but it's /much/ better). 

除此之外,那些认为“只是一个性能上的hack”重要的人:除非你有一台cray-3,我猜任何时候所有人都厌倦了等待机器。我知道我对minix就是如此(啊,是的,对linux我一样如此,不过这要好得/多/)。

{cray-3是一种超级计算机,用于上世纪80年代末期}


>I still maintain the point that designing a monolithic kernel in 1991 is
>a fundamental error. Be thankful you are not my student. You would not
>get a high grade for such a design :-) 

Well, I probably won't get too good grades even without you: I had an argument (completely unrelated - not even pertaining to OS's) with the person here at the university that teaches OS design. I wonder when I'll learn :) 

> ...

这样吧,即使我没有你,我也很可能拿不到好成绩:在这儿的那些在大学里教OS设计的人,我有一点异议要表达(完全没联系 - 不光OS什么事),我好奇什么时候我才要学习:)

{富贵功名与我如浮云,你想叫我还不学呢

又:瞧他最后一句说的多BH,天做衣裳地做席,我就不知道我还有需要学习的时候,牛人啊...}

>My point is that writing a new operating system that is closely tied to any
>particular piece of hardware, especially a weird one like the Intel line,
>is basically wrong. 

But /my/ point is that the operating system /isn't/ tied to any processor line: UNIX runs on most real processors in existence. Yes, the /implementation/ is hardware-specific, but there's a HUGE difference. You mention OS/360 and MS-DOG as examples of bad designs as they were hardware-dependent, and I agree. But there's a big difference between these and linux: linux API is portable (not due to my clever design, but due to the fact that I decided to go for a fairly-well-thought-out and tested OS: unix.) 


>...

但是/我/的观点是OS/不/系于任何一条处理器产品线:UNIX可以运行在大部分现在存在的处理器上。是的,/实现/是硬件相关的,但是这中间有巨大的区别。你说OS/360和MS-DOG{**WTF**}是个硬件中立设计的坏样板,我同意。但是这些OS和linux之间是不同的:linux的API是可移植的(不是因为我明智的设计,而是因为我决定跟随一个慎重考虑的,经过验证的OS :unix)

If you write programs for linux today, you shouldn't have too many surprises when you just recompile them for Hurd in the 21st century. As has been noted (not only by me), the linux kernel is a miniscule part of a complete system: Full sources for linux currently runs to about 200kB compressed - full sources to a somewhat complete developement system is at least 10MB compressed (and easily much, much more). And all of that source is portable, except for this tiny kernel that you can (provably: I did it) re-write totally from scratch in less than a year without having /any/ prior knowledge. 

你今天为linux写的程序,当你发现在21c,只需要为Hurd重现编译下就可以了的时候,请不要太惊奇。正如已经提到的(不仅仅是我一个人),linux内核只是整个系统的一小部分:现在linux全部的源代码压缩后只有200kB - 完整意义上的系统的源代码压缩后至少有10MB(很容易就多的多)。所有{linux现今的}源代码都是可移植的,除了这个微小的内核,也就是说你可以(可以查明:我就做过),在完全没有/任何/基础知识的情况下,1年以内你可以重头开始重新写出来。

{Hurd,就是GNU project中那个传说的kernel}

In fact the /whole/ linux kernel is much smaller than the 386-dependent things in mach: i386.tar.Z for the current version of mach is well over 800kB compressed (823391 bytes ccording to nic.funet.fi). Admittedly, mach is "somewhat" bigger and has more features, but that should still tell you something.

Linus

实际上,比起386架构相关的mach,/整个/linux内核要小很多:mach现今的压缩过的版本i386.tar.Z大于800kB(据nic.funet.fi,823391字节)。诚然,mach“某种程度上”是要更大,也有更多的features,不过这个事实依然可以说明一点什么。

Linus



From: kaufman@eecs.nwu.edu (Michael L. Kaufman)
Subject: Re: LINUX is obsolete
Date: 3 Feb 92 22:27:48 GMT
Organization: EECS Department, Northwestern University 

 

I tried to send these two posts from work, but I think they got eaten. If you have seen them already, sorry. 

------------------------------------------------------------------------------- 

Andy Tanenbaum writes an interesting article (also interesting was finding out that he actually reads this group) but I think he is missing an important point. 

He Wrote:
>As most of you know, for me MINIX is a hobby, ... 

Which is also probably true of most, if not all, of the people who are involved in Linux. We are not developing a system to take over the OS market, we are just having a good time. 


> What is going to happen
> is that they will gradually take over from the 80x86 line. They will
> run old MS-DOS programs by interpreting the 80386 in software. 

Well when this happens, if I still want to play with Linux, I can just run it on my 386 simulator. 


> MINIX was designed to be reasonably portable, and has been ported from the
> Intel line to the 680x0 (Atari, Amiga, Macintosh), SPARC, and NS32016.
> LINUX is tied fairly closely to the 80x86. Not the way to go. 

That's fine for the people who have those machines, but it wasn't a free lunch. That portibility was gained at the cost of some performance and some features on the 386. Before you decide that LINUX is not the way to go, you should think about what it is going to be used for. I am going to use it for running memory and computation intensive graphics programs on my 486. For me, speed and memory were more important then future state-of-the-artness and portability. 


>But in all honesty, I would
>suggest that people who want a **MODERN** "free" OS look around for a
>microkernel-based, portable OS, like maybe GNU or something like that. 

I don't know of any free microkernel-based, portable OSes. GNU is still vaporware, and likely to remain that way for the forseeable future. Do you actually have one to recomend, or are you just toying with me? ;-) 

------------------------------------------------------------------------------ 

In article 12615@star.cs.vu.nl ast@cs.vu.nl (Andy Tanenbaum) writes:
>My point is that writing a new operating system that is closely tied to any
>particular piece of hardware, especially a weird one like the Intel line,
>is basically wrong. An OS itself should be easily portable to new hardware
>platforms. 

I think I see where I disagree with you now. You are looking at OS design as an end in itself. Minix is good because it is portable/Micro-Kernal/etc. Linux is not good because it is monolithic/tightly tied to Intel/etc. That is not a strange attitude for someone in the acedemic world, but it is not something you should expect to be universally shared. Linux is not being written as a teaching tool, or as an abstract exercise. It is being written to allow people to run GNU-type software _today_. The fact that it may not be in use in five years is less important then the fact that today (well, by April probably) I can run all sorts of software on it that I want to run. You keep saying that Minix is better, but if it will not run the software that I want to run, it really isn't that good (for me) at all. 


> When OS/360 was written in assembler for the IBM 360
>25 years ago, they probably could be excused. When MS-DOS was written
>specifically for the 8088 ten years ago, this was less than brilliant, as
>IBM and Microsoft now only too painfully realize. 

Same point. MSoft did not come out with Dos to "explore the frontiers of os research". They did it to make a buck. And considering the fact that MS-DOS probably still outsells everyone else put together, I don't think that you say that they have failed _in their goals_. Not that MS-Dos is the best OS in terms of anything else, only that it has served their needs. 

Michael

{这个老兄从工程学的观点支持linux,指责minix/Tanenbaum光说不练}



From: julien@incal.inria.fr (Julien Maisonneuve)
Subject: Re: LINUX is obsolete
Date: 3 Feb 92 17:10:14 GMT 

I would like to second Kevin brown in most of his remarks.

I'll add a few user points :

- When ast states that FS multithreading is useless, it reminds me of the many times I tried to let a job run in the background (like when reading an archive on a floppy), it is just unusable, the & shell operator could even have been left out.

- Most interesting utilities are not even compilable under Minix because of the ATK compiler's incredible limits. Those were hardly understandable on a basic PC, but become absurd on a 386. Every stupid DOS compiler has a large model (more expensive, OK). I hate the 13 bit compress !

- The lack of Virtual Memory support prevents people studying this area to experiment, and prevents users to use large programs. The strange design of the MM also makes it hard to modify.

The problem is that even doing exploratory work under minix is painful. If you want to get any work done (or even fun), even DOS is becoming a better alternative (with things like DJ GPP). In its basic form, it is really no more than OS course example, a good toy, but a toy. Obtaining and applying patches is a pain, and precludes further upgrades.

Too bad when not so much is missing to make it really good. Thanks for the work andy, but Linux didn't deserve your answer. For the common people, it does many things better than Minix. 

Julien Maisonneuve. 

This is not a flame, just my experience.

{果然,这个老兄就从肯爷爷说的,用户体验的角度谈了几个minux的缺陷,同时也是Torvalds所说的多线程,缺乏虚拟内存管理,页式管理}


{此君好像是个猛人}


From: richard@aiai.ed.ac.uk (Richard Tobin)
Subject: Re: LINUX is obsolete
Date: 4 Feb 92 14:46:49 GMT Reply-To: richard@aiai.UUCP (Richard Tobin)
Organization: AIAI, University of Edinburgh, Scotland 

In article 12615@star.cs.vu.nl ast@cs.vu.nl (Andy Tanenbaum) writes:
>A multithreaded file system is only a performance hack. When there is only
>one job active, the normal case on a small PC, it buys you nothing 

I find the single-threaded file system a serious pain when using Minix. I often want to do something else while reading files from the (excruciatingly slow) floppy disk. I rather like to play rogue while waiting for large C or Lisp compilations. I look to look at files in one editor buffer while compiling in another. 

(The problem would be somewhat less if the file system stuck to serving files and didn't interact with terminal i/o.) 

Of course, in basic Minix with no virtual consoles and no chance of running emacs, this isn't much of a problem. But to most people that's a failure, not an advantage. It just isn't the case that on single-user machines there's no use for more than one active process; the idea only has any plausibility because so many people are used to poor machines with poor operating systems. 

As to portability, Minix only wins because of its limited ambitions. If you wanted a full-featured Unix with paging, job-control, a window system and so on, would it be quicker to start from basic Minix and add the features, or to start from Linux and fix the 386-specific bits? I don't think it's fair to criticise Linux when its aims are so different from Minix's. If you want a system for pedagogical use, Minix is the answer. But if what you want is an environment as much like (say) a Sun as possible on your home computer, it has some deficiencies. 

-- Richard {同样指出minux在多线程文件系统上糟糕的用户体验,

另外,指出minux在可移植性上较好的原因,正是Torvalds所说的有限的features实现,要简单,没有页式内存管理等等}


{ast,第三次出现}


From: ast@cs.vu.nl (Andy Tanenbaum)
Subject: Re: LINUX is obsolete
Date: 5 Feb 92 14:48:48 GMT
Organization: Fac. Wiskunde & Informatica, Vrije Universiteit, Amsterdam 

In article 6121@skye.ed.ac.uk richard@aiai.UUCP (Richard Tobin) writes:
>If you wanted a full-featured Unix with paging, job-control, a window
>system and so on, would it be quicker to start from basic Minix and
>add the features, or to start from Linux and fix the 386-specific
>bits? 

Another option that seems to be totally forgotten here is buy UNIX or a clone. If you just want to USE the system, instead of hacking on its internals, you don't need source code. Coherent is only $99, and there are various true UNIX systems with more features for more money. For the true hacker, not having source code is fatal, but for people who just want a UNIX system, there are many alternatives (albeit not free).

Andy Tanenbaum (ast@cs.vul.nl)  

这里好像另一个观点被忘记了,那就是购买UNIX或者克隆它。如果你只是需要使用系统,而不是从内部去hack他,那么你不需要源代码。两者加一起需要$99,更多其他的有着更多features的UNIX系统需要更多的钱。对于一名真正的hacker,没有源代码是致命的,而对那些仅仅希望一个UNIX系统的人,还是有很多其他的选择的(albeit不是免费的)

  Andy Tanenbaum (ast@cs.vul.nl)



From: ajt@doc.ic.ac.uk (Tony Travis)
Subject: Re: LINUX is obsolete
Date: 6 Feb 92 02:17:13 GMT
Organization: Department of Computing, Imperial College, University of London, UK. 

 

ast@cs.vu.nl (Andy Tanenbaum) writes:


> Another option that seems to be totally forgotten here is buy UNIX or a
> clone. If you just want to USE the system, instead of hacking on its
> internals, you don't need source code. Coherent is only $99, and there
> are various true UNIX systems with more features for more money. For the
> true hacker, not having source code is fatal, but for people who just
> want a UNIX system, there are many alternatives (albeit not free). 

 

Andy, I have followed the development of Minix since the first messages were posted to this group and I am now running 1.5.10 with Bruce Evans's patches for the 386. 

I 'just' want a Unix on my PC and I am not interested in hacking on its internals, but I *do* want the source code! 

An important principle underlying the success and popularity of Unix is the philosophy of building on the work of others. 

This philosophy relies upon the availability of the source code in order that it can be examined, modified and re-used in new software. 

Many years ago, I was in the happy position of being an AT&T Seventh Edition Unix source licencee but, even then, I saw your decision to make the source of Minix available as liberation from the shackles of AT&T copyright!! 

I think you may sometimes forget that your 'hobby' has had a profound effect on the availability of 'personal' Unix (ie. affordable Unix) and that the 8086 PC I ran Minix 1.2 on actually cost me considerably more than my present 386/SX clone. 

Clearly, Minix _cannot_ be all things to all men, but I see the progress to 386 versions in much the same way that I see 68000 or other linear address space architectures: it is a good thing for people like me who use Minix and feel constrained by the segmented architecture of the PC version for applications. 

NOTHING you can say would convince me that I should use Coherent ... 

Tony

{ast的拥趸,从侧面反映了广大Unix用户对AT&T的不满,热切地希望替代品,特别是PC上的替代品的出现。也许这也能解释BSD和linux的命运差异吧,当然社区领导人的因素也可能是原因之一}



From: richard@aiai.ed.ac.uk (Richard Tobin)
Subject: Re: LINUX is obsolete
Date: 7 Feb 92 14:58:22 GMT
Organization: AIAI, University of Edinburgh, Scotland 

In article <12696@star.cs.vu.nl
> ast@cs.vu.nl (Andy Tanenbaum) writes:
>If you just want to USE the system, instead of hacking on its
>internals, you don't need source code.  

Unfortunately hacking on the internals is just what many of us want the system for... You'll be rid of most of us when BSD-detox or GNU comes out, which should happen in the next few months (yeah, right). 

-- Richard

{早期用户都是高级用户,特别是PC用户,都是hacker,看看这个发言人的身份吧}



From: comm121@unixg.ubc.ca (Louie)
Subject: Re: LINUX is obsolete
Date: 30 Jan 92 02:55:22 GMT
Organization: University of British Columbia, Vancouver, B.C., Canada 

 

In <12595@star.cs.vu.nl > ast@cs.vu.nl (Andy Tanenbaum) writes:  
>But in all honesty, I would
>suggest that people who want a **MODERN** "free" OS look around for a
>microkernel-based, portable OS, like maybe GNU or something like that.

There are really no other alternatives other than Linux for people like me who want a "free" OS. Considering that the majority of people who would use a "free" OS use the 386, portability is really not all that big of a concern. If I had a Sparc I would use Solaris. 

As it stands, I installed Linux with gcc, emacs 18.57, kermit and all of the GNU utilities without any trouble at all. No need to apply patches. I just followed the installation instructions. I can't get an OS like this *anywhere* for the price to do my Computer Science homework. And it seems like network support and then X-Windows will be ported to Linux well before Minix. This is something that would be really useful. In my opinion, portability of standard Unix software is important also. 

I know that the design using a monolithic system is not as good as the microkernel. But for the short term future (And I know I won't/can't be uprading from my 386), Linux suits me perfectly. 

Philip Wu pwu@unixg.ubc.ca

 

{再次看到在PC革命刚刚开始的时候,可供PC机上运行的类Unix系统选择不多,solaris和BSD一个由于商业策略,一个由于不关心PC(我猜的:),错过了发展的绝佳机会,而其他同时代的众多原形,包括文中提到的众多OS,最典型的如Hurd过于雄心勃勃,没有注意到诸如ken爷爷说的UI问题,推出速度不够快,WIB

还有早期用户,可以看到这些人的能力都是非常强的专业人士,几乎是打着灯笼也难找的用户,他们关心的是一个真正可以运行的系统,linux占的了先机

linux上的另一个优势是和GNU项目的紧密结合,应用软件也是很重要的UI,GNU项目雄心万丈,由于PC革命的过早开始,或者GNU推出OS的速度赶不上PC革命,使得GNU的发展有点变样了}



From: dgraham@bmers30.bnr.ca (Douglas Graham)
Subject: Re: LINUX is obsolete
Date: 1 Feb 92 00:26:30 GMT
Organization: Bell-Northern Research, Ottawa, Canada 

In article <12595@star.cs.vu.nl > ast@cs.vu.nl (Andy Tanenbaum) writes:  
> While I could go into a long story here about the relative merits of the
> two designs, suffice it to say that among the people who actually design
> operating systems, the debate is essentially over. Microkernels have won. 

Can you recommend any (unbiased) literature that points out the strengths and weaknesses of the two approaches? I'm sure that there is something to be said for the microkernel approach, but I wonder how closely Minix resembles the other systems that use it. Sure, Minix uses lots of tasks and messages, but there must be more to a microkernel architecture than that. I suspect that the Minix code is not split optimally into tasks.

> The only real argument for monolithic systems was performance, and there
> is now enough evidence showing that microkernel systems can be just as
> fast as monolithic systems (e.g., Rick Rashid has published papers comparing
> Mach 3.0 to monolithic systems) that it is now all over but the shoutin`. 

My main complaint with Minix is not it's performance. It is that adding features is a royal pain -- something that I presume a microkernel architecure is supposed to alleviate.  
> MINIX is a microkernel-based system. 

Is there a consensus on this?

> LINUX is
> a monolithic style system. This is a giant step back into the 1970s.
> That is like taking an existing, working C program and rewriting it in
> BASIC. To me, writing a monolithic system in 1991 is a truly poor idea. 

This is a fine assertion, but I've yet to see any rationale for it. Linux is only about 12000 lines of code I think. I don't see how splitting that into tasks and blasting messages around would improve it.

>Don't get me wrong, I am not unhappy with LINUX. It will get all the people
>who want to turn MINIX in BSD UNIX off my back. But in all honesty, I would
>suggest that people who want a **MODERN** "free" OS look around for a
>microkernel-based, portable OS, like maybe GNU or something like that.

Well, there are no other choices that I'm aware of at the moment. But when GNU OS comes out, I'll very likely jump ship again. I sense that you *are* somewhat unhappy about Linux (and that surprises me somewhat). I would guess that the reason so many people embraced it, is because it offers more features. Your approach to people requesting features in Minix, has generally been to tell them that they didn't really want that feature anyway. I submit that the exodus in the direction of Linux proves you wrong. 

Disclaimer: I had nothing to do with Linux development. I just find it an easier system to understand than Minix.

Doug Graham dgraham@bnr.ca My opinions are my own.

{这个老兄认为minux不能算作是真正的微内核的OS,说明微内核的OS在实现上非常困难,实际上,早在1991年的环境下恰恰是微内核的OS的实现是不大可能有着像样的结果的 也提到了GNU OS并没有推出,而linux的诱惑在于提供了足够多的features}


{作者的link}


From: hedrick@klinzhai.rutgers.edu (Charles Hedrick)
Subject: Re: LINUX is obsolete
Date: 1 Feb 92 00:27:04 GMT
Organization: Rutgers Univ., New Brunswick, N.J.  

The history of software shows that availability wins out over technical quality every time. That's Linux' major advantage. It's a small 386-based system that's fairly compatible with generic Unix, and is freely available. I dropped out of the Minix community a couple of years ago when it became clear that (1) Minix was not going to take advantage of anything beyond the 8086 anytime in the near future, and (2) the licensing -- while amazingly friendly -- still made it hard for people who were interested in producing a 386 version. Several people apparently did nice work for the 386. But all they could distribute were diffs. This made bringing up a 386 system a job that isn't practical for a new user, and in fact I wasn't sure I wanted to do it.  

I apologize if things have changed in the last couple of years. If it's now possible to get a 386 version in a form that's ready to run, the community has developed a way to share Minix source, and bringing up normal Unix programs has become easier in the interim, then I'm willing to reconsider Minix. I do like its design.  

It's possible that Linux will be overtaken by Gnu or a free BSD. However, if the Gnu OS follows the example of all other Gnu software, it will require a system with 128MB of memory and a 1GB disk to use. There will still be room for a small system. My ideal OS would be 4.4 BSD. But 4.4's release date has a history of extreme slippage. With most of their staff moving to BSDI, it's hard to believe that this situation is going to be improved. For my own personal use, the BSDI system will probably be great. But even their very attractive pricing is likely to be too much for most of our students, and even though users can get source from them, the fact that some of it is proprietary will again mean that you can't just put altered code out for public FTP. At any rate, Linux exists, and the rest of these alternatives are vapor.

{第一句话开明综意,软件的可用性要比技术上的考量更重要,指出minux有两个劣势,第一是可用性,第二是许可证。虽然minux的设计他很喜欢。 linux其他竞争者GNU要求的资源太高,还是太雄心。BSD4.4陈旧,开发者流失,BSDI在价格和许可证上都有点问题}


{大名鼎鼎的Ts'o,linux kernel专家,fs专家,牛人都是牛,看看这封信的语气和口吻,此君也不是善茬}
From: tytso@athena.mit.edu (Theodore Y. Ts'o)
Subject: Re: LINUX is obsolete
Date: 31 Jan 92 21:40:23 GMT
Organization: Massachusetts Institute of Technology In-Reply-To: ast@cs.vu.nl's message of 29 Jan 92 12: 12:50 GMT


>From: ast@cs.vu.nl (Andy Tanenbaum)   
>ftp.cs.vu.nl = 192.31.231.42 in dir minix/simulator.) I think it is a >gross error to design an OS for any specific architecture, since that is
>not going to be around all that long.  

It's not your fault for believing that Linux is tied to the 80386 architecture, since many Linux supporters (including Linus himself) have made the this statement. However, the amount of 80386-specific code is probably not much more than what is in a Minix implementation, and there is certainly a lot less 80386 specific code in Linux than here is Vax-specific code in BSD 4.3. 

>...

认为Linux和80386架构是捆在一起,这不是你的错。太多人(包括Linus本人)都这样宣称过。{Linux}与80386架构相关的代码并不比Minux实现中要多,而且比起BSD4.3种和Vax架构相关的代码来说,{Linux}和80386相关的代码也肯定要少。

{一上来就拿code说事,表明了一个真正programmer的自豪感和不屑}

Granted, the port to other architectures hasn't been done yet. But if I were going to bring up a Unix-like system on a new architecture, I'd probably start with Linux rather than Minix, simply because I want to have some control over what I can do with the resulting system when I'm done with it. Yes, I'd have to rewrite large portions of the VM and device driver layers --- but I'd have to do that with any other OS. Maybe it would be a little bit harder than it would to port Minix to the new architecture; but this would probably be only true for the first architecture that we ported Linux to.  

虽然{Linux}向其他架构的移植尚未完成。如果要打算想要一个新的架构移植一个类Unix系统,我情愿从Linux而不是Minux开始,因为在做这个工作时,我简单的希望对这个系统有所控制。诚然,我必须重写很多VM和设备驱动---对于其他任何OS我也不得不这样做。也许比起Minux,移植到一个新的架构这要困难一点,但是这只发生在我们第一次移植Linux到一个新的架构时。 {坚持一种工程学观点,下面还有反映}
>While I could go into a long story here about the relative merits of the
>two designs, suffice it to say that among the people who actually design
>operating systems, the debate is essentially over. Microkernels have won.
>The only real argument for monolithic systems was performance, and there
>is now enough evidence showing that microkernel systems can be just as
>fast as monolithic systems (e.g., Rick Rashid has published papers comparing
>Mach 3.0 to monolithic systems) that it is now all over but the shoutin'.  

This is not necessarily the case; I think you're painting a much more black and white view of the universe than necessarily exists. I refer you to such papers as Brent Welsh's (welch@parc.xerox.com) "The Filsystem Belongs in the Kernel" paper, where in he argues that the filesystem is a mature enough abstraction that it should live in the kernel, not outside of it as it would in a strict microkernel design.

>...

这并不是必需的,我认为你这是一种实际上不必要的非白即黑的观点。我得向您指出这样一篇论文Brent Welsh's (welch@parc.xerox.com) "The Filsystem Belongs in the Kernel",论文中作者认为fs是一种足够成熟的抽象层,如果是一个严格的微内核设计,fs应该实现于内核之中,而不是其外。

{观念也许不重要...起码我不关心}

There also several people who have been concerned about the speed of OSF/1 Mach when compared with monolithic systems; in particular, the nubmer of context switches required to handle network traffic, and networked filesystems in particular.

还有一些人在把OSF/1 Mach与宏内核系统比较的时候,关注运行速度;特别是在网络文件系统上,在上下文切换时需要去面对更多网络处理。

I am aware of the benefits of a micro kernel approach. However, the fact remains that Linux is here, and GNU isn't --- and people have been working on Hurd for a lot longer than Linus has been working on Linux. Minix doesn't count because it's not free. :-)

我很清楚微内核方式的好处,但是现实是Linux就在这儿,而GNU不存在---在Hurd上的老兄比在Linux上的老兄工作的时间要更久。Minix不能位列其中,因为它甚至不是免费的:-)

I suspect that the balance of micro kernels versus monolithic kernels depend on what you're doing. If you're interested in doing research, it is obviously much easier to rip out and replace modules in a micro kernel, and since only researchers write papers about operating systems, ipso facto micro kernels must be the right approach. However, I do know a lot of people who are not researchers, but who are rather practical kernel programmers, who have a lot of concerns over the cost of copying and the cost of context switches which are incurred in a micro kernel.

我怀疑在微内核和宏内核系统之间存在一种平衡,取决于你要做什么。如果你兴趣在做研究上,在微内核系统上拿掉并替换掉一个模块显然要更容易,因为研究者只需要写写OS的论文,{在这种意义上}微内核是理论正确的。但是我知道这里很多人不是研究者,使一些更实际的程序员,比起拷贝的代价或者上下文切换的代价这些在微内核上需要关心的问题来,有很多其他的问题更值得关心。

{瞧瞧,这几段话写的,完全符合一个牛人在我心目中的形象啊,囧}

By the way, I don't buy your arguments that you don't need a multi-threaded filesystem on a single user system. Once you bring up a windowing system, and have a compile going in one window, a news reader in another window, and UUCP/C News going in the background, you want good filesystem performance, even on a single-user system. Maybe to a theorist it's an unnecessary optimization and a (to use your words) "performance hack", but I'm interested in a Real operating system --- not a research toy.

另外,我不是故意的说在一个单用户的系统上你就不需要多线程的fs。如果你打开一个窗口,另一个窗口中编译,在后代还有UUCP/C读新闻组,甚至在单用户系统上你也需要很好的fs性能。不过,也许在一个理论家的眼中者是不需要优化的或者(用你的话说)“性能hack”,但是我只对一个真正的OS感兴趣---而不是一个研究玩具。

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Theodore Ts'o bloom-beacon!mit-athena!tytso

308 High St., Medford, MA 02155 tytso@athena.mit.edu

Everybody's playing the game, but nobody's rules are the same!

{我觉得Tso也许是到目前为止的最挺Linux的一个,或者说是对ast持批评态度最激烈的一个,甚至Linus本人都没有Tso那么强烈

Tso不单言词犀利,而且观点鲜明,并且保持/强调了一个程序员的强烈自豪感}



From: joe@jshark.rn.com
Subject: Re: LINUX is obsolete
Date: 31 Jan 92 13:21:44 GMT
Organization: a blip of entropy 

In article <12595@star.cs.vu.nl
> ast@cs.vu.nl (Andy Tanenbaum) writes:
>
> MINIX was designed to be reasonably portable, and has been ported from the
> Intel line to the 680x0 (Atari, Amiga, Macintosh), SPARC, and NS32016.
> LINUX is tied fairly closely to the 80x86. Not the way to go. 

If you looked at the source instead of believing the author, you'd realise this is not true! 

He's replaced 'fubyte' by a routine which explicitly uses a segment register - but that could be easily changed. Similarly, apart from a couple of places which assume the '386 MMU, a couple of macros to hide the exact page sizes etc would make porting trivial. Using '386 TSS's makes the code simpler, but the VAX and WE32000 have similar structures. 

As he's already admitted, a bit of planning would have the the system neater, but merely putting '386 assembler around isn't a crime! 

And with all due respect:

- the Book didn't make an issue of portability (apart from a few "#ifdef M8088"s)

- by the time it was released, Minix had come to depend on several 8086 "features" that caused uproar from the 68000 users.  
>Andy Tanenbaum (ast@cs.vu.nl) 

joe.

{也是来bs Tanenbaum的,居然细扣到了代码的地步,虽然显得有些墙倒众人推的意思,但是代码这个最重要,最能说明问题的地方,minux看来是做得有些不够...

惨烈阿,到此为止的论战几乎是一种半场攻防演练...}



From: entropy@wintermute.WPI.EDU (Lawrence C. Foard)
Subject: Re: LINUX is obsolete
Date: 5 Feb 92 14:56:30 GMT
Organization: Worcester Polytechnic Institute 

In article <12595@star.cs.vu.nl
> ast@cs.vu.nl (Andy Tanenbaum) writes:
>Don`t get me wrong, I am not unhappy with LINUX. It will get all the people
>who want to turn MINIX in BSD UNIX off my back. But in all honesty, I would
>suggest that people who want a **MODERN** "free" OS look around for a
>microkernel-based, portable OS, like maybe GNU or something like that.    

I believe you have some valid points, although I am not sure that a microkernel is necessarily better. It might make more sense to allow some combination of the two. As part of the IPC code I'm writting for Linux I am going to include code that will allow device drivers and file systems to run as user processes. These will be significantly slower though, and I believe it would be a mistake to move everything outside the kernel (TCP/IP will be internal).    

Actually my main problem with OS theorists is that they have never tested there ideas! None of these ideas (with a partial exception for MACH) has ever seen the light of day. 32 bit home computers have been available for almost a decade and Linus was the first person to ever write a working OS for them that can be used without paying AT&T $100,000. A piece of software in hand is worth ten pieces of vaporware, OS theorists are quick to jump all over an OS but they are unwilling to ever provide an alternative.    

The general consensus that Micro kernels is the way to go means nothing when a real application has never even run on one.    

The release of Linux is allowing me to try some ideas I've been wanting to experment with for years, but I have never had the opportunity to work with source code for a functioning OS.  

{不出意料,又是反对Tanenbaum的人。 事态从Tso开始似乎有点失控,几乎上升到了人身攻击的地步,出现了一个名词,OS理论家。难怪下面ast要跳出来了...}


{ast第四次出现,有点愤怒,不过还好,还能开玩笑}

From: ast@cs.vu.nl (Andy Tanenbaum)
Subject: Re: LINUX is obsolete
Date: 5 Feb 92 23:33:23 GMT
Organization: Fac. Wiskunde & Informatica, Vrije Universiteit, Amsterdam 

In article <1992Feb5.145630.759@wpi.WPI.EDU > entropy@wintermute.WPI.EDU (Lawrence C. Foard) writes:
>Actually my main problem with OS theorists is that they have never tested
>there ideas!

I'm mortally insulted. I AM NOT A THEORIST. Ask anybody who was at our department meeting yesterday (in joke).  

>我认为OS理论家的主要问题是他们从来不去验证他们

>自己的想法。

我被严重冒犯了。我不是一个理论家。问问任何一个昨天参加我们系会议的人(开个玩笑)。

{这个笑话有点冷,大概得意思我猜Tanenbaum是说自己和那些正统教授不是一路人}

Actually, these ideas have been very well tested in practice. OSF is betting its whole business on a microkernel (Mach 3.0). USL is betting its business on another one (Chorus). Both of these run lots of software, and both have been extensively compared to monolithic systems. Amoeba has been fully implemented and tested for a number of applications. QNX is a microkernel based system, and someone just told me the installed base is 200,000 systems. Microkernels are not a pipe dream. They represent proven technology.  

事实上,这些观点在实践中都有很好的验证。OSF把他所有的事务都赌在微内核上(Mach 3.0),USL把赌注下在另一个上(Chorus)。这两个都有很多软件要运行,并且他们都对宏内核系统作了深入广泛地比较。Amoeba也快完成,并且很多应用都作过了测试。QNX是一个基于微内核的系统,有人告诉我装机量大约在200,000台。微内核不是白日梦,而是一种证明了的技术。

{摆出一些事实,对上面众多人等的质疑做出有力的反击}

The Mach guys wrote a paper called "UNIX as an application program." It was by Golub et al., in the Summer 1990 USENIX conference. The Chorus people also have a technical report on microkernel performance, and I coauthored another paper on the subject, which I mentioned yesterday (Dec. 1991 Computing Systems). Check them out.  

Andy Tanenbaum (ast@cs.vu.nl)

 

Mach的那些家伙们写了一篇论文,"UNIX as an application program." 由Golub等人完成,提交在1990年夏天的USENIX会议上。Chorus的那些人也有一个关于微内核性能的技术报告,我也和他人合作了一篇论文,就是我昨天提到的(1991/12,Computing Systems)请自行察看。

Andy Tanenbaum (ast@cs.vu.nl)



From: peter@ferranti.com (peter da silva)
Subject: Re: LINUX is obsolete
Organization: Xenix Support, FICC
Date: Thu, 6 Feb 1992 16:02:47 GMT 

In article <12747@star.cs.vu.nl
> ast@cs.vu.nl (Andy Tanenbaum) writes:
> QNX is a microkernel
> based system, and someone just told me the installed base is 200,000 systems.  

Oh yes, while I'm on the subject... there are over 3 million Amigas out there, which means that there are more of them than any UNIX vendor has shipped, and probably more than all UNIX systems combined.



From: peter@ferranti.com (peter da silva)
Subject: Re: LINUX is obsolete
Organization: Xenix Support, FICC
Date: Thu, 6 Feb 1992 16:00:22 GMT 

In article 1992Feb5.145630.759@wpi.WPI.EDU entropy@wintermute.WPI.EDU (Lawrence C. Foard) writes:
> Actually my main problem with OS theorists is that they have never tested
> there ideas!  

I beg to differ... there are many microkernel operating systems out there for everything from an 8088 (QNX) up to large research systems.  
> None of these ideas (with a partial exception for MACH) has ever
> seen the light of day. 32 bit home computers have been available for almost a
> decade and Linus was the first person to ever write a working OS for them
> that can be used without paying AT&T $100,000.  

I must have been imagining AmigaOS, then. I've been using a figment of my imagination for the past 6 years.  

AmigaOS is a microkernel message-passing design, with better response time and performance than any other readily available PC operating system: including MINIX, OS/2, Windows, MacOS, Linux, UNIX, and *certainly* MS-DOS.  

The microkernel design has proven invaluable. Things like new file systems that are normally available only from the vendor are hobbyist products on the Amiga. Device drivers are simply shared libraries and tasks with specific entry points and message ports. So are file systems, the window system, and so on. It's a WONDERFUL design, and validates everything that people have been saying about microkernels. Yes, it takes more work to get them off the ground than a coroutine based macrokernel like UNIX, but the versatility pays you back many times over.  

I really wish Andy would do a new MINIX based on what has been learned since the first release. The factoring of responsibilities in MINIX is fairly poor, but the basic concept is good.  
> The general consensus that Micro kernels is the way to go means nothing when
> a real application has never even run on one.  

I'm dreaming again. I sure throught Deluxe Paint, Sculpt 3d, Photon Paint, Manx C, Manx SDB, Perfect Sound, Videoscape 3d, and the other programs I bought for my Amiga were "real". I'll have to send the damn things back now, I guess.  

The availability of Linux is great. I'm delighted it exists. I'm sure that the macrokernel design is one reason it has been implemented so fast, and this is a valid reason to use macrokernels. BUT... this doesn't mean that microkernels are inherently slow, or simply research toys.

{难得的为Tanenbaum和微内核说几句公道话的人}



{mail作者的link} From: dsmythe@netcom.COM (Dave Smythe)
Subject: Re: LINUX is obsolete
Date: 10 Feb 92 07:08:22 GMT
Organization: Netcom - Online Communication Services (408 241-9760 guest)  In article 1992Feb5.145630.759@wpi.WPI.EDU entropy@wintermute.WPI.EDU (Lawrence C. Foard) writes:
>Actually my main problem with OS theorists is that they have never tested
>there ideas! None of these ideas (with a partial exception for MACH) has ever
>seen the light of day.

 

David Cheriton (Prof. at Stanford, and author of the V system) said something similar to this in a class in distributed systems. Paraphrased:

"There are two kinds of researchers: those that have implemented something and those that have not. The latter will tell you that there are 142 ways of doing things and that there isn't consensus on which is best. The former will simply tell you that 141 of them don't work."

He really rips on the OSI-philes as well, for a similar reason. The Internet protocols are adapted only after having been in use for a period of time, preventing things from getting standardized that will never be implementable in a reasonable fashion. OSI adherents, on the other hand, seem intent on standardizing everything possible, including "escapes" from the standard, before a reasonable reference implementation exists. Consequently, you see obsolete ideas immortalized, such as sub-byte-level data field packing, which makes good performance difficult when your computer is drinking from a 10+ Gbs fire-hose :-).

Just my $.02

D

{还有做俯卧撑的}



{Linus的第三次出现}

From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Apologies (was Re: LINUX is obsolete)
Date: 30 Jan 92 15:38:16 GMT
Organization: University of Helsinki

In article 1992Jan29.231426.20469@klaava.Helsinki.FI I wrote:
>Well, with a subject like this, I'm afraid I'll have to reply.

And reply I did, with complete abandon, and no thought for good taste and netiquette. Apologies to ast, and thanks to John Nall for a friendy "that's not how it's done"-letter. I over-reacted, and am now composing a (much less acerbic) personal letter to ast. Hope nobody was turned away from linux due to it being (a) possibly obsolete (I still think that's not the case, although some of the criticisms are valid) and (b) written by a hothead :-)

Linus "my first, and hopefully last flamefest" Torvalds

>...

我的确回应了,完全没有细想,没有顾及到好品味和网络礼节。向ast道歉,并感谢John Nall友善的来信---“这不是怎么完成它”。我有点反应过度了,而且正在给ast写一封(不那么尖刻的)私人信件。希望不要有人因为linux(a)可能过时(我仍然不那么认为,尽管一些批评是合理的)(b)是一个头脑冲动的家伙写的而放弃它:-)

Linus “我第一次,希望也是最后一次网络论争” Torvalds

{看到自己几乎大获全胜,Linus也准备收手了

不过他的签名...能说什么呢...

}



From: pmacdona@sanjuan (Peter MacDonald)
Subject: re: Linux is obsolete
Date: 1 Feb 92 02:10:06 GMT
Organization: University of Victoria, Victoria, BC, CANADA  

Since I think I posted one of the earliest messages in all this discussion of Minix vs Linux, I feel compelled to comment on my reasons for switching from Minix to Linux. In order of importance they are:

1) Linux is free

2) Linux is evolving at a satisfactory clip (because new features are accepted into the distribution by Linus).

The first requires some explanation, because if I have already purchased Minix, what posssible concern could price have for me? Simple. If the OS is free, many more people will use/support/enhance it. This is also the same reasoning I used when I bought my 386 instead of a sparc (which I could have got for just 30% more). Since PCs are cheap and generally available, more people will buy/use them and thus good, cheap/free software will be abundant.

The second should be pretty obvious to anyone who has been using Minix for for any period of time. AST generally does not accept enhancements to Minix. This is not meant as a challenge, but merely a statement of fact. AST has good and legitimate reasons for this, and I do not dispute them. But Minix has some limitations which I just could no longer live with, and due to this policy, the prospect of seeing them resolved in reasonable time was unsatisfactory. These limitations include:

no 386 support

no virtual consoles

no soft links

no select call

no ptys

no demand paging/swapping/shared-text/shared-libs... (efficient mm) chmem (inflexible mm)

no X-Windows (advocated for the same reasons as Linux and the 386).

no TCP/IP no GNU/SysV integration (portability)

Some of these could be fixed by patches (and if you have done this yourself, I don't have to tell you how satisfactory that is), but at least the last 5 items were/are beyond any reasonable expectation.

Finally, my comment (crack?) about Minix's segmented kernel, or micro-kernel architecture was more an expression of my frustration/ bewilderment at attempting to use the Minix PTY patches as a guide of how to do it under Linux. That particular instance was one where message passing greatly complicated the implementation of a feature.

I do have an opinion about Monlithic vs Message Passing, but won't express it now, and did not mean to expresss it then. My goals are totally short term (maximum functionality in the minimum amount of time/cost/hassle), and so my views on this are irrelevant, and should not be misconstrued. If you are non-plussed by the lack of the above features, then you should consider Minix, as long as you don't mind paying of course :)

{Linus想收手,可惜如此口水的话题不会就此甘休的

这个老兄继续打击minux,两点,第一minux不免费,第二指出minux对开发者不友好,前面有人小心翼翼的提到过这个问题了,就是许可证的问题

}



From: olaf@oski.toppoint.de (Olaf Schlueter)
Subject: Re: Linux is obsolete
Date: 7 Feb 92 11:41:44 GMT
Organization: Toppoint Mailbox e.V.

Just a few comments to the discussion of Linux vs Minix, which evolved partly to a discussion of monolithic vs micro-kernel.

I think there will be no aggreement between the two parties advocating either concept, if they forget, that Linux and Minix have been designed for different applications. If you want a cheap, powerful and enhancable Unix system running on a single machine, with the possibility to adapt standard Unix software without pain, then Linux is for you. If you are interested in modern operating system concepts, and want to learn how a microkernel based system works, then Minix is the better choice.

It is not an argument against microkernel system, that for the time being monolithic implemenations of Unix on PCs have a better performance. This means only, that Unix is maybe better implemented as a monolithic OS, at least as long as it runs on a single machine. From the users point of view, the internal design of the OS doesn't matter at all. Until it comes to networks. On the monolithic approach, a file server will become a user process based on some hardware facility like ethernet. Programs which want to use this facility will have to use special libraries which offer the calls for communication with this server. In a microkernel system it is possible to incorporate the server into the OS without the need for new "system" calls. From the users point of view this has the advantage, that nothing changes, he just gets better performance (in terms of more disk space for example). From the implementors point of view, the microkernel system is faster adaptable to changes in hardware design.

It has been critized, that AST rejects any improvements to Minix. As he is interested in the educational value of Minix, I understand his argument, that he wants to keep the code simple, and don't want to overload it with features. As an educational tool, Minix is written as a microkernel system, although it is running on hardware platforms, who will probably better perform with a monolithic OS. But the area of network applications is growing and modern OS like Amoeba or Plan 9 cannot be written as monolithic systems. So Minix has been written with the intention to give students a practical example of a microkernel OS, to let them play with tasks and messages. It was not the idea to give a lot of people a cheap, powerful OS for a tenth of the price of SYSV or BSD implementations.

Resumee: Linux is not better than Minix, or the other way round. They are different for good reasons.

{来和稀泥的,发表了一些自己的看法,这种观点看起来中庸,但是近似于扯淡。

不过但是说出了minix的用途,教学工具,ast无意使它过于复杂,没有什么雄心,没有看到在minix的周围,由于PC革命的开始,已经聚集了一些真实的用户,这也是前面一再提到的许可证的问题根源。

}



{此人也是开源社区的老大,SAX的leader}

From: meggin@epas.utoronto.ca (David Megginson)
Subject: Mach/Minix/Linux/Gnu etc.
Date: 1 Feb 92 17:11:03 GMT
Organization: University of Toronto - EPAS 

Well, this has been a fun discussion. I am absolutely convinced by Prof. Tanenbaum that a micro-kernel _is_ the way to go, but the more I look at the Minix source, the less I believe that it is a micro-kernel. I would probably not bother porting Linux to the M68000, but I want more services than Minix can offer. 

What about a micro-kernel which is message/syscall compatible with MACH? It doesn't actually have to do everything that MACH does, like virtual memory paging -- it just has to _look_ like MACH from the outside, to fool programs like the future Gnu Unix-emulator, BSD, etc. This would extend the useful lives of our M68000- or 80286-based machines for a little longer. In the meantime, I will probably stay with Minix for my ST rather than switching back to MiNT -- after all, Minix at least looks like Unix, while MiNT looks like TOS trying to look like Unix (it has to, to be TOS compatible). 

David

{支持微内核,但是也指出minix在代码上的不足,又表示要继续使用minix

}



From: peter@ferranti.com (peter da silva) Newsgroups: comp.os.minix
Subject: What good does this war do? (Re: LINUX is obsolete)
Date: 3 Feb 92 16:37:24 GMT
Organization: Xenix Support, FICC  

Will you quit flaming each other? 

I mean, linux is designed to provide a reasonably high performance environment on a hardware platform crippled by years of backwards-compatible kludges. Minix is designed as a teaching tool. Neither is that good at doing the other's job, and why should they? The fact that Minix runs out of steam quickly (and it does) isn't a problem in its chosen mileau. It's sure better than the TOY operating system. The fact that Linux isn't transportable beyond the 386/AT platform isn't a problem when there are millions of them out there (and quite cheap: you can get a 386/SX for well under $1000). 

A monolithic kernel is easy enough to build that it's worth doing it if it gets a system out the door early. Think of it as a performance hack for programmer time. The API is portable. You can replace the kernel with a microkernel design (and MINIX isn't the be-all and end-all of microkernel designs either: even for low end PCs... look at AmigaOS) without disturbing the applications. That's the whole point of a portable API in the first place. 

Microkernels are definitely a better design for many tasks. I takes more work to make them efficient, so a simpler design that doesn't take advantage of the microkernel in any real way is worth doing for pedagogical reasons. Think of it as a performance hack for student time. The design is still good and when you can get an API to the microkernel interface you can get VERY impressive performance (thousands of context switches per second on an 8 MHz 68000).



{ast第五次,愤怒了}

From: ast@cs.vu.nl (Andy Tanenbaum)
Subject: Unhappy campers
Date: 3 Feb 92 22:46:40 GMT
Organization: Fac. Wiskunde & Informatica, Vrije Universiteit, Amsterdam 

I've been getting a bit of mail lately from unhappy campers. (Actually 10 messages from the 43,000 readers may seem like a lot, but it is not really.) There seem to be three sticking points: 

1. Monolithic kernels are just as good as microkernels

2. Portability isn't so important

3. Software ought to be free 

我已经从一些不高兴的社区参与者中得到了一些邮件(实际上从43,000名读者中10条消息看起来有点多,但这不是真的)。看起来有三个关键点:

1. 宏内核和微内核一样好

2. 可移植性不那么重要

3. 软件应该免费/自由

{第三点才是重点}

If people want to have a serious discussion of microkernels vs. monolithic kernels, fine. We can do that in comp.os.research. But please don't sound off if you have no idea of what you are talking about. I have helped design and implement 3 operating systems, one monolithic and two micro, and have studied many others in detail. Many of the arguments offered are nonstarters (e.g., microkernels are no good because you can't do paging in user space-- except that Mach DOES do paging in user space). 

如果大家想认真的讨论微内核vs.宏内核,那好,我们可以去comp.os.research。但是如果你们对讨论的东西没什么概念,你们就不能明确的说出什么。我曾经帮助设计和实现了三个OS,一个宏内核和两个微内核的,并且仔细研究了很多其他的OS。很多的争议都是没意义的(比如,微内核是不好的因为在用户空间上不能作paging--除了Mach已经在用户空间上作了paging以外)

If you don't know much about microkernels vs. monolithic kernels, there is some useful information in a paper I coauthored with Fred Douglis, Frans Kaashoek and John Ousterhout in the Dec. 1991 issue of COMPUTING SYSTEMS, the USENIX journal). If you don't have that journal, you can FTP the paper from ftp.cs.vu.nl (192.31.231.42) in directory amoeba/papers as comp_sys.tex.Z (compressed TeX source) or comp_sys.ps.Z (compressed PostScript). The paper gives actual performance measurements and supports Rick Rashid's conclusion that microkernel based systems are just as efficient as monolithic kernels. 

如果你对微内核vs.宏内核不那么了解,这儿有一篇我和Fred Douglis, Frans Kaashoek and John Ousterhout和写的,发表在1991年的USENIX期刊上的论文COMPUTING SYSTEMS。如果你没有这本杂志,你可以FTP到ftp.cs.vu.nl (192.31.231.42),目录amoeba/papers 有一个comp_sys.tex.Z(压缩过的TeX的源)或者comp_sys.ps.Z (以PostScript压缩)。这篇论文给出了确切的性能衡量,支持了Rick Rashid的结论:基于微内核的系统比宏内核系统要更加有效。

{讨论第一点,还是不能拿代码说事,还是有点学霸的面孔}

As to portability, there is hardly any serious discussion possible any more. UNIX has been ported to everything from PCs to Crays. Writing a portable OS is not much harder than a nonportable one, and all systems should be written with portability in mind these days. Surely Linus' OS professor pointed this out. Making OS code portable is not something I invented in 1987. 

至于说到可移植性,不再需要认真的谈论了。UNIX已经被移植到了从PC到Crays的任何机器上。写一个可移植的OS并不比不可移植的OS难多少,而且所有系统在未开始之前,脑海中首先就要考虑移植性的问题。很显然Linus's OS教授先生已经指出了这一点。让OS的代码具备一致性并不是什么我在1987年才发明的东西。

{不得不说,老先生还是很让人尊敬的,老派的绅士风度}

While most people can talk rationally about kernel design and portability, the issue of free-ness is 100% emotional. You wouldn't believe how much [expletive deleted] I have gotten lately about MINIX not being free. MINIX costs $169, but the license allows making two backup copies, so the effective price can be under $60. Furthermore, professors may make UNLIMITED copies for their students. Coherent is $99. FSF charges
>$100 for the tape its "free" software comes on if you don't have Internet access, and I have never heard anyone complain. 4.4 BSD is $800. I don't really believe money is the issue. Besides, probably most of the people reading this group already have it. 

然而大多数人在讨论内核设计和移植性的时候还算理性,但是涉及到免费/自由时却是100%的情绪化表现了。你不会相信近来在MINIX不是免费/自由这个问题上我收到了多少[咒骂省略]。MINIX价值$169,但是许可证允许两个备份的拷贝,所以实际价格在$60以下。更重要是,教授们用于学生的拷贝时无限制的,统一都是$99,FSF对于那些不能访问Internet的用户为自己“免费的”软件磁带要价是>$100,对此我没有听到过任何抱怨。4.4 BSD要价$800。我真的不认为钱是重要的问题。除此之外,可能大多数阅读这个新闻组的人都已经有了{MINIX?}

{提什么别提钱啊,千万别提钱。

老头急了,真的急了

}

A point which I don't think everyone appreciates is that making something available by FTP is not necessarily the way to provide the widest distribution. The Internet is still a highly elite group. Most computer users are NOT on it. It is my understanding from PH that the country where MINIX is most widely used is Germany, not the U.S., mostly because one of the (commercial) German computer magazines has been actively pushing it. MINIX is also widely used in Eastern Europe, Japan, Israel, South America, etc. Most of these people would never have gotten it if there hadn't been a company selling it. 

我不认为所有的人都赞赏的一点是,通过FTP方式提供最广泛的分发不是必然的方式。Internet仍然是一个相当精英的团体。大多数的计算机用户不在上面。如果我从PH{??,patch,补丁??}中得到的理解不错的话,MINIX在在各个国家中,以德国使用的最广泛,而不是美国。主要的原因可能使一家德国的(商业)计算机杂志曾经卖力的推广过它。MINIX在东欧,日本,以色列,南非等等国家使用的都不是很广泛。如果没有一家公司来卖它的话,那么它也就不可能为大多数人得到。

{ast宣称MINIX除了在德国,根本就没有做过MINIX的商业活动,也就是说他本人无意于此。

而且指出FSF有挂羊头之嫌,这个不好说什么,似乎在1990年不大明朗的时候,还是有点暗流的。当然事后的发展证明一个口号,一个信念还是颇有鼓舞人心的功效的。

随便可以看看在1990年左右发达的计算机国家有哪些:)

}

Getting back to what "free" means, what about free source code? Coherent is binary only, but MINIX has source code, just as LINUX does. You can change it any way you want, and post the changes here. People have been doing that for 5 years without problems. I have been giving free updates for years, too. 

回到自由意味着什么这个议题,那么源代码呢?{抱歉}只有二进制文件奉送。不过MINIX是带源代码的,就像LINUX那样。你可以按照你想的任何方式更改代码,然后在这里公布更改的内容。人们已经这样工作了5年,没有任何问题。我也好多年持续的给出了免费的更新。

{很可能FSF在1990年的做法,或者说目的值得怀疑}

I think the real issue is something else. I've been repeatedly offered virtual memory, paging, symbolic links, window systems, and all manner of features. I have usually declined because I am still trying to keep the system simple enough for students to understand. You can put all this stuff in your version, but I won't put it in mine. I think it is this point which irks the people who say "MINIX is not free," not the $60. 

我认为真正的问题不在这里。我多次提交了诸如VM,分页,符号链接,窗口系统,以及各种features。我通常的倾向因为我尽量试图保持系统的简单性,以便学生的理解。你可以把所有这些都整合到你的版本之中,但是我不会把它们放到我的版本之中。我认为这才是那些说“MINIX不是免费的”苦恼的原因,而不是$60。

{还是要说MINIX的雄心不够,或者ast没有看到PC革命带来的契机和巨大需求。

}

An interesting question is whether Linus is willing to let LINUX become "free" of his control. May people modify it (ruin it?) and sell it? Remember the hundreds of messages with subject "Re: Your software sold for money" when it was discovered the MINIX Centre in England was selling diskettes with news postings, more or less at cost? 

一个有趣的问题是Linus是否准备让LINUX自他的控制中“自由”出来。人们可以修改(毁掉)它吗?记住上百条的消息是这样的主题“Re:你的软件为钱出售”,它表明在英格兰的MINIX中心在卖磁带的同时,也附带着新闻跟新,这也或多或少值点钱吧?

Suppose Fred van Kempen returns from the dead and wants to take over, creating Fred's LINUX and Linus' LINUX, both useful but different. Is that ok? The test comes when a sizable group of people want to evolve LINUX in a way Linus does not want. Until that actually happens the point is moot, however.

假定Fred van Kempen复活{这个老兄好像没有挂啊}并且准备拿到控制权,创造一个Fred版的LINUX和Linus版的LINUX,这两个都有用但是互不相同。这样OK吗?当有一票人希望参与LINUX的发展,但是不是按照Linus自己希望的方式,这个假定就会变成现实。虽然在这一切没有发生的时候是没有意义的。

{这一段的指责很有力,看看现在有多少linux的发行版吧...

不过内核的开发还是在有序之下开发的。Linus真的是一个强有力的社区领导。

}

If you like Linus' philosophy rather than mine, by all means, follow him, but please don't claim that you're doing this because LINUX is "free." Just say that you want a system with lots of bells and whistles. Fine. Your choice. I have no argument with that. Just tell the truth. 

如过你喜欢Linus的而不是我的哲学,尽力跟随他,但请不要声称你是因为LINUX是“自由/免费”而这样做的。只需说你需要一个花哨的系统。很好,你自己的选择。我对此毫无意见。只要说出事实。

{应用为王啊,花哨就是说可用的东西多。ast还是没有搞清楚迎合用户才是重要的,而不是研究教学。特别是在微内核还是一个概念产品的情形下。

}

As an aside, for those folks who don't read news headers, Linus is in Finland and I am in The Netherlands. Are we reaching a situation where another critical industry, free software, that had been totally dominated by the U.S. is being taken over by the foreign competition? Will we soon see President Bush coming to Europe with Richard Stallman and Rick Rashid in tow, demanding that Europe import more American free software? 

Andy Tanenbaum (ast@cs.vu.nl)

顺便说一句,那些没有读新闻邮件头的人,Linus是芬兰的,我是荷兰的。在自由软件美国长期霸占的的关键产业,是否进入到一种被他国竞争者抢占了地位的情形下吗?我们是不是很快会看到Bush总统带着Richard Stallman,Rich Rashid座着拖车来到欧洲,恳求欧洲输入更多美国的自由软件呢?

Andy Tanenbaum (ast@cs.vu.nl)

{

发泄完了,ast又恢复了派头,依然尖酸的讲着冷笑话。虽然事实会让他大跌眼镜。

U.S.当然还是无可争议的no.1但是Linus却无人不识了

}


{ast第六次,意犹未尽,马上又跳出来了...}
From: ast@cs.vu.nl (Andy Tanenbaum)
Subject: Re: Unhappy campers
Date: 5 Feb 92 23:23:26 GMT
Organization: Fac. Wiskunde & Informatica, Vrije Universiteit, Amsterdam

 

In article 205@fishpond.uucp fnf@fishpond.uucp (Fred Fish) writes:
>If PH was not granted a monopoly on distribution, it would have been possible
>for all of the interested minix hackers to organize and set up a group that
>was dedicated to producing enhanced-minix. This aim of this group could have
>been to produce a single, supported version of minix with all of the commonly
>requested enhancements. This would have allowed minix to evolve in much the
>same way that gcc has evolved over the last few years.

This IS possible. If a group of people wants to do this, that is fine. I think co-ordinating 1000 prima donnas living all over the world will be as easy as herding cats, but there is no legal problem. When a new release is ready, just make a diff listing against 1.5 and post it or make it FTPable. While this will require some work on the part of the users to install it, it isn't that much work. Besides, I have shell scripts to make the diffs and install them. This is what Fred van Kempen was doing. What he did wrong was insist on the right to publish the new version, rather than diffs against the PH baseline. That cuts PH out of the loop, which, not surprisingly, they weren't wild about.     If people still want to do this, go ahead. 

这的确是可能的。如果有些人希望这么做,很好。我个人认为让散布在世界各地的1000个主角一起合作就像放养猫那么简单,但是不存在合不合法的问题。当一个新版本就绪以后,只需要作一个diff列表{??},然后把它贴出来或者能够通过FTP得到。不过这需要用户花点功夫安装软件,这不是什么大不了的事。别急,我还有一个shell脚本制作这些diff补丁并且能自动安装。这正是Fred van Kempen做的事。坚持拥有发布新版本的权利上,而不是与PH基线作比较,产生diff补丁这件事上,他做错了。这把PH从循环中去掉了,这毫不惊奇,因为他们对此毫无兴趣。   如果你们还想这么做,没问题。

Of course, I am not necessarily going to put any of these changes in my version, so there is some work keeping the official and enhanced ones in sync, but I am willing to co-operate to minimize work. I did this for a long time with Bruce Evans and Frans Meulenbroeks. 

当然,我完全没有必要把任何这些改变放到我的版本中来,在保持官方版本和增强版本之间,会有一些同步工作要做,不过我很愿意积极合作,以最小化工作量。我和Bruce Evans以及Frans Meulenbroeks已经很长一段时间这样工作了。

If Linus wants to keep control of the official version, and a group of eager beavers want to go off in a different direction, the same problem arises. I don't think the copyright issue is really the problem. The problem is co-ordinating things. Projects like GNU, MINIX, or LINUX only hold together if one person is in charge. During the 1970s, when structured programming was introduced, Harlan Mills pointed out that the programming team should be organized like a surgical team--one surgeon and his or her assistants, not like a hog butchering team--give everybody an axe and let them chop away. 

如果Linus想保持控制官方版本,而一群热心人却想向另一个方向发展,相同的问题就会出现了。我不认为版权问题是一个真正的问题。问题是合作。诸如GNU,MINIX,LINUX这样的项目只有当一个人领导时才能很好的团结在一起。在1970年代,结构化编程被引入的时候,Harlan Mills指出编程团队应该像一个外科手术团队那样去组织——一个主治医师以其助手,那不是像屠猪的团队——每个人都有一把斧头,各自劈杀。

{ast的确指出了OSS社区的普遍问题,但是很可惜,在只认代码的社区,他没有看到自己和Linus的差别所在。还有热情。

也许Linux社区的成功正是因为Linus本人的才能。

}

Anyone who says you can have a lot of widely dispersed people hack away on a complicated piece of code and avoid total anarchy has never managed a software project. 

任何宣称能够避免在很多人修改一块复杂的代码的所产生的混乱,那么他肯定没有管理过一个软件项目。

>Where is the sizeable group of people that want to evolve gcc in a way that
>rms/FSF does not approve of?

A compiler is not something people have much emotional attachment to. If the language to be compiled is a given (e.g., an ANSI standard), there isn't much room for people to invent new features. An operating system has unlimited opportunity for people to implement their own favorite features. 

Andy Tanenbaum (ast@cs.vu.nl)

>…

编译器不允许人们附带感情色彩。如果一个语言需要编译(例如,一个ANSI的标准),没有太多的空间让人们发明什么新特性。但是OS却有无限的空间来让人们实现他们自己喜欢的features。

Andy Tanenbaum (ast@cs.vu.nl)

{这是一个无力的反击。很容易引起口水。}

 


{Torvalds第四次}

From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Re: Unhappy campers
Date: 6 Feb 92 10:33:31 GMT
Organization: University of Helsinki

In article <12746@star.cs.vu.nl
> ast@cs.vu.nl (Andy Tanenbaum) writes:
>>If Linus wants to keep control of the official version, and a group of eager
>beavers want to go off in a different direction, the same problem arises. 

This is the second time I've seen this "accusation" from ast, who feels pretty good about commenting on a kernel he probably haven't even seen. Or at least he hasn't asked me, or even read alt.os.linux about this. Just so that nobody takes his guess for the full thruth, here's my standing on "keeping control", in 2 words (three?): 

I won't. 

已经第二次了,我看到了来自ast的这个“指控”,对于一个他可能从未见过的内核加以评论,他的感觉相当不错。至少他没有问过我,甚至没有读过alt.os.linux上面的相关内容。当然不会有人把他的猜测当作真相,这是我对于“保持控制”的立场,俩个字(还是三个?)

我不会。

The only control I've effectively been keeping on linux is that I know it better than anybody else, and I've made my changes available to ftp-sites etc. Those have become effectively official releases, and I don't expect this to change for some time: not because I feel I have some moral right to it, but because I haven't heard too many complaints, and it will be a couple of months before I expect to find people who have the same "feel" for what happens in the kernel. (Well, maybe people are getting there: tytso certainly made some heavy changes even to 0.10, and others have hacked it as well) 

唯一的控制是我一直让linux有效的发展,我知道我比其他任何人做的要好,并且我把我的更改发布到ftp站点上。这些造就了高效的官方版本,我期望在一段时间内不要改变这种模式:不是因为我觉得自己有天然的权利这样做,而是因为我听到了太多的抱怨,对于在内核上正在发生什么,几个月前我就期望找到有相同“感受”的人。(那好吧,也许那个人就在这儿:tytso甚至对0.10就作出了一些重大的改进,还有其他几个人也作出了贡献)

In fact I have sent out feelers about some "linux-kernel" mailing list which would make the decisions about releases, as I expect I cannot fully support all the features that will /have/ to be added: SCSI etc, that I don't have the hardware for. The response has been non-existant: people don't seem to be that eager to change yet. (well, one person felt I should ask around for donations so that I could support it - and if anybody has interesting hardware lying around, I'd be happy to accept it :)

事实上,我在“linux内核”的邮件列表发过一些试探性的邮件,关于发布的版本需要做的决定,比如那些本/应该/被添加的features,例如:SCSI等等,因为我没有相应的硬件。正如我期望的,我没有得到完全支持。回应好像没有:人们看起来还不急于改变。(那好,有人觉得我应该寻求支援,这样我就能支持这些特性 - 如果有人对底层硬件非常有兴趣,我很乐意接受它:)

The only thing the copyright forbids (and I feel this is eminently reasonable) is that other people start making money off it, and don't make source available etc... This may not be a question of logic, but I'd feel very bad if someone could just sell my work for money, when I made it available expressly so that people could play around with a personal project. I think most people see my point. 

版权禁止的唯一一件事(我觉得这合乎情理)是其他人通过它来牟利,并且不提供源代码等等…这在逻辑上不是个问题,如果有人通过买我的作品来赚钱的话我会感觉很不爽,我只会让它直接可用以便人们能够工作在一个个人项目上。我认为大多数人已经了解我的观点。

That aside, if Fred van Kempen wanted to make a super-linux, he's quite wellcome. He won't be able to make much money on it (distribution fee only), and I don't think it's that good an idea to split linux up, but I wouldn't want to stop him even if the copyright let me.

另外,如果 Fred van Kempe想做一个super-linux,他将会得到欢迎。他不需要在这上面花费很多(只需要分发费) ,虽然我不认为把分裂linux是个好主意,但我不会阻止他,即使版权允许我那样做。

>I don't think the copyright issue is really the problem. The problem is >co-ordinating things. Projects like GNU, MINIX, or LINUX only hold together
>if one person is in charge. 

Yes, coordination is a big problem, and I don't think linux will move away from me as "head surgeon" for some time, partly because most people understand about these problems. But copyright /is/ an issue: if people feel I do a bad job, they can do it themselves. Likewise with gcc. The minix copyright, however, means that if someone feels he could make a better minix, he either has to make patches (which aren't that great whatever you say about them) or start off from scratch (and be attacked because you have other ideals). 

>…

的确,协作是个大问题,不过我认为,一段时间内,我不会远离linux“主治医师”这个角色的,部分是因为大多数人都意识到了这一点。不过版权也/是/一个问题:如果大家认为我的工作做得不好,他们可以自己干。同样的,使用gcc。而minix的版权意味着如果有人认为自己可以制作一个更好的minix,他要么制作补丁(不管怎么说,总不那么大好)要么重头开始(由于你有其他的理念而被攻击)。

Patches aren't much fun to distribute: I haven't made cdiffs for a single version of linux yet (I expect this to change: soon the patches will be so much smaller than the kernel that making both patches and a complete version available is a good idea - note that I'd still make the whole version available too). Patches upon patches are simply impractical, especially for people that may do changes themselves. 

分发补丁不是那么有趣的:我从未为单一版本的linux制作过cdiffs(我期望变成这样:很快补丁将会大大小于内核,这样,同时提供补丁和一个完全版的就会是使一个不错的主意 - 注意我仍然保持了完整版本可用)。补丁摞补丁是不切实际的,特别是对那些需要自己去做这件事的时候。

{用户体验啊…}


>>Where is the sizeable group of people that want to evolve gcc in a way that >>rms/FSF does not approve of?
>A compiler is not something people have much emotional attachment to. If
>the language to be compiled is a given (e.g., an ANSI standard), there isn't
>much room for people to invent new features. An operating system has unlimited
>opportunity for people to implement their own favorite features.

Well, there's GNU emacs... Don't tell us people haven't got emotional attachment to editors :) 

 

Linus

>…

那好吧,还有GNU emacs…别告诉我对于编辑器人们没有感情倾向:)

Linus

{这封mail是Linus对ast的一些反驳,可以看出来OSS本身也有其固然的一些问题,不过我以为这都不是重点了…

}

 



From: dmiller@acg.uucp (David Miller)
Subject: Linux is Obsolete and follow up postings
Date: 3 Feb 92 01:03:46 GMT
Organization: AppliedComputerGroup  

As an observer interested in operating system design, I couldn't resist this thread. Please realize that I am not really experienced with minux or linux: I have been into unix for many years. First, a few observations:  

Minix was written to be an educational tool for ASTs' classes, not a commercial operating system. It was never a design parameter to have it run freely available source code for unix systems. I think it was also a statement of how operating systems should be designed, with a micro kernel and seperate processes covering as much of the required functionality as possible.  

Linux was written mostly as a learning exercise on Linus part - how to program the 386 family. Designing the ultimate operating system was not an objective. Providing a usable, free platform that would run all sorts of widely available free software was a consideration, and one that appears to have been well met.  

Criticism from anyone that either of these systems isn't what *they* would like it to be is misplaced. After all, anybody that has a computer that will run either system is free to do what Linus and Andrew did: write your own!  

I, for one, applaud Linus for his considerable effort in developing Linux and his decision to make it free to everybody. I applaud AST for his effort to make minix affordable - I have real trouble relating to complaints that minix isn't free. If you can afford the time to explore minix, and a basic computer system, $150 is not much more - and you do get a book to go with it.  

Next, a few questions for the professor:  

Is minix supposed to be a "real operating system" or an educational tool ? As an educational tool it is an excellent work. As a real operating system it presents some terribly rough edges (why no malloc() ?, just for starters) My feeling from reading The Book and listening to postings here is that you wanted a tool to teach your classes, and a lot of others wanted to play with an affordable operating system. These others have been trying to bolt on enough features to make it a "real operating system", with less than outstanding success.  

Why split fundemental os functions, such as memory management, into user processes? As all good *nix gurus know, the means to success is to divide and conquer, with the goal being to *simplify* the problem into managable, well defined components. If splitting basic parts of the operating system into user space processes complicates the function by introducing additional mechanisms (message passing, complicated signals), have we met the objective of simplifying the design and implementation?   I agree that *nix has suffered a bad case of feature-itis - especially sysVr4. Perhaps the features that people want for either functionality or compatibility could be offered by run-time loadable modules/libraries that offer these features. The micro-kernel would still be a base-level resource manager that also routes function requests to the appropriate module/library. The modules could be threads or user processes. (I think - os hackers please correct me :-) )  

Just my $.04 worth - please feel free to post or email responses. I have no formal progressive training in computer science, so I am really asking these questions in ignorance. I suspect a lot of others on the net have similar questions in their own minds, but I've been wrong before.  

 

-- David



From: michael@gandalf.informatik.rwth-aachen.de (Michael Haardt)
Subject: 1.6.17 summary and why I think AST is right.
Date: 6 Feb 92 20:07:25 GMT Reply-To: u31b3hs@messua.informatik.rwth-aachen.de (Michael Haardt)
Organization: Gandalf - a 386-20 machine  

 

I will first give a summary of what you can expect from MINIX in *near* future, and then explain why I think AST is right. 

Some time ago, I asked for details about the next MINIX release (1.6.17). I got some response, but only from people running 1.6.16. The following informations are not official and may be wrong, but they are all I know at the moment. Correct me if something is wrong: 

- The 1.6.17 patches will be relative to 1.5 as shipped by PH. 

- The header files are clean. 

- The two types of filesystems can be used together. 

- The signal handling is rewritten for POSIX. The old bug is removed. 

- The ANSI compiler (available from Transmediar, I guess) comes with compiler binaries and new libraries. 

- There don't seem to be support for the Amoeba network protocol. 

- times(2) returns a correct value. termios(2) is implemented, but it's more a hack. I don't know if "implemented" means in the kernel, or the current emulation. 

- There is no documentation about the new filesystem. There is a new fsck and a new mkfs, don't know about de. 

- With the ANSI compiler, there is better floating point support. 

- The scheduler is improved, but not as good as written by Kai-Uwe Bloem. 

I asked these things to get facts for the decision if I should upgrade to MINIX 1.6.17 or to Linux after the examens are over. Well, the decision is made: I will upgrade to Linux at the end of the month and remove MINIX from my winchester, when Linux runs all the software I need and which currently runs under MINIX 1.5 with heavy patches. I guess this may take up to two months. These are the main reasons for my decision: 

- There is no "current" MINIX release, which can be used as basis for patches and nobody knows, when 1.6.17 will appear. 

- The library contains several bugs and from what I have heard, there is no work done at them. There will not be a new compiler, and the 16 bit users still have to use buggy ACK. 

- 1.6.17 should offer more POSIX, but a complete termios is still missing. 

- I doubt that there is still much development for 16 bit users. 

I think I will stop maintaining the MINIX software list in a few months. Anyone out there, who would like to continue it? Until Linux runs *perfect* on my machine, each update of Origami will still run on 16-bit MINIX. I will announce when the last of these versions appears. 

In my opinion, AST is right in his decision about MINIX. I read the flame war and can't resist to say that I like MINIX the way it is, now where there is Linux. MINIX has some advantages: 

- You can start playing with it without a winchester, you can even compile programs. I did this a few years ago. 

- It is so small, you don't need to know much to get a small system which runs ok. 

- There is the book. Ok, only for version 1.3, but most of it is still valid. 

- MINIX is an example of a non-monolithic kernel. Call it a microkernel or a hack to overcome braindamaged hardware: It demonstrates a concept, with its pros and cons -- a documented concept. 

In my eyes, it is a nice system for first steps in UNIX and systems programming. I learned most of what I know about UNIX with MINIX, in all areas, from programming in C under UNIX to system administration (and security holes:) MINIX grew with me: 1.5.xx upgrades, virtual consoles, mail & news, text processing, crosscompiling etc. Now it is too small for me. I don't need a teaching system anymore, I would like to get a more complicated and featureful UNIX, and there is one: Linux. 

Back in the old days, v7 was state of the art. There was MINIX which offered most of it. In one or two years, POSIX is what you are used to see. Hopefully, there will be MINIX, offering most of it, with a new book, for people who want to run a small system to play and experiment with. 

Stop flaming, MINIX and Linux are two different systems with different purposes. One is a teaching tool (and a good one I think), the other is real UNIX for real hackers. 

Michael



From: dingbat@diku.dk (Niels Skov Olsen)
Subject: Re: 1.6.17 summary and why I think AST is right.
Date: 10 Feb 92 17:33:39 GMT
Organization: Department of Computer Science, U of Copenhagen   michael@gandalf.informatik.rwth-aachen.de (Michael Haardt) writes:  
>Stop flaming, MINIX and Linux are two different systems with different
>purposes. One is a teaching tool (and a good one I think), the other is
>real UNIX for real hackers.  

Hear, hear! And now Linux articles in alt.os.linux (or comp.os.misc if your site don't receive alt.*) and Minix articles here. 

eoff (end of flame fest :-)   Niels

{正式昭告comp.os.linux的成立}

 


星期五, 十月 31, 2008

[Geekland]The Mythical Man-Month

人月神话是一本软件工程领域的经典,缘起是一个不能上网的夜晚和Brooks所获得的Turning Awards。

在我们这个星球上,如果说还有哪些软件开发依然遵循类似书中描述的OS/360开发模式的话,那么毫无疑问,电信行业的软件开发应该可以算作仅有几个之一。我自己也是在看了这本书以后,才明白我目前的公司组织架构,流程,角色,不同角色的义务和权利等等原来是有来由的。拥有一副清晰的图景我以为是必要的。

原本我想按照原文的顺序每章写一个简单的介绍和评价,不过作者再次证明了计算机行业是一个应用心理学的行业,他非常体贴在最后用单独一章(Propositions of the Mythical Man-Month: True or False?)给出了每章的简短提要和一些核心观点。原作者自己的理解肯定比我要正确,所以下面就讲一讲印象特别深的几个地方。

在MMM这本书的一开头,Brooks就用一幅画表明了一个隐喻(metaphor:在CS,特别是软件开发这个领域,一定要理解一些metaphor,不过幸好这个对我们中国人不是很困难,中国人一向享有形象思维的美誉,这是从风雅颂以来确立的名物传统):焦油坑中的巨兽。作者Brooks用这metaphor来表征软件开发过程的困难,那么困难在那里呢?困难能不能克服呢?

我以为Brooks论证了软件开发过程中的两个方面的困难:大型软件系统开发所需要的人手和人与人之间交流沟通的困难所产生的矛盾,软件开发上的本质困难。我先讲后面那个,再讲前面的。和书中的顺序有点不一样,因为第二个问题...

软件开发过程中出现的困难能不能解决,我以为Brooks的答案是有些可以克服,比如沟通问题,有些就不大好办,比如本质困难。具体可以参见文中那篇著名的论文“没有银弹”,大概得意思是说软件是现实世界的模拟,而现实世界是纷扰复杂的,所以说软件过程从本质上来说就是困难的。举一个我们熟悉的例子,比如打电话,我们理解起来简单,各有一个号码,拨通就OK了,但是我们现在知道,所有在物理层,不管是空口还是核心网,传输的只是一些数据或者说信号,而打一个电话中发生了多少逻辑业务上的处理呢?所有这些都是软件来模拟的。所以软件从本质上是复杂的,困难的。一些诸如工具等等带来的进步不可能从根本上改变目前的现状,Brooks甚至提到了I型AI,II型AI,(Turning Awards不是白拿的)这些有兴趣的老大们可以自己去看看。

下面回到第一个问题,也许能能过努力改善的地方,这也是Brooks这本书的目的。Brooks在自己的和同时代很多其他人经验基础上,总结软件工程上非常多的实用方法和指导意见,个人以为我们目前所处的系统大模大样就是书中的蓝图规划出来的。

Brooks提出了所谓的Brooks法则:

向进度落后的项目中增加人手,只会使进度更加落后。(Adding manpower to a late software project makes it later)

为什么这么说呢?按照Brooks的说法,在一个n个人的团队中,每两个人一个接口的话,一共有C n 2=n·(n-1)/2个接口,每m(1<=m<=n)个人是一个内部团队的话,一共有n!个内部团队。这就是巴别塔为什么会倒掉的原因,所以要加强沟通的强度和效率,而最有效的沟通方式无疑是face-to-face,加上一张白纸一支笔。不论是email或者phone都不能取代f2f的交流。

组内的架构书中推荐了外科手术式的团队,从我个人来说,我觉得团队内部一个Architecture+ assoiated Architecture,能够cover所有相关的技术问题。一个Documents管理员角色和一个tools/environment管理者角色是非常必要的,这些完全可以是兼职的,能够节省所有人的时间,提高效率。而documents目前来看,无疑wiki是非常好一种形式。

最后一个是角色的权利和义务,虽然我们都是来自第一线的开发人员,但是软件从根本上是一种创造性活动,在一种架构之内并不意味要完全要压制我们自己的创造力,也就是说,我们不光要强调我们的义务,同时还应该实现自己的权利。按照Geek社区的说法就是Do it youself/Just do it。我们完全可以根据实际情况来改进流程,创造性地完成工作。实际上,现在的一些软件工程方法,比如敏捷方法,就把个人的能动性突出出来,Brooks显然也意识到了这个问题的重要性,只不过大大型软件系统中,需要突出的重点不同而已,最重要的问题显然是沟通。

最后,我想要说明一下的是,虽然书中描述的蓝图使一些已经验证了的方法,而且目前看来我们的系统正是按照这个蓝图组织起来,不过这并不表明只有这一种方法做事,另一本软件工程领域的名著“大教堂和市集”,作者Raymond就令人信服的论证了在开源社区中采用的另一种方法,几乎是和MMM针锋相对的做法(从名字就可以看出:)所取得的巨大成功,虽然我个人觉得OS社区的成功至今看起来有一些迷雾,也许一个合理的解释是大多数现实当中运行的系统虽然大模大样是按照Brooks的蓝图设计的,可惜的是在具体施行上有很大的偏差,以致于一些愤怒的programmer不得不在OS社区中发泄自己的创造力(纯属瞎掰,仅供一笑:)

星期二, 十月 28, 2008

[Geekland]god,神了

Turning Award是理论计算机界的最高荣誉,几乎可以把它当作CS的Nobel Prize。不过有一点是明显不同的,就是获奖感言,Nobel Prize感言我不是很清楚,估计不超出感谢CCAV,感谢MTV之类的话。但是Turning Award Lectures(download link)都是非常高质量的论文,表达了老大们的对学科,行业的观察和发展,甚至不会放弃表达哲学观点的机会。这当然首先要感谢Alan.J.Perlis创立的传统,所谓开国气象,同时这也是继承自CS重视writing所谓essays的传统。

1974年的Turning Awards获得者Knuth是很多人眼里的god,其中原因很多,不过Knuth被人称为“理论界的第一名笔”肯定也是原因了。自然他的Award lecture: Computer Programming as an Art也是非常大作,被称作是“真正顶尖的geek风范”。原来一直以为Knuth爷爷是我的终极target,昨天我鬼使神差居然读了这篇文章,居然是出于意料的明白易懂,完全没有恐怖的,god damn的高级adj/adv。而且...

记得以前看bbs上tex时候,有人就说高爷爷很神,说是读The Tex book的时候,刚好看到自己不想读了。高爷爷就跳出来说要休息一下。OMG,昨天我看到“Science and Art”这一节时,我就快坚持不住了,不过就像我说的,实在是明白,实在是合脾胃,心想再看完这一节。于是到了“Works of Art”,本来不打算看了,可是还是瞄了一眼,就看到高爷爷说:

When I'm sitting in an audience listening to a long
lecture, my attention usually starts to wane at about
this point in the hour. So I wonder, are you getting a
little tired of my harangue about "science" and "art"?
I really hope that you'll be able to listen carefully to
the rest of this, anyway, because now comes the part
about which I feel most deeply.

OMG,神了,god is god...

所以我决定还是不要看下去,集中注意力今天在看:)

星期三, 九月 24, 2008

[Geekland]程序员的乐观性、emacs的org模式的和wiki、Newton的利爪

alas,我自己都觉得这个名字太长了。

-------------------谦逊的分割线---------------------------

程序员群体天生就是一个乐观的群体。但是且慢,真的是这样吗?让我们来看看有哪些表现。

  • 如果你熟悉社区,那么你对呆伯特漫画系列和xkcd webcomic一定不会陌生。
  • 随便找一篇程序员写给程序员看的文档,你会有怎样的印象呢?比如这篇正则表达式的教程,里面有什么呢?

除非你是超人 :)

要么你是一个天才,要么,你不是地球人

IP地址中每个数字都不能大于255,大家千万不要被《24》第三季的编剧给忽悠了...

地球人,是不是觉得这些术语名称太复杂,太难记了?我也和你一样。知道有这么一种东西就行了,它叫什么,随它去吧!“无名,万物之始...”

...god

怎么样,有点感觉了吧。是不是有点...扯

ok, 看过了事实,让我们一起来想想为什么。

  • 程序员写code非常枯燥,再不给自己找点乐子,就真的要崩溃了
  • 程序员是一群高智商的群体,并且有文化,为了体现优越性,有足够的理由表现一些风度,而humors就是最好的表现形式
  • 我为什么要写程序员的乐观性,¥%……—*#

--------------restart...loading...----------------------------

最近因为某种原因,阅读了人月神话,非常非常棒的一本书,其中有这样的一节The Second-system Effect, 大意是说一般人在软件的第一版中小心谨慎,第二版中就要大胆的多了,多半会按完美主义者的做法去添加一切稀奇古怪的想法,这个往往会使软件的开发步入一个泥塘,最危险的系统。为什么会有所谓的second-system effect呢?Brooks在随后的经典的没有银弹这篇轮文中指出软件开发之所以困难的根本原因是系统就是这么复杂,软件的核心就是模拟,比方我们说打一个电话,真正的发生是在电路接通时候,我们需要把这个物理过程映射到软件系统中,同时还要模拟这个过程中发生的逻辑。

然而,不幸的是,大多数程序员都没有意识到系统的复杂性,也就是程序员有说盲目的乐观性,这是因为(下面的是一种典型的心理学观念):

  • 软件系统实在太复杂了,远比我们想象的更复杂,然而,进化论给与我们的本能使得我们人类天生具有这样的倾向:把过分简单的事物复杂化,同时也把过分复杂的事物简单化。也就是说,在应当悲观的时候我们往往比我们想象的要乐观一点,而在应当乐观的时候我们往往又要比我们想象的要悲观一点。对于程序员来说,不幸的是,我们往往要面对的大多数现实都是悲观的:-(
  • 软件过程正如很多人指出的那样,是类似于写作,绘画一样的创造的过程(不难理解为什么The Element Of Style这样一本指导写作的书在程序员和geek那里被奉为圭皋了^-^)。在我看来,创造的过程是带着惊喜和呵护的心情的,带着一种添砖加瓦的态度,是一种建设者的心态,不难理解为什么这种手工艺创造者对于现实多半会带着一种乐观大于悲观的态度了。同时,程序员和作家、画家或者音乐家之间最大的区别是,程序员要创造的世界几乎就是一个真实的世界,类似于造物主的工具让程序员有了从“无”到有的能力。Alas,造物主。也许程序员的成就感要来得强烈和自然一点吧:~)

星期三, 九月 10, 2008

[web2.0]推荐Youtube上的一些channel

从这里看到一个非常cool的关于web2.0和新媒体的youtube视频,作者是传播系的。

顺便发掘了一下youtube上面的channel,就跟大家共享一下。

http://www.youtube.com/user/leelefever?recommended=0

这个就是做上面那个视频作者的channel

http://www.youtube.com/user/adcouncil

这个是专门广告的,广告讲究的就是抖包袱(这里好像都是些公益ads)

http://www.youtube.com/user/MIT

MIT和youtube的合作,不过好像OCW更好

 

http://www.youtube.com/user/stanford

stanford,stanford和itunes也有个合作

http://itunes.stanford.edu/

 

http://www.youtube.com/user/ucberkeley

UCBerkeley, and http://webcast.berkeley.edu/

 

http://www.youtube.com/user/googletechtalks

google tech talk, and http://research.google.com/video.html

 

http://www.youtube.com/user/Google

google自己在youtube上面的公关阵地

http://www.youtube.com/user/chelseafc

居然还发现了车路士的公关

http://www.youtube.com/user/LearnMagicTricks101

魔术学习

http://www.youtube.com/user/motg

街头足球,这个很扯,比老马好像都强,我才明白过来上次我们看到的街头足球广告(http://www.youtube.com/watch?v=Jl39guVpofw)是有来由的

(tag:motg)master of the game

星期四, 八月 21, 2008

[ComputerScience]Alan Kay & computing teach

Alan kay是人精,他也一贯强调对计算机教学,特别是孩子的计算机教育。前几天也读到了一篇他的访谈,甚为有趣。

大概看了一下,可以感觉到Alan Kay对于认知科学,教学法(我想到一个词,pedegogy)的强调。讲究因材施教,反对只通过讲授的方法,而是赞同在学习music/sport过程类似的方法,认为除了语言之外,还有感知潜意识。(Alan开了玩笑说,你要学习的地方它其实不懂英文。什么,看不懂?说的就是那只打网球的手)

其实软件叫做software craft,有的地方翻译成技艺,意思是说手工艺人,就像比如游泳,一旦学会就永远不会忘记,(aha!是的,波恩的身份)个人经验,coding是要言传身教的。比如做一件相同的事,在software上有无数种办法,我们熟悉的往往是那几种。

现在有点理解硅谷好人Woz为什么志向是当一个小学老师了。

but I think there are real parallels with what happens with learning programming

附一条:

常青藤名校的计算机课程比较

再附一条:

都是很久以前的bagua了:0

dress like a programmer?(一 二)

顺便google一把geek的clothing style,这个好像还不错;)

星期一, 八月 04, 2008

code test

from xml.dom import minidom 
if name == __main__:

星期四, 七月 31, 2008

[Geekland]WIB & philosophy

worse is better这篇文章真是越看越有趣,这篇文章前面后面还讲了一些lisp的细节,不过最重要的是提出了WIB的思想,事实上,jwz就把这一小节单独抽出来,作为一篇essay:The rise of "Worse is Better"放在自己的site上。看来早在1990年工程界就开始反思80/20法则了。

Unix/c或者worse is better或者New Jersey approach的哲学是简单优于正确,差一点(损有余)刚好。所以作者才说c是汇编,简单,把复杂性留给了UI,而unix/c就是computer viruses,比right thing能够迅速流行。

不过我觉得要看到lisp的原来的设计目的是AI,在AI上面差不多几乎是致命的缺陷,想想看,一个人说话,比如英语,你只听懂了80%的单词,最终会明白多少呢?几乎是一头雾水。这也放映了业界在80年代末,90年代初一些不切实际的幻想,似乎到现在还有观点认为AI是进展最让人感到失望的领域之一。一些最有聪明才智的人才作出的一些最天才的尝试基本都失败了(可以参见这本书),比如麦卡锡大佬,费根鲍姆老大的故事。但是这些努力现在看来也不是没用,反而现在随着web2.0,长尾,个人化,推介系统的流行,以及multi-core等等,又逐渐被人们再发现,又流行了起来。

在这之后,才出现了linux,oss和internet也逐渐流行,然后一切就变成了现在的样子。可见*nux系统和c,乃至c++,java这一流占据天时地利人和的历史也不是自然而然水到渠成的,套用一句话来说,是自然选择的结果。

因为在这篇文章里,我们可以看到,lisp社区有着一样好的hacker,同时也不是像我们通常所认为的那样,lisp的编译技术比C差,效率低。那么决定的因素是什么呢?是背后的哲学,是分别以mit为代表和UCBerkerlay代表的不同思想,不敢妄评,不过mit似乎更学术化一点,UCBerklay要工程化一点,在iWoz里面也能感觉到在60、70年代UCBerklay还不是特别好的学校。而worse is  better在大教堂和市集里被认为是linux哲学的先驱。

历史真是非常有趣,感觉是有几股暗流,交相辉映。

星期二, 七月 29, 2008

[programming]python, one stupid error

准备写一个处理xml的小脚本,想到了python,于是准备做一点小小的实验,因为是处理xml,所以就命名为xml.py,加上执行权限,run...问题来了,报这样的错:

Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "xml.py", line 2, in ?
    from xml.dom import minidom
ImportError: No module named dom

开始我以为是python的也有所谓的libpath的问题,上网google了一下,不得要领。

而且我看到机器上面有这样的dir

/usr/lib/python2.4/xml/dom

我只好把我得错误信息直接提交给google,刚刚看了第一个我就意识到了我得愚蠢错误,python把我刚刚写的这个xml.py当作xml的module导进来了,我还正奇怪为什么会生成xml.pyc呢,真是个愚蠢的错误。

教训是不要把你的*.py文件命名成标准库里面的文件,包括目录名。

收获是对python的命名空间多了一点了解。

星期一, 七月 28, 2008

[geekland]Alan kay's reading list & worse is better

通过del.icio.us的network发现了这个好玩的东东,号称是Alan Kay推荐的阅读列表,原文是这样说的

The following list was prepared by Alan Kay for his students and is presented here for those who want to learn more about the ideas and philosophies that influenced the creation of Squeak.

Aha!还记得我的那一篇post上面提到的computer science里面隐秘的发展线吗,这个绝对是一个绝好的印证,大约我可以看出来的有心理学,儿童教育,东方的传统等等。

=======我是传说中的分割线=======

Richard P. Gabriel在追忆他的worse is better的思想产生过程的这篇文章也特别有趣,值得看看。特别是里面提到的人名,作者没有给链接,我bagua一点,就不辞劳苦的google了一把

  • Gerry Sussman(wikipedia, person) SICP作者之一
  • Carl Hewitt(wikipedia, person)MIT EECS的prof.,程序语言的planner的发明者
  • Scott Fahlman(wikipedia, person)CMU的cs prof.,同时也是:-)的发明人
  • Jamie Zawinski(wikipedia, person)这个老兄jwz如果说是史上最牛之高中生估计没有太大的疑问吧,功绩包括xEmacs和mozilla和Netscape Navigator的早期版本。他的个人主页真实太cool了
  • 作者本人Richard P. Gabriel(wikipedia, person)非常有名的lisp专家,common lisp commitee的成员,他的essays里面有一篇The Evolution of Lisp对lisp繁复的发展有比较好的整理
  • Richard Stallman这个伯伯我就不再说什么了吧

让我感到惊异的是这些人来自于不同学校,同时也有学术届的prof,和单纯programmer,但是从文中看,他们之间的相互的了解和联系显然很紧密,而且这些只是冰山一角,我相信通过他们联系起来的geek & hacker & prof.会更多。这样的现象我只是在web2.0兴起之后,在国内的blogsphere上面看到过,但是要知道,那是在Internet和各种各样的工具发展起来以后的现象啊。也许这就是Paul Grapham在Great Hacker里面所说的Clumping现象吧。alas!国内的高校我所知道的只局限于bbs,甚至一个学校不同系之间的联系都不多,缺少一些润滑者啊。A国人果然执IT技术牛耳,要学习的地方很多啊。

星期五, 七月 04, 2008

[ComputerScience]顺流而下

Down in missippi where I was came

起因来自枫哥给我的一本书《大师的智慧》out side their minds

Computer Science很多人坚持认为不能称为科学。不过就我而言,CS已经进入了physics, mathematics同等的地位,属于能够找到坚实的,形而上的基础和方法。在差不多研二的时候,当我孤独的在wg打发无聊的时光的时候,我意识到找到了一种也许是可以从事一生的职业。不过相对于phy和math,cs的历史要短得多,不过这丝毫不妨碍它群星闪耀的天空。而且在我来说,我一贯注重的方法论是考古学。(福柯的考古学?)我想稍微解释一下我心中的“考古学”

(update:我上网看了一下福柯的理论,繁密精深,不是我所能够掌握的,不过我觉得还是包容在福柯所谓的“知识考古学”之内,更退一步说,我想象中的这种方法和福柯是有着密切联系的,最起码是缘起)

为什么一切就是现在这个样子,而不是其他的样子呢?现实是历史汇聚涓涓细流而来的结果还是像打碎的镜子各条裂痕相互影响的结果?大多数情况下,两者兼而有之,不过按照塔勒布先生的说法存在一种存活者偏差(Fooled by Randomness/Black Swan,这两本书有机会再讲)的现象,人们天生偏向解释,(这个在社会心理学也有类似的概念,需要回去查一下),当事后诸葛亮,需要给个reason先。于是在历史的迷雾之中,我们今天所熟悉的种种一点一点的添加到认知体系当中,但是太多的忽然事件我们都已经淡忘了,虽然对于结果很有可能我们找到了合乎情理的理由,也许是在此话语之下启发出来的互动的过程,到今天看来已不稀奇;也许甚至是和缘起毫不相干的理由。

(update2:忍不住再说一下塔勒布,FbR和BS两本书讲的就是概率和随机性,突发事件,非常有意思的阅读体验)

所以我以为需要深入考察当时的情况。譬如CS来说,研究的问题,(逻辑基础,能不能解决问题;算法,更好的解决问题;AI,旁支,能不能自主地发现要解决的问题),所运用的方法论,还有的是贯穿其中的人。相比之下,人这个样本空间受到特例的影响极大,就是说CS的发展和CS科学家非常相关,科学家(sorry)的背景和知识都有可能造成非常的结果和影响。(不好意思,我又一次的使用了塔勒布先生的分析框架,因为这篇东西虽然我早有想法,不过这里看到的是我今天的修改稿,看,思想的碎片轻而易举的就进入了我的脑袋)举一个小小的例子,在CS中,logic是毋庸置疑的一条主线,相形之下,OO就显得吊诡很多。

枫哥给我的这本书就是这样一本书,记录了一些事实,发掘出了一些root。虽然稍微有点薄弱,还不是很详细。随便说一下书名,中文名大师的智慧,原书名Out of their minds,既非音译,亦非意译,毫无干联不说,原作者借此传达出来的一些微妙的意味完全丢失了,光从书名看,原作者显然是带着一点存在主义的味道的,同时还传达了一种既有超越又有扩展的可能,而扩展的这种含义正是我所特别感兴趣的话题。

如果有传记就好了,片言只语还是不够的。譬如迪杰斯特拉,麦卡锡,高纳德,巴库斯,拉宾。也许CS的历史还太短了,大多数人还都健在,还不是总结的时候,同时,CS本身这样一个有点尴尬的地位,正如Dijkstra所言,计算机和计算机科学的差别正如望远镜和天文学之间的差别,而且,CS同时也是异常的困难,哪怕是我这个可以算半个科班的出生,知道毕业,也没有听说过Y,所以CS的受众不是太广泛。但是,CS的历史比较而言,也许是有着最多的意外性的一门学科,我希望以此为起点,能够从稍微有点不一样的地方来发现cs的传统,现在想到和看到的大致有有心理学传统,儿童教育学和初学者的传统,东方传统,生物学的传统,工程的观点,图论,可计算性…

希望能够不断地发掘和写下去,wiki也许是一个更好的选择。

星期六, 六月 07, 2008

[web2.0]时间的量化和lifestream

桌面软件

Firefox
  • 有一段时间很郁闷,打开之后,往往只看到一个process,却看不到窗口。最近换了skin,终于在firefox窗口没有出来看到了一个另外的窗口,上面闪过进度条,你猜我想到了什么,windows的启动



  • 第二个现象,我的firefox不一样,就是说在家里用的和在办公室用的不一样,和我以前用的每一个firefox都不一样。为什么?因为plugin太多了,我只记着几个,譬如better gmail…据说有人重新安装ff很痛苦,要备份xpi。我才刚刚意识到这个问题。很多ff的 plugins我越来越想念。可惜plugins越来越多,速度,尤其是启动速度越来越慢
Adobe AIR

有两个WebSerivces的client,Twhirl,号称最好用的twitter的client,还有一个是friendfeed的AIR client alart thingy.
Twhirl很好用,可以自说自话。我每天只要上网,就会开qq和MSN,可惜经常十天也说不了十句话,没有交流的对象和事情。twitter是个好东西, 可以自说自话,不需要face2face,甚至也不需要一个团体。但是到twiter.com上去发布显然太麻烦了,Twhirl提供了这样的可能。

Web Services/Application


  • Twitter

    毫无疑问,twitter+twhirl很无敌的,gtalk虽然也可以twitter,不过个人感觉专注更胜一筹

  • friendfeed

  • 刚刚出了概念lifestream,后面就出了个friendfeed,对于这样的产品除了能说这就是我想要的还能说什么呢?friendfeed我个人觉得非常重要,从webapp->mashup->lifestream,从中我们可以看到一条清晰的产业之路。还记得我们以前讨论的单点登陆的问题,当时我就不大看好openid,不过现在我却从friendfeed中间看到了问题解决的另一种思路和方案,现在我相信在未来的单点登陆的方案之中rss会发挥更加重要的作用。

  • del.icio.us/diigo.com
    这个还有什么好说的呢?我们每个人的商业价值就在于我们每个人上网的时间,SNS或者说web2.0只不过找到了一种量化的方法。
  • google page/ning.com
    个人site应该是怎么样的呢?看看那些professor的个人pages,一个类似的wiki系统是需要的。我在有营建自己的google pages,放一些常用的reference和link

  • rssmeme有点像zhuaxia或者xuanguo的热文,这几乎已经是我现在打发时间的杀手锏了。从donews->techweb->sina tech->…

在终于找到了info发现的方式,而且你可以确信不会浪费时间。Data真的是根本,就像费根鲍姆说的“知识,还是知识”而不是逻辑,才是制约条件

星期三, 四月 09, 2008

[computer science]Church Numerals

说来惭愧,lambda,我虽然也算半个科班,却还不太清楚。看了看g9老大的文章,有了点兴趣。
不过说句实话,g9老大虽然是中文,却还不如这篇文章好懂。
闲话少说,起因是上面Rice大学311课程的辅助材料里面提到了Church Numerals的exponentiate的形式应该是怎么样的。
Church Numerals
Zero:C0 = lambda fx.x
one: C1 = lambda fx.fx
n: Cn = lambda fx. f(f(...(fx))) = lambda fx.f^n x

if M =Cm, N = Cn, then

ADD:
Cm + Cn = lambda MN. lambda fx. N f(M f x)

Multiplication:
Cm*Cn = lambda MN.lambda fx. N(M f) x

具体我就不验证了,文章中清清白白,只要按照lambda算子的规则就能得到想要的结果。问题是指数运算呢?

我大概推了一下,也不知道对不对,还希望哪位看到错了能指出来, 3ks先

exponentiate:
Cn*Cn = lambda f x. Cn(Cn f) x
Cn·Cn·Cn = Cn·lambda f x. Cn(Cn f) x
= lambda fx. (lambda f1 x1.Cn (Cn f1) x1)(Cn f) x
=
lambda f x. Cn (Cn (Cn f)x

Cm^Cn = lambda fx. M(M (...(M f)))x = lambda fx.(M^N f)x
还是很好玩的。^~^

数学是很抽象的,就像曲率。要想知道具体含义,还得有个文字解释,做一条切线。

lambda算子目前我还不是很明白,不过自己稍微想了一下,还是很有意思的。lambda就相当于函数名称,f,x相当于参数,譬如lambda fx.sth我们可以表示为:
func(f, x) = sth
func(f, x)
{
sth;
}
只不过lamdba把他们都写在了等号的一边,aha,函数参数加上一个引用,OK, like this
func(f, x, &sth)
{

}

关键是我们不需要知道函数体是怎么样的。我们就知道我们可以构造出来Church数,构造出来表达式,按照我们熟悉的运算法则运算。太神奇了,Church果然是天才啊。

还没有可以学习lambda在实际语言中的应用,譬如python(我就不说lisp了),有了感想在写。

BTW:
1.这篇文章更加通俗易懂,还有很多online pratices
2。Rice univ.的这门课程311似乎也很是值得看看,应该就是这门课程开发了DrScheme环境,对向我这样的new comer很友好,只不过现在好像换成Java了

星期六, 三月 29, 2008

[无题]无题

just for myself.

传统的力量
心理学

根源
枭獍
读书
CIA

星期一, 三月 17, 2008

[翻译]警惕免费导向经济

原文link
按:当自由不再是一种信念而是一种手段

==================================================

几周前我们在这个blog上发表了一篇名为“警惕免费的午餐 ”的blog,其中我们讨论了免费现象的兴起,这里免费指的是一种市场策略,即数字产品是像礼品一样赠送的。这个月Wired杂志由执行主编Chris Anderson做了一个类似主题的封面故事 。其中对Anderson即将发布的新书做了一个预告,就是(你已经猜到了)免费。不过这篇文中我们将讨论这个新的经济模型看起来很糟糕的两个特性:垄断市场和复杂交易。
Chris和其他免费导向经济的倡导者声称随着数字产品的价格迅速下降,最好是直接把它们免费。这种方式能保证你的用户群,因为人们更愿意得到免费的东西,而不是哪怕只需要一分钱的东西。Chris列举了诸如这样的例子:免费的Web Mail。免费的DVR,免费的411,甚至$20的机票(并不完全免费,但是已经相当接近)作为免费导向经济出现的证据。
人们更钟爱免费的午餐,而大公司也有能力提供免费的午餐,问题在于免费导向经济是好是坏目前还不是很清楚。

垄断市场之GMail的故事


Chiris所引用的一个主要的事例是web mail。Yahoo!有一个免费版的web mail,但是只有有限的空间,必须付费才能得到额外的存储空间。然后google来了,不仅带来了免费的email,还带来了巨大的存储空间。于是一些人(在这一点上几乎所有早期的试用者)从Yahoo!迁移到了GMail。既然这种趋势是如此的明显,于是Yahoo!别无选择,只能增加的邮箱大小并且也免费来保持竞争力。看起来这是Google漂亮的一击,赢得了客户的认可。但是这是公平的竞争策略吗?
说Google研发出GMail,并且提供GMail服务没有什么成本是显然错误的。很可能每年GMail将花费数以百万计的美元。事情变得这样主要的原因可能是因为Google有能力提供很酷而且免费的GMail。这是一种进入新市场的标准的垄断竞争策略-压低价格(这里是$0),驱逐其他竞争者。Yahoo!实际上是这个市场的先发者,并且有着一个相当公平模型的很完美的产品:免费提供一种基本功能的产品,和收费提供更多空间的升级版的产品。但是当Google采取了行动时,Yahoo!的这种模型就没有竞争力了。
onopolistic Markets: The Tale of DVR

垄断市场之DVR的故事


另外一个被引用的例子是数字视频录像机(DVR),Comcast 免费提供DVRs,就是手机公司免费提供基本的手机,然后从服务上赚取利润。也许DVRs这个例子有一点久远,不过它很不同于GMail的例子,在这里是免费提供某些东西,为了让客户为服务付账-其实际价值会随着时间得到体现。这和一家公司免费提供产品进入一个新的市场是不一样的。
且慢,免费的另一面是质量。每一个有Comcase DVR的人都知道遥控器不是比较差,实际上它根本就是坏的。甚至像我这样拥有计算机科学硕士学位的老兄都花了一个月的时间才掌握了它的使用方法。免费并不总是好,很快,而不是稍晚,免费就会给质量带来瑕疵。如果它是免费的,就不需要那么多工程师在上面了,接着为什么我们需要修正bug?它是免费的-这就已经足够了。

垄断市场之没融资的创业者


也许最担心免费的人是创业者。刚开始就要面对如何和免费竞争的痛苦?假定某人就如何提升web mail有一个非常棒的创意。不过进入到主流市场是非常困难的,在自由导向经济的新世界里,google已经设定了消费者的惯性,你不可能在价格上做文章了。就在不久以前,创业者可以用更好更便宜的口号来进入市场。不过现在更便宜需要被免费替代,价格已经不是标杆之一了。
更大的问题是融资。你能投资于这样的创业者么?即使领先也不能向消费者收费。有人可能会说我们生活在广告就是金钱的世界里。是的,我们的确是,但是事情不是那么简单。首先,有多少创业者利用广告赚到钱了呢?是的google做的非常棒,但是Yahoo呢?我们过去使用的Flickr,每年可能要支付$25的额外费用。现如今我们说Flickr必须对每一个人免费,而且是无限量存储空间才能撑下去。对于你自己的图片广告也有什么模型吗?


复杂交易之中间人



垄断就没有好事情。它首先微笑着递过来一根胡萝卜,接下来一定是大棒了。不过免费导向经济还有另一个让人担忧的地方——中间人。要明白为什么,尝试去想象一个生产需要广告的产品的公司。中间人是广告网络,一边是生产产品的产家,另一边是对商品感兴趣的受众,不过他们并愿意为自己埋单。于是广告出现了——问题的灵丹妙药。


经济处于低迷时期,厂商们会突然不想再在广告上花费。是这是真的么?不做广告的结果就是生意马上就会受影响,即使是对你产品的需求没有一下子完全消失。这很奇怪吗?即使你的消费者基数增大,你仍然在亏钱。


问题的关键是每一个生意人都应该考虑到广告的复杂性。你不仅需要做出完美的产品,你还需要非常擅长于打广告。对你来说,选择他人的广告系统还是自己建造广告系统,是非常痛苦的决定,因为自己建造广告网络是一项昂贵的提议。

复杂交易之哦……复杂



更广泛一点说,免费导向经济会导致一系列的隐性收费行为。chris举了一个例子,欧洲航空公司对每位旅客只收$20。其他的钱就通过餐费,饮料,高级座位,信用卡操作,广告提成等等。对于商家和消费者来说,这听上去是难以置信的复杂。


发明和说明这些非常小的收费的成本是很高的。对于消费者来说,就是一场噩梦。哦,你是说在航行中你想座着而不是站着?需额外支付$20。应该一个价格打包买一打东西,人们更喜欢包括所有,而不是什么都不包括,大公司从这里学到的一课似乎被人们遗忘了。

结论


毫无疑问,我们会看到越来越多的商品以免费的方式提供的例子,这并一定是件好事。免费(或者说自由)有着多种多样的方面和面孔。Fred Wilson称之为免费附加(freemium)的Flickr的免费模型是基本版本免费,加强版需要收费。这种模型不同于Gmail的模型,Gmail是整个产品以全功能的方式免费。免费导向经济的另一面就是垄断市场,对整体起副作用,并且较少的激励创新。另外中间人和交易复杂性是这种新的经济潮流的另一个副作用。=====================================================


读后感


1.文中翻译过来的免费,原文是free,也有自由的意思。


2.其实提到的gmail的例子我以为不是很恰当,Gmail不光是技术的试验田,同时Gmail也承担着google单点登陆的ID作用,其实了解过风不是系统的同学都知道,这通常也是第一个要考虑的问题。但是...


3.想想GPL v3被称作GPL霸权 ,还有所引发的口水


2.在想想SUN开源JAVA的过程,据说 是IBM的高级副总裁一个故意泄密的邮件,挑逗起开源社区的群情激愤。(在我看来,这也稍微带有一点网络暴民的色彩)结果呢?McNealy下台,Sun裁员,然后solaris开了,SPACR开了,JAVA也开了,能开得都开了。恩,很好,这是旧模式的失利。但是...


3.而李开复到学校演讲的骄傲的提到直到我们找到了一种商业模式,不妥协的态度。想想最近 M$,yahoo的故事。而Yahoo曾经拥有的辉煌 。难道是旧商业模式的胜利。


4.不可否认,Internet极大的提高了生产力,但是愿意买单的人呢?现在的情况好像是形成了一种博弈,囚徒困境式的博弈,到目前为止,看起来是消费者胜利了,但是在硅兽 的阴影下,整个行业创新的能力逐渐消失的时候,譬如说baidu的地下帝国 。再比如有人说Youtube的被收购是个标志,幸好还有个FB。难道就没有个纳什均衡(不懂博弈论,望高手指正)


5.Internet可有可无吗,一种生活方式的改变,也许需要一代人的时间,从小就成长在这种方式之下的孩子。工业化大生产之后,正式进入了大众消费品的时代,带来了广告。到现在电影早在电影院里看了,看球也要钱了。也许要等个5年以上,那么不知道有多少人可以撑过去,还有持续的创新能力么?


6.一些地方提到了generation free 。也许最重要的还是Lessig 说的,分清楚自由和免费的区别。

===============================================

update:

有人问为什么“不把 Freeconomics 翻译成免费经济学呢”

1.free有免费也有自由的意思。而且我第一眼看到肯定会认为是自由。我相信发明Freeconomics 这个词汇的人(我不太肯定是不是安德森)有强调观念的意味,而“免费经济学”这个词有点普通,看不大不出来。当然“免费导向”似乎也不是个恰当的翻译。
2.大众消费时代的概念最开始引起我注意是在《华尔街史》这本书里面。(好像特别是在汽车大众化以后的事情,100年前的社会和现在几乎是两回事情。整个过程好像也持续了很久,知道60年代才完全为大众所接受。想想安迪·沃霍尔著名的波普画系列吧,信用卡的大发展也差不多在60年代。(这个是大话题,我没有相应的才学)
3.而安德森之所以创造出Freeconomics 这个概念,显然是针对所谓的“大众消费品”时代的。(http://www.dapenti.com/blog/more.asp?name=xilei&id=11008)他认为这是长尾和丰饶经济的自然发展,而大众消费必然会消失,历史好像又在螺旋式的发展?
4.不过对于这种违反直觉的判断,我只能说我热爱自由,拥护自由。但是我不相信完全免费。
5.其实自由是有限度的,历史上从来就不乏反思者。想想大革命的口号吧"自由平等博爱",自由是基础,平等是限定,博爱则是引申。(这个是个更大的话题 :$)

星期五, 二月 29, 2008

[读书]阅读的乐趣--其一

按:这篇文章转自我的live spaces,本来只想作为心情日记用的,也不想有交叉。还是忍不住放上来。

记得很久以前,也就是很小的时候,ld就告诉过我,王国维的方法叫做互证。从其他的材料,比如诗歌,新出土的文物,其他民族的史料记载,特别中亚的一些过去我们称作“西域”的地方的史料。更准确地说,这种方法叫“文史互证”,而且这种方法也是陈寅恪的方法。
翻了点旧账,主要的意思呢是因为最近在阅读的体验中,发现类似“互证”的文本给我带来了很大的乐趣,的确在不相干领域中的书提到差不多的东西是最可信的,或者有的时候你会了解它的理由,很多东西不是你想得那样
  • 譬如我以前提到的“金色降落伞”,在“华尔街史”以及其他很多书籍当中,都当做是华尔街fb堕落,权欲薰天高管们搞出来的东西,虽然很疑惑这么明显的有缺陷的机制的存在。但是在“门口的野蛮人”一书当中,我知道了这是在恶意兼并的背景下,为了防止公司被收购而加的限制,基本上这种东西设计者的意图是不希望它实现的
  • 再比如,在“美国宪政历程”当中提到一些大法官,其中有个沃伦,基本上学养深厚,道德高尚,推动了民权运动。但是书中只是隐约提到了他和尼克松的交恶。再看“硬球”中提到尼克松在竞选加州参议员的时候,巧妙的用卑鄙的但是有效的手段,利用了当时的州长沃伦先生,就得到了比以前阅读时更加鲜明地映像,不难明白两者不光是在信念上不一样,在本质上两者也都是不一样的。不过,沃伦是州长,上网查了一下,还曾经是副总统候选人,也就是说,是政治人物
  • 另外,在昨天看“泡沫,从股市到楼市的繁荣幻象”的时候,在提到泡沫的根源,在检讨新古典主义理性自由人的假设的时候,提到了行为经济学对人的影响作用的时候,提到了两位以色列的经济学家,卡内曼和特沃斯基,关键是他们在2002年得到了诺贝尔经济学奖。aha,心理帐户,这不是一个老兄推荐我看得一本书里面的内容么,当时推荐的时候他说,理财书籍,这些错误我们都会犯,在我们一不注意的时候,虽然道理比较简单,当时因为是理财,我还不以为意,只是大概翻了翻。hehe,看来有时间应该好好看看这本书“半斤非八两”,不过在这本书中,理论的名字叫“心理经济学”。而根据wikipedia的结果,该理论的名字叫“展望理论”
  • 再有,稍微扩展一点,昨天在yeeyan上看到了十大杰出社会心理学研究,aha,这几天我刚好也在看“社会心理学”。已经介绍的那几个实验我基本上在书中我都看到了,怎么说呢?书中介绍的试验没有那么详细,也不如yeeyan上的煽情有趣,但是书上的知识却是系统全面,从方法论开始讲起,实验的结果也有相互参照。不看书的话,我得感觉是很容易就会被诸如“tipping point”或者“blink”或者yeeyan上的这种文章吸引,认为自己找到一个新的认识自己,认识世界的方式。但是,我自己现在的感觉是心理学也是一种科学,建立在实验的,归纳法基础之上,也有很严密的逻辑,但是比较起自然科学来,用公式表达的理论来,应该被称作为“软性科学”,我自己还是更愿意“信仰科学”
  • 说到“blink”,我又想起了“社会心理学”,其实只要你读了前两掌,blink中的那些内容你就不会感到那么新奇了。心理学就讲潜意识,不光是心里潜意识还有感知潜意识,也就是说,我们看到的,听到的,感觉到的绝对比我们认为自己感知到的要多得多,这是人类在进化过程中形成的特殊的本领。不过,从这个角度,计算机视觉应该怎么往下走呢?
  • 最后在举一个例子,在看“蓝海战略”和“魔鬼经济学”的时候,两本书当中都提到了纽约市的在90年代的犯罪率下降的例子。不过兰海战略是从“破窗理论”出发的,论证了市长朱利安和警察局长的突出作用,最终支持了自己的蓝海的观点。(似乎tipping point也提到了类似的话,不过这次是想说明“破窗理论”多么有用),不过在魔鬼经济学却从统计学的角度,从婴儿出生率的角度,从社会大背景的角度说这只不过是自然现象,而不是什么人力所为。aha,相同的例子,却被用来说明两者相反的理论,这个就不需要我引申什么了吧?
不知道各位在阅读过程中有没有类似的体验和类似阅读的乐趣呢?

星期六, 二月 02, 2008

[math theory]Large Deviations

good math, bad math 是g9老大介绍的blog
今天一看到这片帖子,我马上就想到了“黑天鹅理论”,最早看到是在思维的乐趣的这里,当时就想长期资本公司也可以用这个来解释,以及后来的不凋花的事件。
不过,看起来虽然很爽,终究觉得有点玄而又玄,好像是社会学上面一个独特的理论一样。现在好了,我们有了数学模型,一切都是摸得到了。而且看起来这个领域虽然是最近才发展起来的,不过发展的却是很快。看,这不是得奖了么

好了,废话少说,看看这篇blog都说了什么

主要观点


Large deviations theory asks a very different question. It asks: what about the unlikely outcomes? Given information about probability distributions, what can we say about outcomes that are significantly different from the expectation? In particular, what can we say about how the probability of outcomes vary as they get increasingly distant from the expectation?
Large deviations theory问了这样几个不同的问题:那些不大可能的结果是怎样的?给定可能的分布的信息,对于那些显著偏离预期的结果,我们知道什么?特别是,当结果逐渐偏离期望值的时候,他们是如何变化的?(有点拗,不如看原文)

提出背景


这些问题为什么重要呢?这个领域有一名工作在保险公司的数学家创立。正常来说,保险公司的保费是根据过去年份的统计数据为 基数来设定的。例如,保险公司在预测发生洪水时它需要支付多少钱时,它的依据是在过去的一段年限当中,他必须支付多少来抵消洪水带来的损害。但是,正如从 卡特利娜飓风中学到的,有几年是戏剧性的偏离正常值-这样保险公司在这几年当中就会支出比正常年份要多得多的代价。
所以对于一个保险公司来说,他们不仅要知道对于某一个给定年份他们需要支付的数额的期望值,更要紧的是知道,那些造成达到正常值一个甚或两个数量级损失的特异的年份的概率。

Prof. Varadhan的工作


Prof. Varadhan发展了被称作Large Deviation Priciple的理论,Large Deviation Priciple提供了解出这些巨大偏移的概率的方法。就想我说的,这是无法想象的困难的工作。Varadhan的工作是做非线性分析,偏微分方程以及其他半打特别困难的数学工具,把他们糅合到一起发展出了large deviation概率的完备理论。可能是Bayes以来概率论上最重大的突破了。
Varadhan的工作除了应用于金融领域外,对于现在 物理学也是一个巨大的贡献。在单个基本粒子行为概率可被预测的情况下,这些粒子群体的活动通过large deviation概率有着很好的解释。特别是,在热动力学上,我们只能得到单独粒子行为概率的描述;不过我们想知道的却是这些粒子作为一个巨大集合体的 聚集在一起的描述。Prof.Varadhan正在和物理学家合作把他的理论应用与热动力学。

感想

  • 在这里我看到了一个基本的数学技巧,把变化变成变化率。aha,这不是求导数么?
  • 和The black Swan这本书不一样,社会学家提出问题,描述想象。数学家确是找出模型,运用数学工具。也许结果不一定对,也许会带来对纯粹理性的盲目信任。但是相比之下,我还是更愿意信仰科学

星期日, 一月 13, 2008

[essays]顶尖黑客 (翻译)

原文link在这里

译者按:
1.作者Paul Graham 是一个Lisp黑客 ,同时也是Y-Combinator 的联合创始人(什么是Y-combinator的本意?看看这里 ,可惜我没有看懂,不过我猜想和Lisp有很深的关系,好像是lambda算子可以推出Y)
2.这篇文章是作者的Essays系列 ,注意它不是blog,也就是说,这是TMD文学作品。不得不承认,这篇文章从篇章结构到遣词造句,都已经超越我了E文水平。(也许只在四六级考试里见过...)这里 是我在google docs上的草稿,如果你发现错误,尚请顺手改过来。(我在翻阅这篇文章的同时,发现了另一个老兄 已经翻译了Paul的几篇作品 )
3.翻译这篇文章的缘起是一个无聊星期六的中午和下午。不过能够坚持把它读完并打算把它译出来则是因为我自己最近的经历和体验。

=====================================
========下面进入正题======================
=====================================

(这篇散文源于2004年Oscon 上的一个演讲)
几个月前我刚刚完成了一本书 ,在书评中我发现了书评中诸如这样的字眼,“煽动的”,“争议的”,更别说还有“白痴般的”评价。

我无意使那本书处于争议之中,我只是试图更有效率,告诉你们已经知道的事情是浪费你们的时间。不同是更有效的方法,不过这注定产生一本火药味的书。

爱迪生们



关于哪个是最有争议的观点中,这一个无疑没有太大异议:寻求更多的变化,这并不是像我们想得那样的大问题。

我没有在书中说寻求变化本身就一定是件好事,而是说在某些情况下这是一个好的征兆。脑袋的阵痛也许不是好事,但是有时,譬如在受到头部重击之后恢复意识的时候,就是一件好事。

力求变化可能是生产力提高的一个征兆(在一般意义上,他们几乎是同义词),这几乎永远是一件好事,如果社会的生产力停滞不前,多半不是因为人人都是爱迪生。相反是因为没有爱迪生。

在科技不发达的社会里,生产力上面的差异可能不是那么显著。在一个到处捡柴生火的游牧部落中,一个最好的捡柴禾者比最差的捡柴禾者能强多少呢?两倍吗?但是在操作像计算机这样复杂的的工具时,个体之间生产力的差异将是巨大的。

这些并不是新观念,Fred Brooks早在1974年就把它们写了下来,而他引用的研究成果发表于1968年。不过我认为Brooks还是低估了程序员之间的差异。Brooks是以代码行来描述生产力的:最好的程序员能在1/10的时间内解决问题。但是如果连问题都还没有给出呢?在程序世界的许多领域,最难得恰恰不是解决问题,而是要解决什么问题。想象力是无法量化的,但在实践中,就衡量生产力而言,占据支配地位的标准却是可以量化的代码行。

几乎所有领域的生产力都在提高,不过到目前为止,得到显著提高的领域为数有限。程序员之间的巨大差异看起来就是得到巨大提高的一个例子,不过我不认为这是写程序的固有特征。在所有领域,技术是放大生产力之间的差异的杠杆。我想在写程序上存在着特别多的技术杠杆。就当下来看,所有领域中杠杆都在变长,所以在越来越多的领域中,差异也会随着时间的推移越来越显著。公司的成功,甚或国家的成功,都取决于他们对于这种将要发生的,在效率方面差异所要采取的对策。

如果说在生产力上面的差异会随着技术而增长,那么随着时间的推移,最有效率的个体对整体做出的贡献也会不成比例的扩大。当1%的成员贡献了90%的产出时,把他们的效率拉到平均水平会使整体损失巨大。(不管是海盗出击,还是计划经济)

如果我们希望得到最大的产出,我们需要理解这些有着最高效率的人。什么是他们的驱动力?他们需要什么来完成他们的工作?如何识别他们?如何让他们为你工作?最后必然是这个问题,如何成为其中的一员?

不仅仅是钱



碰巧我认识几个超级黑客,于是我开始坐下并思考什么是他们的共同点。决定性的品质很可能是他们真的热爱编程。一般程序员写代码是为了讨生活。顶尖的黑客认为这是让他们得到乐趣的途径,更让人兴奋的是还会有人付钱给他们。

大多数时候人们认为顶尖的程序员对钱漠不关心,不幸这并不那么对。不过他们真正在乎的是他们正在做有趣的事情。为了这样的理由:能够赚足够多的钱,做任何想做的事,黑客们会被赚取巨大财富的主意吸引。一旦他们面对日常工作,他们就会更加关心他们要做什么,而不是能够得到多少报酬。

从经济学的角度看,你不需要向顶尖的黑客支付等同于他们身价的薪水,这是一个非常重要的事实。在生产力上,顶尖的程序员是一般人的数十倍甚至上百倍,他们却为自己得到了三倍的薪资而暗自高兴。后面我会提到,部分的原因是顶尖的程序员不清楚他们自己有多棒,同时对于他们来说,金钱也不是他们想要的最主要的东西。

什么是一个黑客真正希望拥有的?就像所有的手艺人那样,黑客最喜欢的是好的工具。有一句这样的话,好黑客绝不容忍差工具。对于那些构建在错误基础设施之上的项目,他们会简单得说不。


在我曾经工作过的一个创业团队当中,有一样东西是钉在我们的公告板上面的,那是一张IBM的广告。那是一张AS400 的图片,我想我能读到的标题就是“黑客不鸟它”[1]

当你决定在项目中使用什么基础设施时,不仅仅是作一个技术决定,同时也是一个社会学意义上的决定,并且后一个才是两者之中真正重要的决定。例如,你的公司决定写一个软件,看起来似乎用Java来做是一个谨慎的做法。但是在你选择编程语言的时候,你同时也是选择了一个社区。你能够雇佣的Java程序员可能不如那个使用Python的程序员,黑客的质量要比起你要选择的语言的要更加重要。并且实际上,那个使用Python而不是Java的家伙会告诉你他使用的语言(python)有多棒。


商业决定通常倾向于更流行的语言,因为它们把这些看作标准。它们不会把公司的未来赌在Betamax 上面。但是问题是语言不仅仅是个标准。如果你需要在网络上传输比特,那意味着使用TCP/IP。程序语言不仅仅是格式,而是一种表达的媒介。

我曾经读到Java已经取代Cobol成为最流行的语言。作为一个标准,你不可能再奢望更多。但是作为表达的媒介,你可以做得更好。在所有我能想到的最好的程序员中,我知道只有一个会自愿使用java。而所有这些人,没有人愿意在java上为Sun工作.

通常顶级的黑客坚持使用开源软件。不仅是它们更好,而且开源提供给他们更多的控制。好的黑客坚持控制,这是为什么他们是好的黑客的部分原因:当什么东西不对劲时,他们需要修正它。当你需要黑客们按照上面的方式去写软件的时候,对于黑客们要求他们使用的OS也应该如此时,不要感到惊讶。

数年以前,一个风险投资人朋友告诉我他正参与一个创业的团队,一切听上去很好。但是第二次我们谈到,他们决定在windows NT上面构建他们的软件 ,并且刚刚雇佣了一名非常有经验的NT开发者作为他们的CTO,我想这些家伙真是逊掉了。首先,这个CTO不可能是第一流的黑客,因为一名优秀的NT开发者会不自觉地倾向使用NT,我不能想象一个顶级的黑客会这样;其次,即使这个家伙足够棒,在使用NT的项目中,很难雇佣到一个优秀的开发者。[2]


终极边界


除了软件,对黑客来说最仰仗的工具就是他的办公室。大公司认为办公室空间的功能是等级的表示。不过黑客们是这样来使用他们的办公室的:办公室是思考的场所。如果是一家技术公司,他们思考的东西就是你的产品。所以,让黑客们工作在嘈杂混乱的环境下就像是一个空气中充满了煤烟的画室。

呆伯漫画 中总是以赞赏的态度提到小休息室。不过我认识的所有黑客对此都不屑一顾,被打断意味着阻止黑客们解决难题。如果希望在一间带着小休息室的办公室中作真正的工作,你有两个选择:在家工作,或者选择比其他人早或者比其他人迟,或者在周末,总之是没有其他人在的时候。那些公司难道没有看出这有什么不对劲么?办公室理应是帮助你工作的地方,而不是这就是你工作的地方。

像Cisco这样的公司总是自豪的宣称每个人,甚至是CEO,都有一个小休息室。但是他们并不是像他们自己想的那样前卫。显然他们还是把办公室空间看作等级的徽章。注意Cisco是以在家里开发的,很小的产品而著称,但是这些产品都来自对那些创业者的新技术的收购。这些创业者的信条是:黑客需要在安静的地方工作。

理解这些黑客们的需要有一家大公司,M$,我见过一张M$的招聘广告,上面是一个大大的门。这里的逻辑是,为我们工作,我们会给你个地方,你的确能够把工作完成。在大公司中,M$对于在提倡像在家里那样开发软件的理念是突出的。不是最好,但已经足够好。

如果公司希望黑客们有效率,它们应该关注一下黑客们在家里是怎么工作的。在家里,黑客们可以自己安排要做的事情,并将其中的绝大多数完成。而当黑客们在家里工作时,他们不会工作在嘈杂的,开放的空间中,他们是工作在门的后面。当他们需要费力思考时,他们工作在舒适的,周围有人的,有地方可以散步的环境中,而不是在停着许多车子的大停车场旁边的几个玻璃盒子中。当他们感觉疲倦时有沙发可以小憩,而不是在桌子旁边昏昏沉沉。在夜晚,这是 最主要的黑客时段,没有人拿着真空吸尘器咆哮,也没有会议和上帝禁止的集体反思乃至团队建设活动。当你望向他们的电脑时,你会巩固我先前说过的工具的观念,在工作上他们可能不得不使用java和windows,但是在家里,他们可以自己作主的地方,你很可能发现他们在使用Perl和Linux

实际上,那些关于Cobol和Java是最流行语言的统计数据可能是误导。如果我们想知道那些工具是最好的,我们应该考虑到的是黑客可以自由选择的工具。也就是黑客们自己的项目。当你问这个问题,你会发现开源OS已经占据决定性的市场份额,排名第一的语言则是Perl。


兴趣



有了好的工具,黑客们还希望有趣的项目。怎样让一个项目有趣?哦,那些公然的,性感的应用,比如偷飞机或者软件的特别作用是非常有趣的。只要准备迎接新奇技术的挑战,任何应用都是有趣的。事实上很难猜测黑客们喜好的问题,因为工作在那些无趣问题上的人通过发现新的解决方法,会使问题变得有趣。在ITA之前(Orbit上的软件 由他们完成),飞机票费用搜索可能是可以想到的最无趣的应用。不过ITA将问题换成更具雄心的描述方式之后,事情变得有趣了。

我认为相同的事情也发生在google身上,google建立时,传统智慧认为在门户中搜索是无聊的,不重要的。不过这些家伙不认为搜索是无趣的,这就是为什么它们做的这么好的原因。

这里是经理可以做出贡献的地方。就像父母对孩子说,我打赌你在10分钟内不能把房间打扫干净。好的管理者可以把问题重新定义的更加有趣。Steve Jobs在这方面好像特别擅长,部分的原因不过是他的高标准而已。在Mac之前有很多小的,便宜的电脑。他把问题重新定义为:做一个漂亮的。这可能比任何胡萝卜加大棒都更有效。

他们当然成功了,在Mac第一次面世时,你甚至不必开机就知道它到底有多好。从这个案例中你应该可以学到什么。就在几个星期前,我走在剑桥的街道上,在某人丢弃的垃圾中我发现了Mac的包装盒,我向里看了一眼,那不是一台Mac SE 吗!我把它带回家,插上电,然后它启动了。快乐的Macintosh标志,然后是finder 。天啊,就是这么简单,就像...google(sorry,不熟悉Mac,所以什么是Macintosh face? 我翻译成标志)

黑客们喜欢和高标准的人一起工作,但是仅仅严格要求是不够的。你还必须坚持正确的事情,通常这意味着你自己也必须是一名黑客。我偶尔可以看到如何管理程序员的文章。实际上这里有俩个主题:一个是自己是程序员时要做什么,另一个是你不是程序员时你要做什么。第二种情况可以简单的浓缩为一个词:放弃

问题并不是出在日常的管理上,好的黑客都是自我管理者。问题是,如果你不是黑客,你就不能辨别谁是好的黑客。类似的我们可以解释为什么美国的汽车都很丑陋。我称之为设计悖论,你可能认为我只要雇佣好的设计者就可以设计出漂亮的产品。但是没有好品味,你怎么才能辨识好的设计者呢?名义上你可以考察他的履历,但是仅仅是得过的奖项和曾经拥有的工作是不行的。因为在设计上,或者说在所有领域,那些被时髦和人云亦云驱使的人,是没有能力做一个合格的第三方的。 下面这样是行不通的:不了解什么是美,却希望通过控制流程来制造漂亮的事物。美国汽车的丑陋是因为美国的汽车公司是一帮没有品味的人在把持。

这个国家的很多人认为品味是飘忽的,甚至是反复无常的,但是两者都不对。出色的设计中,经理应该是公司产品的要求最高的使用者。如果你确实有不错的品味,Steve Jobs就做到了,你可以在满足自己的要求的同时,让最好的人甘心为你工作。

琐碎的小问题


非常容易分辨出什么问题是无趣的:那些不是宏大的,清楚的,困难的的问题,但是你必须一个个去解决的很琐碎的问题。为一个到处是bug的软件的写界面就是一件最差的事。为每个客户提供复杂的,病态要求的定制是另一个差的不能再差的事。对于一个黑客来说这不谛于千刀万剐。

琐碎的事的显著特征就是你不能从中学习。写一个编译器是有趣的,因为你从中学到了什么是编译器。而为到处是bug的软件的写界面却不能教会你任何东西。因为bug是必然会产生的[3]。这里不是说让一个顶尖的黑客尽量远离琐碎的问题,这也不仅仅是自我保护的本能。做琐碎的事情会让你变蠢,就像模特远离奶酪三明治一样,顶尖的黑客也会远离这种问题。

当然有时必然需要这种角色。并且由于供需比例,他们也会得到非常好的报酬。就公司而言,找一个顶尖的黑客来做这些乏味的工作的尝试是有可能成功的。你怎样才能做到呢?

这种情况会发生在一个地方,就是在创业者当中。在我们创业时,我们找到了Robert Morris 做系统管理员。是不是感觉就像滚石乐队在酒吧里做善事,所以你不可能雇佣到这样的天才。但是他们会为他们自己的公司吃任何苦头。[4]

大一点的公司可以通过拆分公司来解决这个问题。他们可以成立单独的R&D部门来雇用聪明的家伙,好让他们不必直接面对刁钻的客户[5]。在这种情形下,研究部门相当于一座宝矿,产生公司其他部门使用的新奇主意。

不过你可能不需要如此极端。自下至顶编程法 建议的另一种分割公司的方法:让聪明人成为工具制造人。如果你的公司制造生产其他什么东西的软件,那就让一小群人来做,然后用这些工具软件来写你的应用。这种方法可以让聪明的家伙为你完成98%的代码,同时又可以像传统的研究部门那样,让他们几乎和用户绝缘。工具制造者的确有用户,不过面对的是公司里的开发者。[6]

如果M$使用这种发式,他们的软件就不会到处是安全漏洞。正是因为不那么聪明的家伙是不太会考虑底层的操作,比如内存分配。所以不要用C来直接写Word,应该用像搭建Lego的积木那样的Word语言。(Duplo ,我相信这是一个太过于技术的术语)(不知道这里的Word是不是指得M$的Word)

群聚


除了有趣的事情,黑客们最欣赏的是另一个好家伙。顶尖的黑客倾向于聚集一处——有时非常壮观,譬如在施乐帕洛阿尔托研究中心 。所以所能营造出来上佳的氛围是和你能招徕到的黑客是成比例的。群聚的含义就是这样的一个氛围。所以赢者通吃,在任意时段,只有那么10到20个地方是黑客们希望工作的地方。如果不在其中,你不会招揽到少数几个黑客,而是零个。

是否拥有顶级黑客,仅就此而言,已经足够让你的公司成功的假设,对于google和ITA而言,两个目前的最炙手可热的地方,这是正确的。(译者:这是在2004,ITA是什么东西 ?)但是这救不了Thinking Mchines 和施乐。Sun有一段时间做的很好,但是他们的商业模式在飞速的走下坡路,在这种情况下,甚至是最好的黑客也不能拯救你。

我认为在其他条件等同的情况下,能吸引到黑客是公司的一项巨大的优势。可能有人对此不同意,在我们于90年代开办VC企业的时候,一些人告诉我们软件公司不会通过写伟大的软件获胜,但是品牌和渠道能帮助他们成为好买卖。

他们好像很相信这一点,我想我明白为什么。我认为许多VCs在寻找下一个M$,至少是无意识的。当然M$就是你的模型,你不应寻找希望通过写好软件来获胜的公司。但是VCs寻找下一个M$是一个错误,因为没有创业公司会成为下一个M$,除非是其他人恰巧在正确的时刻屈服,转而去做下一个IBM。

把M$当作模型是一个错误,因为他们整个的文化继承于一个幸运的突破点。M$是一个错误数据,如果你把M$抛在脑后,你会发现在市场上还是好的产品更容易成功。VCs们更应该关注下一个Apple,下一个Google

我认为Bill Gates很清楚这一点,让他真正担忧不是Google的品牌,而是Google有着更好的黑客[7]。

辨识


那么谁是顶尖黑客呢?当你遇到一个时你怎么知道他就是呢?这非常困难。甚至是黑客们自己也不能辨别。我现在可以非常肯定我的朋友Trevor Blackwell 是一顶级黑客。你可能在slashdot上面 读到过他曾经做出来他自己的赛格威 电动车。令人印象深刻的是它在一天之内就写出了所有的软件(顺便提一句,他用的是python)

对Trevor 而言,这是非常平常的。不过我第一次碰到他的时候,我想这家伙真是一个完完全全的白痴。他站在Robert Morris的办公室中,嘴里胡乱的说着什么,我还能记得在他后面,Robert做着夸张的动作试图把这个怪人赶出办公室,好和我一起去吃午饭。 Robert说他一开始也错误的判断了Trevor。当Robert第一次碰到Trevor时,Trevor刚刚开始一项计划,他随身携带这些带索引的小卡片,并把个人生活的每一个方面都记在上面。Trevor那时刚从加拿大来,带着很浓的加拿大口音和他那mullet 发型。(这个找不到对应的中文词^^,hacker就是hacker)

问题在于,黑客是这样的混合体:除了他们那不善于社交的名声之外,通常他们还会付出很大的努力使得自己看起来聪慧。当我还个高中生时,我时常在MIT人工智能实验室旁边晃荡。那的确是压抑的感觉,每个人说话说得快极了。不过一段时间之后,我就发现了其中的诀窍。你的思维不需要很快,不过需要用两倍的话语来表达任何事情。

从这些纷杂的情形里传出来到信号就是,当你碰到好的黑客时认出他们是很困难的。我自己直到今天还不能辨别。你也不能从他们的简历中辨别它们。看起来唯一的途径就是和一个黑客一起工作一段时间。

这也就是高科技区域通常产生于大学的周围,这里主要是因为学生而不是教授。创业者成长在大学的周围是因为大学把这些有希望的年轻人带到一起,让他们工作在同一个项目上。一个聪明人找到了另一个,于是两个人就一起建起了他们自己的项目。

除了和他们一起工作就不能辨识好的黑客的假设对于黑客本人也适用,黑客们通常都意识不到自己有多棒。相比而言,这在其他大多数领域要容易得多。百米赛跑只需要10秒就可以知晓跑得最快的那个。甚至在数学上面哪些是公认的难题以及它们的最佳解决方案似乎也有一致的意见。但是做黑客就好像写作。谁能说在两部小说当中有一个更好呢?当然作者本人除外。

不过黑客在一起时,至少其他的家伙知道你是黑客。因为黑客并不是小说家,黑客在项目上相互协作。当你在网络上和别人较劲时,你很快会意识到还击是格外困难的。(When you get to hit a few difficult problems over the net at someone, you learn pretty quickly how hard they hit them back.)但是黑客们不能在工作中看到自己,如果你问一个顶级黑客他本人有多好,他一定会回答,我不知道。他这并不是在自谦,他是真的不知道。

除了那些我们确实在一起工作的人,其他的我们都不熟悉。这就导致了这样奇怪的情形:我们不知道谁应该是我们的英雄。那些赫赫有名的黑客通常只在特定的小圈子里有享有盛名。(The hackers who become famous tend to become famous by random accidents of PR. )通常当我需要给出顶级黑客例子的时候,我真的为很难。首先想到的肯定我认识的那些人,但是这样似乎有点眼界太小的意思。也许我应该给出像Richard Stallman,Linus Torvalds,Alan Kay这样有名的例子。但是我对于这些家伙是不是顶级的黑客一点没有底,因为我从来没有和他们在一起工作过。

如果黑客世界中有一个Michal Jordon,没有人会知道,包括他自己。(这是什么鬼意思)

养成


最后,关于黑客所有人都会感兴趣的问题是:如何才能成为一个顶级黑客?我不太确信你是否能成为其中一员。但是可以确信能够做点什么让你自己变得更蠢一点,如果你能让自己变蠢,你也很可能让自己变得更聪明。

成为一个好的黑客的关键是做你喜欢的工作。当我回想起那些我认识的顶尖黑客,他们共性是让他们做不想做的事情将是极端困难的。我不清楚这是原因还是结果,亦或二者兼具。

把事情做好的前提是热爱它,也就是你热爱什么东西你就会有持续hacking的动力。尝试去找在你14岁时迫不及待编程的感觉。如果你觉得现在的工作让你的大脑僵化,那么事实可能就是如此。

最好的黑客肯定是聪明的,但是其它很多领域最好的人也是聪明的人。那么对于黑客有什么是他们独特的品质呢?我问过一些朋友,他们首先提到的就是好奇心。不过我总是假定所有的聪明人都是好奇的——好奇是知识的自然延伸。但是明显的黑客特别好奇,特别是在事物如何工作方面。这就是意义所在,因为程序的绝大部分就是描述事情是如何运作的。

几个朋友提到黑客的能力在于专注——他们的能力就是,有人说的好,“把脑袋当中其他的一切杂念摒除”。我当然也很清楚这一点。我甚至听几个黑客说过,在没有喝掉半打啤酒之前他们是根本没有办法写程序的。所以hacking可能是在专注上是需要一些特别的能力的。可能顶尖的黑客在他们的大脑中可以容纳相当大的上下文,所以在他们看到一行行的代码是,他们不仅仅是看到了一行,而是整个程序。John Mcphee在写道Bill Bradley之所以是一个成功的篮球运动员时,部分的要归因于Bill那不同寻常的周围视野,“完美的”视野意味着水平47度的周围视野,Bill是70度,当他看像地板时他也能看见篮球。也许顶尖的黑客也有类似的与生俱来的能力。(我使用非常浓密的语言来欺骗,这会使我在法庭退缩)(I cheat by using a very dense language, which shrinks the court天啊,这又是什么鬼意思)

这也可以解释很什么需要一个个单独的房间,对于在小房间里工作,也许从来不关注细节,管设备的人没有任何概念,不过黑客倾向于让自己的脑袋处于混乱的状态。(如果哪个孤僻症的谣言是真的,Bill对此显然非常了解)(是指Bill Gates?)

在顶尖黑客和一般意义上的聪明人之间,我注意到的一个区别是,黑客们通常都是政治错误的。好黑客之间心灵相通的奥秘,在他们很了解对方的时候,会相互表达对于公众来说是非常颠覆性的观点。我能看到的,为什么政治错误是编程上的一个好品质:程序是复杂的,在好的程序员手中尤其这样,非常灵活。在这种情形下,挑战假设就是一个很好的习惯了。

你能培养这些品质么?我不知道,至少你可以加强他们。这里我有一个良方。如果你希望自己成为一个顶尖黑客,尝试着对自己作这些事情吧:绝不工作在无聊的项目上(除非你真的没饭吃),作为报答,你也决不能允许自己做事只做一半。我认识的所有顶尖黑客都会把一票干完,虽然有时他们只是别无选择。

脚注



[1]平心而论,我不得不说IBM做硬件还是相当好的,我就是在IBM笔记本上写这篇文章的。
[2]他们的确走向了失败,几个月之后他们关门大吉了事。
[3]我想这也是人们通常所说的“生命的意义”。表面上看,这看起来很奇怪。生命不是一种表达;怎样才能有意义?但是保证品质会感觉更有意义。在一个写编译器的项目上,你不得不解决很多问题,但是所有的问题都属于一类,看起来都有相同的信号。在那些随机的产生问题的情况下,这好比是噪音。
[4]爱因斯坦曾经设计过电冰箱(他有股票)
[5]很难说什么是计算机世界里的研究,但是粗略可以等同于:那些没有用户的软件。
我不认为最好的黑客,就像公众认为的那样,倾向于工作在研究部门。我认为大部分原因是,不必和产品经理在一起开三个小时的会,来讨论第13.27条,即整合南韩版本的问题。
[6]在相当长的一段时间之内,相同的问题也发生在建筑界。几百年前建造房屋时,建筑师一切从头做起。慢慢的有人开始使用已经由别人造好的模块来构建房屋。这就像DTP 的发布,给了人们自由和损失惨重基础上的经验,但是显然这更有效。(不知道有什么典故)
[7]比起Netscape,Google是M$的真正威胁。也许是有史以来最危险的。不仅是他们决定对抗,在他们工作列表上,他们宣称一个“核心价值”是“不做恶”。从买豆油的公司到采矿设备公司,这样的宣言都不仅仅是古怪可以形容的了。我想计算机世界的所有人都知道谁宣布战争开始了。(这是在2004年)

致谢:感谢Jessica Livingston, Robert Morris, and Sarah Harlin审阅了这个讲稿的早期版本



http://www.itconversations.com/shows/detail188.html

读后感:
(原谅我既有译者按,又有译后感。不过既然我付出了劳动,总要让我表达自己的意见吧^^)
1.个人觉得这篇essay的风格还是正统硅谷风格的文章,或者说,介于黑客(hacker)和奇客(geek)之间,更倾向越黑客一点。虽然作者一直说的是黑客,不过我想黑客是信奉do it now的。表达的思想虽然有点激进,不过不妨碍他说出了很多事实。(在纠正人心上,矫弯必过正。)特别是既然在代码上不能强过你们,那么更要说点什么了。
2.前面说个人经历,我想在稍微说一点。就在最近几个月,我见识了:



  • 在你debug一个下午,还在徒劳的寻找什么出错了的时候,别人只需要10分钟,再注释点几行code后,一切都正常了。是的,快速修改code的能力,文章里说黑客坚持控制,我原来也试图搞清楚一切,但是这样在出问题时你往往不能fix it。我想文章还说到了不仅仅看到了那一行code,这就是问题所在,基础的差异。
  • 在别人说要需要修改代码,你花了一个星期去研究,还在各种纷繁复杂得class中试图搞清楚问题到底在哪里。别人去只花了2个小时,就了解了提出需求的人在想什么。然后快速定位了代码,虽然那些我都看过。是的,修改代码有时就像解数学题,问题面前除了排除法就是一片空白。我真是奇怪在初中是解几何题时的那种感觉那里去了。是的,这些已经不能说经验或者基础了,的确需要灵感。需要理解别人的表述风格,code的风格。一种语言就是一种表达的媒介。
  • 还有在两个星期里反复看code,前一个星期也是空白,然后写code,然后改来改去,最后只需要200行就OK了
呵呵,距离文中的黑客我恐怕只能想想了...

星期一, 十二月 31, 2007

[读书]Steven Wozniak电子小孩

按:这本来是在公司里写给几个哥们的mail,怎么也是2007年最后一天,决定就把它放上来了

今天是2007年最后一天,明天开始放假。
接近下班,闲来无事,还记得我说的公司创始人的故事。就从Apple的Woz开始把
买了iWoz很久,一直没有看,以前大家说Wozniak是“硅谷好人”,硅谷成功的人有很多,不过被称为硅谷好人的好像只有Woz了,现在在San Jose还有一条街道叫Woz街

Woz是硅谷很早的居民了,大约60年代就成长在硅谷了,只不过那时候硅谷还没有成为Hi-Tech的心脏。

按照Woz自己的说法,大约在5、6岁时他的工程师父亲就告诉了他电子,原子的知识。然后是电阻,后来就是晶体管了。而在他的小学初中时期,从3年级开始,除了一年外,每一年他都参加了电子设计竞赛。大约在11岁就拿到了业余无线电的执照 ,这和他老爸一起拿得。Woz自己说他在大学时IQ已经200多,老师都责怪他不好好学习数学和物理。颇有点“若个当年万户侯”的感慨

毫无疑问,Woz的工程师父亲对他的影响至关重要,尽管后来开始酗酒。不过美国在60年代几项发动全民的浩大活动对美国在90年代经济的重新崛起具有决定性的影响。60年代婴儿潮出生的人大多赶上了这些活动,不可以想象,没有如此数量的工程师和工程师文化,可以出现硅谷。

今天中国的嫦娥计划,大飞机计划,水利水电工程还有跨海大桥计划,应该用意也颇在此。(国家大就是好啊,日本人想捣腾也没地方,欧盟就不说了,除了在电信产业中国人挺了他们一把,剩下来的就是空客公司了)


不过还是应该看到不同处,美国人在60年代末,70年代初遭遇了越战,也就是Woz在青春期的时候,由此产生了嬉皮士的文化,Woz在书中也提到了嬉皮士,好像意思是说他们精神相通(?),区别在于Woz不打算吸毒。显然Woz很是羡慕这些人,不过Woz还不能算作其中一个。但是嬉皮士文化的影响就是把人们从纳粹式的宏大抱负中解脱出来,Woz之所以是一个工程师而不是科学家,太半在此。 而Woz以及现在大受赞赏的大部分hi-tech公司的工程师文化都收益与此。

看过《In The name of father》的人,刘易斯一开始加入的那个小团体就给我留下了深刻的印象,就像看到那些留着长头发的面目和善的青年男子给我的感觉一样,特别的亲切,特别的人性化。虽然社会的进步不能指望这些人,不过在拯救人心,散发理想主义光辉,(不是前面说的纳粹是抱负,而是积极并且实际的主张),作用是非常巨大的。但是中国的今天,无疑商业化色彩太浓洌一点,需要什么才能让最优秀的头脑向纯粹智性和纯粹理性和方面靠拢是个问题。就好像keso念念不忘的“科技是一种信仰”

说了一些背景和感想,再来说Woz,看他的传记,Woz号称“好人”,不过他的性格里面偏执狂的倾向非常明显,如果不是因为IQ过高和过于shame(不过这两者好像是一回事),我恐怕他就不能被称为说是好人了。但是Woz无疑是个天才,硬件上面的天才,电子学的天才,工程师的天才。

我个人觉得,没有Woz Apple肯定不会成为Apple,Jobs应该庆幸自己遇到了Woz,虽然没有Jobs,apple不会像那时和现在这么成功,伟大的公司。不过,没有Woz,Apple根本无从谈起,连产生都不会产生。最坏的结果不过是fairchild的那样了,Jobs?也许会成为一个成功的人,而不会是现在这个Jobs。
之所以提到这个,是因为我看到一些人随便就想复制奇迹,野心勃勃的就可以做一个Jobs和Apple,认为presentation比什么都重要,其实成功的商人是需要一个平台的,包括Intel的格罗夫。相比之下,Bill Gates是一个另类。这也是为什么我更服气Gates一点。成功是没有办法复制的,真正cool的人就是cool

所以我觉得现在Jobs对待Woz的态度就有一点兄弟的样子,似乎拿Once upon a times in Americ兄弟之情来比如最合适不过,愈是愿意伤害的人愈是自己的兄弟,不过Woz看着兄弟发大财,虽然生性豁达,不过也还是有点酸葡萄的意思。方博士在序言里提到Woz命名这本书叫iWoz,还是很认同Apple的文化,这是一种委婉的说法。就好像Woz在多年以前看到的那些嬉皮士那样,"hi,哥们,再喝一杯怎么样
"。一切都没有改变,只有时间在流逝。



好了,废话了这么多,意思就是大家有时间把这本书找来看一看《iWoz》

(那个时候的berkelay好像还不时非常好的学校),

星期日, 十二月 23, 2007

[web2.0]谢文的新年讲话,传统的力量

“又是一年春来到”,年关将到,难免有人坐而论道,这不,谢文大佬和keso老兄再有麦田兄弟又打开话闸子了。

谢文


第一次发现xiewen是源于blogsphere上面对他的一个ppt的讨论,那是我还混在学校,还有时间,基本上donews那时还是我每天必上的地方。说句实在话,给我的启发还是非常大的,基本上对于Myspace的关注也在于那个时候。以前只知道流量很大,却不知道可以到今天这个状况,虽然主角换成了 FB。后来我就关注起了这个老兄,逐渐发现xiewen的观点非常的熨贴,无论体系还是前瞻性都非常好。另外,我还知道了xiewen去过了哥伦比亚,而且是在1995年,啊哈,哥伦比亚的社会学基本上全美是数的着得应该,可见背景和传统的力量。(下面还会说到这个话题)

谈话和虚拟经济


不过,这次收获好象不如以前大,启发也比不上以前。不过还是可以看出xiewen最看中的是商业模式,他(包括所有的实践者)思考的角度应该主要是从商业角度出发的,也就是说,怎么样才能赚到钱。这其实是我非常困惑的问题,虚拟化的基础上的赚钱,谢文说是“做互联网”,有什么一定需要Internet,离了Internet就不行了呢?
在我看来,Internet基本上是一种新媒体,还没有到拓展人类生存的地步。那么Internet现在只能发挥媒体的作用。媒体的作用基本上就是信息传播,不会产生实际价值。所以基本上的收入来源是Ads,这样就养育了Google这样的Monster,而且我恐怕现在所有的Internet公司主要是以广告,或者以信息附加分成的那部分形式体现的Ads作为收入的主要来源的。
虚拟经济会发展起来么?这取决于虚拟消费的存在和增长。虚拟消费能够满足什么样的需求呢?我们对于美食的渴望来源自我们的胃这样的生理需求,虚拟消费呢?我觉得肯定不是类似于qq的增值品,特别不应该是那些没有得到主流意志认可的价值观。

时间和Ecosystem


所以还是坚持这样的一个观点,一切需要时间。譬如说,现在我会愿意100元/年的价格来满足我的网络声誉和ID的维护,也就是我的blog如果需要这么大的成本我是愿意的。
什么时候才是虚拟经济能够真正能够成功的时候?第一肯定是基本的生活需求不再是威胁,也就是说,大量的闲人,社会产品极大丰富,接下来就是精神生活了。其次,要等一代人的时间,也就是20年,谢文说2010年,我认为还是太乐观了,毕竟到现在Internet普及只是20年,这一代人还没有生活在Internet之下。中国的宽带普及我觉得也不过3、4年而已。
不过xiewen,keso讨论给我的启发意义在于,在这样的环境下,如何作网站,从商业模式和社会学的角度去看待要解决的问题。(可以看他们对FB的Beacon的讨论)
一定有用户黏度,但是满足了需求就要让他们离开。我觉得30mins/week比较适合。基本上这个也是我在douban上的时间,del.icio.us要短一点,不过这个有点不一样。(另:del.icio.us的search功能在对特定领域的search很有用,比如AI,类似现象发生在wikipedia,而且wiki的时间也在这个数)

传统的力量


从这里,也可以看到传统的力量,Web2.0从一开始就有着社会学,心理学的影响,想想破窗理论,六度分离,马太效应等等,而不是Hacker/UNIX的流派。(其实包括Emacs的心理医生可以看作一个root,只不过还只是涓涓细流,特别是在AI发展的让人如此失望的背景之下),我个人这个主要的原因是在于SNS是针对大众的,是一种大众消费品,有人的地方也就肯定有社会学了。
不过,大部分讨论Web2.0还是从另一个Root来看的,Tech/Computer,这个原因自然是IT技术和Internet是Web2.0的基础,最初的那班人都是以技术人才出现的。不管是FB的platform还是OpenSocial还是data,algorithm,这些似乎才是他们关注的焦点。
行文至此,我也无话可说了 ^o^