@article{Wirth1995a,
  author    = {Niklaus Wirth},
  title     = {{A plea for lean software}},
  journal   = {IEEE Computer},
  pages     = {64--68},
  year      = 1995,
  month     = 2,
  volume    = {28},
  number    = {2},
  url= {https://metager.to/0x-9a},
  urldate={2017-11-10},
  annote    = {http://www.oberon2005.ru/paper/nw1995-02e.pdf
              Abstract:
              ---------
              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.

              ...
              Increasingly, people seem to
              misinterpret complexity as
              sophistication, which is baffling---the
              incomprehensible should cause
              suspicion rather than admiration.
              Possibly this trend results from a
              mistaken belief that using a somewhat
              mysterious device confers an aura of
              power on the user.},
  issn      = {0018-9162},
}

{"_id":"aBf9aZSGFNxxotdPg","bibbaseid":"wirth-apleaforleansoftware-1995","downloads":0,"creationDate":"2017-12-10T11:20:57.939Z","title":"A plea for lean software","author_short":["Wirth, N."],"year":1995,"bibtype":"article","biburl":"http://ddi.uni-wuppertal.de/forschung/Komplett.bib","bibdata":{"bibtype":"article","type":"article","author":[{"firstnames":["Niklaus"],"propositions":[],"lastnames":["Wirth"],"suffixes":[]}],"title":"A plea for lean software","journal":"IEEE Computer","pages":"64--68","year":"1995","month":"2","volume":"28","number":"2","url":"https://metager.to/0x-9a","urldate":"2017-11-10","annote":"http://www.oberon2005.ru/paper/nw1995-02e.pdf Abstract: --------- 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. ... Increasingly, people seem to misinterpret complexity as sophistication, which is baffling---the incomprehensible should cause suspicion rather than admiration. Possibly this trend results from a mistaken belief that using a somewhat mysterious device confers an aura of power on the user.","issn":"0018-9162","bibtex":"@article{Wirth1995a,\n author = {Niklaus Wirth},\n title = {{A plea for lean software}},\n journal = {IEEE Computer},\n pages = {64--68},\n year = 1995,\n month = 2,\n volume = {28},\n number = {2},\n url= {https://metager.to/0x-9a},\n urldate={2017-11-10},\n annote = {http://www.oberon2005.ru/paper/nw1995-02e.pdf\n Abstract:\n ---------\n Memory requirements of today's\n workstations typically jump\n substantially--from several to many\n megabytes--whenever there's a new\n software release. When demand surpasses\n capacity, it's time to buy add-on memory.\n When the system has no more\n extensibility, it's time to buy a new,\n more powerful workstation. Do increased\n performance and functionality keep pace\n with the increased demand for resources?\n Mostly the answer is no. The author\n contends that software's girth has\n surpassed its functionality, largely\n because hardware advances make this\n possible. He maintains that the way to\n streamline software lies in disciplined\n methodologies and a return to the\n essentials. He explores the reasons\n behind software's increasing heft and\n relates the history of Project Oberon\n as an example of how software should be\n built. Oberon's primary goal was to show\n that software can be developed with a\n fraction of the memory capacity and\n processor power usually required without\n sacrificing flexibility, functionality,\n or user convenience. The Oberon system\n has been in use since 1989, serving\n purposes that include document\n preparation, software development, and\n computer-aided design of electronic\n circuits, among many others. The system\n includes storage management, a file\n system, a window display manager, a\n network with servers, a compiler, and\n text, graphics, and document editors.\n\n ...\n Increasingly, people seem to\n misinterpret complexity as\n sophistication, which is baffling---the\n incomprehensible should cause\n suspicion rather than admiration.\n Possibly this trend results from a\n mistaken belief that using a somewhat\n mysterious device confers an aura of\n power on the user.},\n issn = {0018-9162},\n}\n\n","author_short":["Wirth, N."],"key":"Wirth1995a","id":"Wirth1995a","bibbaseid":"wirth-apleaforleansoftware-1995","role":"author","urls":{"Paper":"https://metager.to/0x-9a"},"downloads":0,"html":""},"search_terms":["plea","lean","software","wirth"],"keywords":[],"authorIDs":[],"dataSources":["6BepyHGwnjChmJuia"]}