What Makes the History of Software Hard

Total Page:16

File Type:pdf, Size:1020Kb

What Makes the History of Software Hard What Makes the History of Software Hard Michael S. Mahoney Princeton University History of commitments constrains choice. Narrow incentives and opportunities motivate choice. —Rob Kling and Walt Scacchi1 We never have a clean slate. Whatever new we do must make it possible for people to make a transition from old tools and ideas to new. —Bjarne Stroustrup2 Creating software for work in the world has meant translating into computational models the knowledge and practices of the people who have been doing that work without computers. What people know and do reflects their particular historical experience, which also shapes decisions about what can be automated and how. Software thus involves many histories and a variety of sources to be read in new ways. This article originally appeared in L. Bo¨szo¨rmenyi, most current, is in that sense ‘‘legacy’’ soft- ed., MEDICHI 2007—Methodic and Didactic ware. That is what makes the history of Challenges of the History of Informatics, software hard, and it is why the history of Austrian Computer Society (OCG), Klagenfurt, software matters to the current practitioner. Austria, 178 pp. The Austrian Computer Society (OCG) has kindly granted permission for an edited Decentering the machine version to be published by the Annals.3 Until recently, the history of computing has focused largely on the machines them- The history of software is the history of how selves, tracing the path by which the electronic various communities of practitioners have put digital computer emerged from a long history their portion of the world into the computer. of efforts to mechanize calculation and then That has meant translating their experience evolved into a variety of increasingly complex and understanding of the world into compu- forms in response to the possibilities opened tational models, which in turn has meant by the transistor, the integrated circuit, and creating new ways of thinking about the world magnetic and optical media of ever greater computationally and devising new tools for capacity. This focus has led to a familiar expressing that thinking in the form of narrative (see Figure 1), which begins with working programs. It has also meant deciding, the abacus and then follows a by now familiar in each realm of practice, which aspects of sequence of devices—mechanical and electro- experience can be computed and which mechanical, analog and digital—all converg- cannot, and establishing a balance between ing on ENIAC, or more broadly on the several them. Thus, the models and tools that consti- electronic devices of a similar nature con- tute software reflect the histories of the ceived and built at the time. From ENIAC the communities that created them and cannot story moves to the EDVAC design and to its be understood without knowledge of those early realizations.4 The mainframe era then histories, which extend beyond computers begins, followed by the short reign of the and computing to encompass the full range minicomputer and then by the current age of of human activities. All software, even the the microcomputer in ever more powerful 8 IEEE Annals of the History of Computing Published by the IEEE Computer Society 1058-6180/08/$25.00 G 2008 IEEE form. The sequence is commonly treated as a natural evolution of forms. As each new generation appears, the old disappears from the story, as if mainframes went the way of the dinosaur when minicomputers appeared, and they in turn followed the mainframe into obsolescence as the microcomputer opened a new era of personal computing. It would be hard to know from most histories of this sort that IBM still derives a major share of its income from mainframe computers, especially as accounts of the Internet focus on the PC clients to the exclusion of the mainframe servers. Similarly, emphasis on the PC has hidden the ways in which with their growing power they have incorporated minicomputer architectures and Figure 1. The convergent account. systems and, with them, their mainframe legacy. Also lost from view with a focus on misleading in at least two ways. First, it makes the visible PC is embedded computing, which the application of the computer in a wide accounts for the vast majority of the micro- range of areas unproblematic. If people have processors at work today. been waiting for the computer to appear as the To the extent that the standard narrative desired solution to their problems, it is not covers software, the story follows the genera- surprising that they then make use of it when tions of machines, with an emphasis on systems software, beginning with program- it appears, or indeed that they know how to ming languages and touching—in most cases, make use of it. By the same token, it then just touching—on operating systems, at least becomes difficult to explain, for example, why up to the appearance of time-sharing. With a IBM would have hesitated to enter the com- nod toward Unix in the 1970s, the story moves puter market in the late 1940s, or why the quickly to personal computing software and National Institutes of Health had to launch a program to persuade biologists that computers the story of Microsoft, seldom probing deep 5 enough to reveal the roots of that software in could be of use to them. Second, the the earlier period. One may learn a bit about convergent account sets up a narrative of the beginnings of the data processing industry, revolutionary impact, in which the computer since it is synonymous with IBM, but there is is brought to bear on one area after another, in little if anything about the building of the first each case with radically transformative effect. large systems in business, industry, and gov- There is a lot of ‘‘revolution talk’’ in ernment. For this story, one must delve into computing. It dates back at least to 1962 with the specialist literature, much of it still the publication of Edmund C. Berkeley’s The dominated by ‘‘pioneer’’ accounts. The soft- Computer Revolution, in which the author made ware of the embedded systems underlying the the computer part of the ‘‘second industrial world’s technical, industrial, and financial revolution’’ and fretted over what was to infrastructure remains, of course, as invisible become of humans in an age of Giant Brains, to the historical record as do the devices on or Machines That Think (the title of his 1949 which it runs. book). One can hardly pick up a journal in Indeed, with respect to applications soft- computing today without encountering some ware, the standard narrative converges in sort of revolution in the making, usually another way. Just as it places all earlier proclaimed by someone with something to calculating devices on one or more lines sell. Critical readers recognize most of it as leading toward the electronic digital comput- hype based on future promise rather than er, as if they were somehow all headed in its present performance, and those with long direction, so too it pulls together the various memories recall the many revolutions that contexts in which the devices were built, as if have been canceled or postponed owing to they constituted a growing demand for the technical difficulties. invention of the computer and as if its Historians have grown wary of the notion appearance was a response to that demand. of revolutions, especially those that purport to That way of telling the story is historically erase the past or render it obsolete, as if July–September 2008 9 What Makes the History of Software Hard societies could start from scratch. There have been episodes in which societies changed The history of comput- radically over a relatively short period, and ‘‘revolution’’ seems an appropriate designa- ing, especially of soft- tion for the process, for example, the Industrial Revolution in England in the late 18th and ware, should strive to early 19th centuries. But even there one must be careful, because revolution talk tends to preserve human agency hide the continuities that tie the present to the past, or rather the continuities through which by structuring its the past informs the present. Nothing is in fact unprecedented, if only because we use prece- narratives around people dents to recognize, accommodate, and shape the new. In our personal encounters with new facing choices and situations, we turn to our memory for similar situations as a guide to how to respond. making decisions. History is our community memory, and it is as much embedded in our lives as our personal memories. Through language, customs, edu- In the impact model, ‘‘the computer’’ cation, and institutions, it informs the way we happens to people, who are put in the position think and the way we do things. It shapes our of responding to it. But computers do nothing expectations and our actions; it is built into without programs, and programs do not just our practices.6 As a senior colleague of mine happen by themselves. People design them for once remarked to a group of scientists, the their own purposes. Hence, the history of question is not whether one does history but computing, especially of software, should whether one does it well. For example, the strive to preserve human agency by structuring quest for a discipline of software engineering its narratives around people facing choices and began with a search for historical forebears, making decisions instead of around imperson- and the subsequent literature is filled with al forces pushing people in a predetermined appeals to the history of technology, some of direction. Both the choices and the decisions them well founded, others not.7 are constrained by the limits and possibilities of the state of the art at the time, and the state Histories of computing of the art embodies its history to that point.
Recommended publications
  • Connecticut DEEP's List of Compliant Electronics Manufacturers Notice to Connecticut Retailersi
    Connecticut DEEP’s List of Compliant Electronics manufacturers Notice to Connecticut Retailersi: This list below identifies electronics manufacturers that are in compliance with the registration and payment obligations under Connecticut’s State-wide Electronics Program. Retailers must check this list before selling Covered Electronic Devices (“CEDs”) in Connecticut. If there is a brand of a CED that is not listed below including retail over the internet, the retailer must not sell the CED to Connecticut consumers pursuant to section 22a-634 of the Connecticut General Statutes. Manufacturer Brands CED Type Acer America Corp. Acer Computer, Monitor, Television, Printer eMachines Computer, Monitor Gateway Computer, Monitor, Television ALR Computer, Monitor Gateway 2000 Computer, Monitor AG Neovo Technology AG Neovo Monitor Corporation Amazon Fulfillment Service, Inc. Kindle Computers Amazon Kindle Kindle Fire Fire American Future Technology iBuypower Computer Corporation dba iBuypower Apple, Inc. Apple Computer, Monitor, Printer NeXT Computer, Monitor iMac Computer Mac Pro Computer Mac Mini Computer Thunder Bolt Display Monitor Archos, Inc. Archos Computer ASUS Computer International ASUS Computer, Monitor Eee Computer Nexus ASUS Computer EEE PC Computer Atico International USA, Inc. Digital Prism Television ATYME CORPRATION, INC. ATYME Television Bang & Olufsen Operations A/S Bang & Olufsen Television BenQ America Corp. BenQ Monitor Best Buy Insignia Television Dynex Television UB Computer Toshiba Television VPP Matrix Computer, Monitor Blackberry Limited Balckberry PlayBook Computer Bose Corp. Bose Videowave Television Brother International Corp. Brother Monitor, Printer Canon USA, Inc. Canon Computer, Monitor, Printer Oce Printer Imagistics Printer Cellco Partnership Verizon Ellipsis Computer Changhong Trading Corp. USA Changhong Television (Former Guangdong Changhong Electronics Co. LTD) Craig Electronics Craig Computer, Television Creative Labs, Inc.
    [Show full text]
  • Retrocomputing As Preservation and Remix
    Retrocomputing as Preservation and Remix Yuri Takhteyev Quinn DuPont University of Toronto University of Toronto [email protected] [email protected] Abstract This paper looks at the world of retrocomputing, a constellation of largely non-professional practices involving old computing technology. Retrocomputing includes many activities that can be seen as constituting “preservation.” At the same time, it is often transformative, producing assemblages that “remix” fragments from the past with newer elements or joining together historic components that were never combined before. While such “remix” may seem to undermine preservation, it allows for fragments of computing history to be reintegrated into a living, ongoing practice, contributing to preservation in a broader sense. The seemingly unorganized nature of retrocomputing assemblages also provides space for alternative “situated knowledges” and histories of computing, which can sometimes be quite sophisticated. Recognizing such alternative epistemologies paves the way for alternative approaches to preservation. Keywords: retrocomputing, software preservation, remix Recovering #popsource In late March of 2012 Jordan Mechner received a shipment from his father, a box full of old floppies. Among them was a 3.5 inch disk labelled: “Prince of Persia / Source Code (Apple) / ©1989 Jordan Mechner (Original).” Mechner’s announcement of this find on his blog the next day took the world of nerds by storm.1 Prince of Persia, a game that Mechner single-handedly developed in the late 1980s, revolutionized computer games when it came out due to its surprisingly realistic representation of human movement. After being ported to DOS and Apple’s Mac OS in the early 1990s the game sold 2 million copies (Pham, 2001).
    [Show full text]
  • Case No COMP/M.1694 - EMC / DATA GENERAL
    EN Case No COMP/M.1694 - EMC / DATA GENERAL Only the English text is available and authentic. REGULATION (EEC) No 4064/89 MERGER PROCEDURE Article 6(1)(b) NON-OPPOSITION Date: 06/10/1999 Also available in the CELEX database Document No 399M1694 Office for Official Publications of the European Communities L-2985 Luxembourg COMMISSION OF THE EUROPEAN COMMUNITIES Brussels, 06.10.1999 SG(99)D/7991 In the published version of this decision, some information has been omitted pursuant to Article 17(2) of Council Regulation (EEC) No PUBLIC VERSION 4064/89 concerning non-disclosure of business secrets and other confidential information. The MERGER PROCEDURE omissions are shown thus […]. ARTICLE 6(1)(b) DECISION Where possible the information omitted has been replaced by ranges of figures or a general description. To the notifying party Dear Sirs, Subject : Case No IV/M.1694-EMC/DATA GENERAL Notification of 3-09-19999 pursuant to Article 4 of Council Regulation No 4064/89. 1. On 3 September 1999, the Commission received a notification of a proposed concentration pursuant to Article 4 of Council Regulation (EEC) No 4064/891 by which EMC Corporation (“EMC”), USA, will acquire sole control of Data General Corporation (“Data General”), USA. 2. After examination of the notification the Commission has concluded that the notified operation falls within the scope of Council Regulation (EEC) No 4064/89 and does not raise serious doubts as to its compatibility with the common market and with the EEA Agreement. I. THE PARTIES 3. EMC Corporation , based in the U.S.A, is active mainly in the design and manufacture of a wide range of information technology products, including hardware, software and related services.
    [Show full text]
  • Aviion SERVERS and WORKSTATIONS PLUS
    "Great products ••• fantastic support!" Buzz Van Santvoord, VP of Operations, Plow & Hearth, Inc. Buzz Van Santvoord, Plow & Hearth When you've got 100 telesales reps VP of Operations, and Peter Rice, processing 6,500 orders a day your President, with a selection of items computer system had better work! from their catalogue. Virginia ba ed, Plow & Hearth, Inc. i a $30 million mail order company, specializing in product for country living. Mailing over 20 million catalogue a year and with an e tabli hed ba e of over 1 million cu tomer , it computer y tems are critical to the onver ion of the AOS / VS OBOL program to ACUCOBOL company' ucce and growth. commenced in June and the ystem went live on a Data General A VUON 8500 in September, in plenty of time for the Chri tma ru h. To meet it pecific need Plow & Hearth had inve ted The AIM plu AVUON combination gave the bu ine a dramatic more than $500,000, over a period of 13 year , developing a boo t: "The much fa ter re pon e time improved morale and Data General MY-ba ed y tern in AOS{VS COBOL with 300 increa ed our tele ale capacity without adding a body, and the program and 70 INFOS databa e . But by early 1995 the extra order gained gave u our be t Chri tma ever." company realized that their MY9600 didn't have the capacity to make it through the bu y Chri tma ea on. Expert migration consultants Buzz Van Santvoord, Vice Pre ident of Operation explains: Thi ca e tudy illu trate how Tran oft' AIM offering i more "A move to Open Sy tern wa our preferred strategic direction.
    [Show full text]
  • The Past, Present, and Future of Software Evolution
    The Past, Present, and Future of Software Evolution Michael W. Godfrey Daniel M. German Software Architecture Group (SWAG) Software Engineering Group School of Computer Science Department of Computer Science University of Waterloo, CANADA University of Victoria, CANADA email: [email protected] email: [email protected] Abstract How does our system compare to that of our competitors? How easy would it be to port to MacOS? Are users still Change is an essential characteristic of software devel- angry about the spyware incident? As new features are de- opment, as software systems must respond to evolving re- vised and deployed, as new runtime platforms are envis- quirements, platforms, and other environmental pressures. aged, as new constraints on quality attributes are requested, In this paper, we discuss the concept of software evolu- so must software systems continually be adapted to their tion from several perspectives. We examine how it relates changing environment. to and differs from software maintenance. We discuss in- This paper explores the notion of software evolution. We sights about software evolution arising from Lehman’s laws start by comparing software evolution to the related idea of software evolution and the staged lifecycle model of Ben- of software maintenance and briefly explore the history of nett and Rajlich. We compare software evolution to other both terms. We discuss two well known research results of kinds of evolution, from science and social sciences, and we software evolution: Lehman’s laws of software evolution examine the forces that shape change. Finally, we discuss and the staged lifecycle model of Bennett and Rajlich. We the changing nature of software in general as it relates to also relate software evolution to biological evolution, and evolution, and we propose open challenges and future di- discuss their commonalities and differences.
    [Show full text]
  • A Brief History of Software Engineering Niklaus Wirth ([email protected]) (25.2.2008)
    1 A Brief History of Software Engineering Niklaus Wirth ([email protected]) (25.2.2008) Abstract We present a personal perspective of the Art of Programming. We start with its state around 1960 and follow its development to the present day. The term Software Engineering became known after a conference in 1968, when the difficulties and pitfalls of designing complex systems were frankly discussed. A search for solutions began. It concentrated on better methodologies and tools. The most prominent were programming languages reflecting the procedural, modular, and then object-oriented styles. Software engineering is intimately tied to their emergence and improvement. Also of significance were efforts of systematizing, even automating program documentation and testing. Ultimately, analytic verification and correctness proofs were supposed to replace testing. More recently, the rapid growth of computing power made it possible to apply computing to ever more complicated tasks. This trend dramatically increased the demands on software engineers. Programs and systems became complex and almost impossible to fully understand. The sinking cost and the abundance of computing resources inevitably reduced the care for good design. Quality seemed extravagant, a loser in the race for profit. But we should be concerned about the resulting deterioration in quality. Our limitations are no longer given by slow hardware, but by our own intellectual capability. From experience we know that most programs could be significantly improved, made more reliable, economical and comfortable to use. The 1960s and the Origin of Software Engineering It is unfortunate that people dealing with computers often have little interest in the history of their subject.
    [Show full text]
  • Trade Mark Opposition Decision (O/396/02)
    TRADE MARKS ACT 1994 IN THE MATTER of application No. 2165852 by Yorkshire Co-operatives Limited and IN THE MATTER of opposition thereto under No. 50738 by Sun Microsystems Incorporated. Background 1. On 6th May 1998 Yorkshire Co-operatives Limited (YCL) applied under the Trade Marks Act 1994 to register the mark SUNWIN for the goods and services specified in ANNEX A. 2. The application was accepted and published. On 21st February 2000 Sun Microsystems Incorporated (‘the opponents’) filed notice of opposition to the application. They are the proprietors of a large quantity of marks, registered in the UK and the under the Community system, a number of which are on display in ANNEX B to this decision. They state that these marks constitute a ‘family’ of marks, and have traded under the SUN and SUN prefixed trade marks since 1983, producing a wide range of ‘..computer hardware, software and other microelectronic goods and services..’ becoming, as a result, a market leader in computer workstations, servers and operating systems. 3. The opponents’ first grounds of opposition to registration is under s. 5(2)(b) of the Act, and relates (in particular, but not exclusively) to the following goods and services which are considered to be similar: Class 9: Computers; computer hardware, software and firmware; scientific apparatus and instruments; apparatus and instruments all for the recordal, storage, transmission and reproduction of audio, visual and audio visual data. Class 38: Installation and repair services relating to electrical apparatus and instruments, data processing apparatus and computers. Class 38: Telecommunications. 4. The opponents also consider that, as their earlier trade marks have a reputation in the United Kingdom, use of the applicants’ mark would be contrary to Section 5(3) of the Act, for goods and services which are not considered similar under Section 5(2).
    [Show full text]
  • The History of Computing in the History of Technology
    The History of Computing in the History of Technology Michael S. Mahoney Program in History of Science Princeton University, Princeton, NJ (Annals of the History of Computing 10(1988), 113-125) After surveying the current state of the literature in the history of computing, this paper discusses some of the major issues addressed by recent work in the history of technology. It suggests aspects of the development of computing which are pertinent to those issues and hence for which that recent work could provide models of historical analysis. As a new scientific technology with unique features, computing in turn can provide new perspectives on the history of technology. Introduction record-keeping by a new industry of data processing. As a primary vehicle of Since World War II 'information' has emerged communication over both space and t ime, it as a fundamental scientific and technological has come to form the core of modern concept applied to phenomena ranging from information technolo gy. What the black holes to DNA, from the organization of English-speaking world refers to as "computer cells to the processes of human thought, and science" is known to the rest of western from the management of corporations to the Europe as informatique (or Informatik or allocation of global resources. In addition to informatica). Much of the concern over reshaping established disciplines, it has information as a commodity and as a natural stimulated the formation of a panoply of new resource derives from the computer and from subjects and areas of inquiry concerned with computer-based communications technolo gy.
    [Show full text]
  • An Overview of Software Evolution
    An Overview of Software Evolution CPRE 416-Software Evolution and Maintenance-Lecture 2 1 Software Evolution • What is it? • How important is it? • What to do about it? 2 An early history of software engineering • The following slides provide a condensation of the ideas of Robert L. Glass in his book "In the Beginning: Recollections of Software Pioneers" about the history of software engineering. 3 The Pioneering Era (1955-1965) • New computers were coming out every year or two. • Programmers did not have computers on their desks and had to go to the "machine room". • Jobs were run by signing up for machine time. Punch cards were used. • Computer hardware was application-specific. Scientific and business tasks needed different machines. 4 The Pioneering Era (1955-1965) • High-level languages like FORTRAN, COBOL, and ALGOL were developed. • No software companies were selling packaged software. • Academia did not yet teach the principles of computer science. 5 The Stabilizing Era (1965-1980) • Came the IBM 360. • This was the largest software project to date. • The 360 also combined scientific and business applications onto one machine. 6 The Stabilizing Era (1965-1980) • Programmers had to use the job control language (JCL) to tell OS what to do. • PL/I, introduced by IBM to merge all programming languages into one, failed. • The notion of timesharing emerged. • Software became a corporate asset and its value became huge. • Academic computing started in the late 60's. • Software engineering discipline did not yet exist. 7 The Stabilizing Era (1965-1980) • High-hype disciplines like Artificial Intelligence emerged.. • Structured Programming burst on the scene.
    [Show full text]
  • The History of Unix in the History of Software Haigh Thomas
    The History of Unix in the History of Software Haigh Thomas To cite this version: Haigh Thomas. The History of Unix in the History of Software. Cahiers d’histoire du Cnam, Cnam, 2017, La recherche sur les systèmes : des pivots dans l’histoire de l’informatique – II/II, 7-8 (7-8), pp77-90. hal-03027081 HAL Id: hal-03027081 https://hal.archives-ouvertes.fr/hal-03027081 Submitted on 9 Dec 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. 77 The History of Unix in the History of Software Thomas Haigh University of Wisconsin - Milwaukee & Siegen University. You might wonder what I am doing The “software crisis” and here, at an event on this history of Unix. the 1968 NATO Conference As I have not researched or written about on Software Engineering the history of Unix I had the same question myself. But I have looked at many other The topic of the “software crisis” things around the history of software and has been written about a lot by profes- this morning will be talking about how sional historians, more than anything some of those topics, including the 1968 else in the entire history of software2.
    [Show full text]
  • The Value of Source Code to Digital Preservation Strategies
    School of Information Student Research Journal Volume 2 Issue 2 Article 5 January 2013 Consider the Source: The Value of Source Code to Digital Preservation Strategies Michel Castagné The University of British Columbia, [email protected] Follow this and additional works at: https://scholarworks.sjsu.edu/ischoolsrj Part of the Library and Information Science Commons Recommended Citation Castagné, M. (2013). Consider the Source: The Value of Source Code to Digital Preservation Strategies. School of Information Student Research Journal, 2(2). https://doi.org/10.31979/2575-2499.020205 Retrieved from https://scholarworks.sjsu.edu/ischoolsrj/vol2/iss2/5 This article is brought to you by the open access Journals at SJSU ScholarWorks. It has been accepted for inclusion in School of Information Student Research Journal by an authorized administrator of SJSU ScholarWorks. For more information, please contact [email protected]. Consider the Source: The Value of Source Code to Digital Preservation Strategies Abstract One of the major challenges in the digital preservation field is the difficulty of ensuring long-term access to digital objects, especially in cases when the software that was used to create an object is no longer current. Software source code has a human-readable, documentary structure that makes it an overlooked aspect of digital preservation strategies, in addition to a valuable component for the records of modern computing history. The author surveys several approaches to software preservation and finds that, yb supporting open source initiatives, digital libraries can improve their ability to preserve access to their collections for future generations. Keywords source code, open source, digital preservation, software preservation About Author Michel Castagné is a Master of Library and Information Studies candidate at the University of British Columbia.
    [Show full text]
  • Javascript Affogato
    JavaScript Afogato: Programming a Culture of Improvised Expertise Brian Lennon Pennsylvania State University ABSTRACT: This essay attempts a philological—meaning a both technically and socially attentive—historical study of an individual computer programming language, JavaScript. From its introduction, JavaScript’s reception by software developers, and its importance in web development as we now understand it, was structured by a con- tinuous negotiation of expertise. I use the term “improvised expertise” to describe both conditions for and effects of the unanticipated de- velopment of JavaScript, originally designed for casual and inexpert coders, into a complex of technical artifacts and practices whose range and complexity of use has today propelled it into domains previously dominated by other, often older and more prestigious languages. “Im- provised expertise” also marks the conditions for and effects of three specific developmental dynamics in JavaScript’s recent history: first, the rapidly accelerated development of the language itself, in the ver- sions of its standard specification; second, the recent, abruptly emerg- ing, yet rapid growth of JavaScript in server-side networking, data pro- cessing, and other so-called back-end development tasks previously off limits to it; third, the equally recent and abrupt, yet decisive emer- gence of JavaScript as the dominant language of a new generation of dynamic web application frameworks and the developer tool chains or tooling suites that support them. Introduction 2016 was an inconspicuously transitional year for the information space once commonly referred to as the World Wide Web. Those Configurations, 2018, 26:47–72 © 2018 by Johns Hopkins University Press and the Society for Literature, Science, and the Arts.
    [Show full text]