Programming in Oberon: steps beyond Pascal and Modula
Programming in Oberon: steps beyond Pascal and Modula
Project Oberon: the design of an operating system and compiler
Project Oberon: the design of an operating system and compiler
Computer
Simplifying array processing languages
APL '98 Proceedings of the APL98 conference on Array processing language
Issues in agent-oriented software engineering
First international workshop, AOSE 2000 on Agent-oriented software engineering
Lightweight Plug-In-Based Application Development
NODe '02 Revised Papers from the International Conference NetObjectDays on Objects, Components, Architectures, Services, and Applications for a Networked World
Preface: how to approach the virtual shared memory paradigm
Virtual shared memory for distributed architectures
IEEE Spectrum
Proceedings of the third ACM SIGPLAN conference on History of programming languages
An empirical study of cycles among classes in Java
Empirical Software Engineering
Distributed measurement systems: An object-oriented architecture and a case study
Computer Standards & Interfaces
WLGauge: a web link gauge to measure the quality of external www links
ICWE'03 Proceedings of the 2003 international conference on Web engineering
Iterative software engineering for multiagent systems: the MASSIVE method
Iterative software engineering for multiagent systems: the MASSIVE method
Beyond simulation: designing for uncertainty and robust solutions
SpringSim '10 Proceedings of the 2010 Spring Simulation Multiconference
Green challenges to system software in data centers
Frontiers of Computer Science in China
A survey of the practice of computational science
State of the Practice Reports
Mobile application research and development: the African context
Proceedings of the 2nd ACM Symposium on Computing for Development
Hi-index | 4.10 |
Memory requirements of today's workstations typically jump substantially--from several to many megabytes--whenever there's a new software release. When demand surpasses capacity, it's time to buy add-on memory. When the system has no more extensibility, it's time to buy a new, more powerful workstation. Do increased performance and functionality keep pace with the increased demand for resources? Mostly the answer is no. The author contends that software's girth has surpassed its functionality, largely because hardware advances make this possible. He maintains that the way to streamline software lies in disciplined methodologies and a return to the essentials. He explores the reasons behind software's increasing heft and relates the history of Project Oberon as an example of how software should be built. Oberon's primary goal was to show that software can be developed with a fraction of the memory capacity and processor power usually required without sacrificing flexibility, functionality, or user convenience. The Oberon system has been in use since 1989, serving purposes that include document preparation, software development, and computer-aided design of electronic circuits, among many others. The system includes storage management, a file system, a window display manager, a network with servers, a compiler, and text, graphics, and document editors.