I said that Heritage / 1 wanted to be a computer "old" but "useful." Without emgargo, and even if the hardware were to work reliably, Heritage/1presenta serious limitations even within the framework of "his age" (1966-1972).
The first limitation is the purely personal (single taxpayers) of this project, which limits the growing of software: even if I try I can not get far developing it all, from the operating system to applications, to hit assembly and without the slightest support previous code. Carrying
Open Source code is not possible at this stage since the architecture of Heritage / 1 is too early to existing Open Source code, for example, Heritage / 1 does not support Virtual Memory (which is that can be repaired in the future by building an MMU to achieve inserted into the existing architecture.) An alternative would be to port code "ancestral", but this is a technical rather than archaeological work for other hard in both directions.
Consequently, I can not make utilitarianism a central objective of the project. Rather, utilitarianism is a guide for experimentation in the field of Software. My applications are hopelessly primitive, but must (of course) be designed to work "compelling" as, for example, the database management. The ultimate goal is not to use the machine to solve day-to-day but experience with application development "real life" within the historical context of Heritage / 1 (1966-1972).
the only way to get away (as well as the minis came in the 70s) would be collaboration between hundreds of programmers over the Internet, ie converting Heritage / 1 on a collaborative project. But for that H1 should be sufficiently attractive and do not think that's the case.
The initial question can not therefore be answered with too much optimism. The machine is designed to perform useful work, but in practice will be as useful as my patience will allow.
0 comments:
Post a Comment