在主流计算中，有一件事没有改变，那就是分级文件系统。在我看来，这是一种耻辱，因为在20世纪80年代末和90年代，一些工作已经完成，以设计更适合现代面向对象操作系统的新型文件系统——那些从头开始就是面向对象的操作系统。

OO操作系统倾向于具有可扩展且灵活的平面对象存储。我认为EROS项目就是围绕这个想法建立的;PenPoint操作系统是20世纪90年代的面向对象操作系统;Amazon S3当然是当代的平面对象存储。

在面向对象的平面文件系统中，至少有两个想法是我特别喜欢的:

The entire disk was essentially swap space. Objects exist in memory, get paged out when they are not needed, and brought back in when they are. There's no need for a hierarchical filesystem that's separate from virtual memory. Programs are "always running," in a sense. A flat file/object store allows content to be indexed and searched, rather than forcing the user to decide -- ahead of time -- where the content will live in relation to other content and what its name shall be. A hierarchical system could be built on top of the flat storage, but it's not required.

正如Alan Cooper在他的书《About Face》中所述，分层文件系统是一个拼凑物，是为20世纪60年代和70年代内存和磁盘存储有限的计算机设计的。可悲的是，Windows和Unix的流行保证了分层文件系统的主导地位。

如果我们作为一个团体认真地回答这个问题。 不幸的是，我相信我们需要的不仅仅是一串随机的善意的帖子! 我知道，这听起来很无聊，但经常把事情做完才是!

We Write a list of powerful ideas in the area of computing Maybe we should define a few categories to separate each one because videoconference somehow does not fit well with object oriented programming. Seeing ideas by categories makes it easier to generate them without redundancy. It's too easy to sidetrack in teleportation if quantum computing is not kept away from flying cars. Try to attribute each of them a date This will settle the before/after 1980 and restrict debate about each idea to its own. It will be fun to dig for earliest reference, first known implementation, etc. Plus this will allow people like me who were 2 years old in 1980 to have a better idea of what was common programming knowledge in 1980 (nothing beats being there at the time) Try to attribute each of them the current state of their implementation Ok, some idea were sci-fi in 1850, with early development in the 1970 and serious improvement breakthrough in the 1990. Some ideas are just starting to get around. Some are almost forgotten. Probably the wiki thing is a good idea. I think this could really get somewhere if slightly organized. I did not check, but maybe this whole thing already exist already on the net (I usually find that if you think about something, someone already did it). What do you think ? Cheers !

在操作系统核心开发中使用函数式编程/语言。

采用面向对象。

这个想法早前就出现了(例如Simula)，但在20世纪90年代成为主流。(恕我直言，它最大的好处之一是在开发人员之间提供了一个通用的词汇表，所以它的广泛采用使它更有价值。)

HTM系统(分层时态记忆)。

人工智能的一种新方法，由杰夫·霍金斯通过《论智能》一书发起。

现在是一家名为Numenta的公司，通过开发“真正的”人工智能来测试这些想法，并邀请社区通过sdk使用该系统来参与。

它更多的是从头开始构建机器智能，而不是试图模仿人类的推理。

收缩包装软件

在1980年以前，软件大多是专门编写的。如果你经营一家企业，想要计算机化，你通常会有一台计算机、编译器和数据库，然后自己写东西。业务软件通常是为适应业务实践而编写的。这并不是说没有固定的软件(我在1980年之前使用SPSS)，但这不是常态，我看到的往往是基础设施和研究软件。

现在，你可以去电脑商店，在货架上找到经营小生意所需的一切。它的设计并不是为了无缝地适应您曾经拥有的任何实践，但是一旦您学会或多或少地按照它的工作流程工作，它就会很好地工作。像SAP和仁科(PeopleSoft)这样的大企业比过去更接近于收缩包装。

这并不是一个彻底的突破，但在1980年之后，有一个非常明确的转变，从昂贵的定制软件到低成本的现成软件，灵活性从软件转移到业务流程。

它还影响了软件的经济性。定制软件解决方案可以盈利，但无法规模化。你只能向一个客户收取这么多钱，你不能把同样的东西卖给多个客户。使用收缩包装软件，你可以卖出很多很多相同的东西，在一个非常大的销售基础上摊销开发成本。(你必须提供支持，但这是有限度的。就当这是销售软件的边际成本吧。)

Theoretically, where there are big winners from a change, there are going to be losers. So far, the business of software has kept expanding, so that as areas become commoditized other areas open up. This is likely to come to an end sometime, and moderately talented developers will find themselves in a real crunch, unable to work for the big boys and crowded out of the market. (This presumably happens for other fields; I suspect the demand for accountants is much smaller than it would be without QuickBooks and the like.)