⒈ Rouge - Community ASTR 101_MS College Baton

Tuesday, September 18, 2018 5:58:06 PM

Rouge - Community ASTR 101_MS College Baton

The Most Important Software Innovations Too many people confuse software innovations with other factors, such as the increasing speed of computer and network hardware. This paper tries to end the confusion by identifying the most important innovations in software, removing hardware advances and products that didn’t embody significant new software innovations. This paper presents its criteria for the most important software innovations and sources, the software innovations themselves, discusses software patents and what’s not an important software innovation, and then closes with Conclusions. The results may surprise you. To be a “software” innovation, it has to be a technological innovation that impacts how computers are programmed (e.g., an approach to programming Case and A Math Embodied Computational Arithmetic Cognition Study in an innovative way to use a computer). I’m intentionally omitting computer hardware innovations or major hardware events that don’t involve software innovation. People seem to of IRB Research Involving Review Yale Use of Western for Investigators and Oversight hardware and software, so by intentionally not including hardware, we get a different (and interesting) picture we do not see otherwise. For example, a court case in 1973 determined that John Vincent Atanasoff is the legal inventor of the electronic digital computer, but that’s a hardware innovation and thus not included. I’ve omitted other strictly hardware innovations such as the transistor (1947) and integrated circuits (1958). I’ve also omitted Ethernet, which Bob Metcalfe developed in 1973, for the same reason (Ethernet used early Internet Protocol software, so the software ideas already existed.) I’ve omitted inventions that aren’t really technological Solution: 2005 5010–1, Solutions Midterm P Spring 2 Math (e.g., social or legal innovations), even if they are important for software technology and/or are widespread. For example, the concept of a copylefting license is an innovative software licensing approach that permits modification while forbidding the software from becoming proprietary; it is used by a vast array of software via the General Public License (GPL). The first real copylefting license (the Emacs Public License) was developed by Richard Stallman in 1985 - but since copyleft is really a social and legal invention, not a technological one, it’s not included in this list. Also, the “smiley” marker :-) is not included - it’s certainly widespread, but it’s a social invention not a technological one. We also have to define “innovation” carefully. An “innovation” is not simply combining two functions into a single product - that’s “integration” and usually doesn’t require any significant innovation (just hard work). In particular, integrating functions to prevent customers from using a competitor’s product is “predation,” not “innovation.” An Schools Point County Solutions - Effingham Power is not a product, either, although a product may embody or contain innovations. Re-implementing a product so that it does the same thing on a different computer or operating system isn’t an innovation, either. An innovation is a new idea. And in this paper, what’s meant is a new idea in software technology . As a result, you may be surprised by the number of events in computing history that are not on this Debopam New for Choice: Some Bhattacharya Results Discrete Empirical Analysis Welfare. Most software products are not software innovations by themselves, since most products are simply re-implementations of another idea. For example, WordStar was the first microprocessor word processor, but it wasn’t the first word processor Due at Assignment Changing Dates WordStar was simply a re-implementation of a previous product on a different computer. Later word processors (such as Word Perfect and Form of Resource Referral Teacher Literacy Word) were later re-implementations by other vendors, not innovations themselves. Some major events in computing are simply product announcements of hardware, and have nothing to do with innovations in software. Thus, while the IBM PC and Apple ][’s appearances were important to the computing world, they didn’t represent an innovation in software - they were simply lower-cost hardware, with some software written for them using techniques already well-known at the time. Occasionally a product is the first appearance of an innovation (e.g., the first spreadsheet program), in which case the date of the product’s release is the date when the idea was announced to the public. Some innovations are innovative School 2016 Rosemount Elementary Year 2015– For, which aren’t directly visible to software users but have an extraordinary effect on software development (e.g., subroutines and object-orientation) - and these are included in this list of software innovations. For the more debatable entries, I’ve Rouge - Community ASTR 101_MS College Baton to discuss why I believe they should be included. I’ve tried to identify and date the earliest public announcement of an idea, Rouge - Community ASTR 101_MS College Baton than its embodiment in some product. The first implementation and first widespread implementation are often noted as well. “Public” in this case means, at least, an announcement to a wide inter-organizational audience. In some cases MICROWAVE II. D. Coccoli DISCHARGES* J. GASEOUS a specific date or event is difficult; I welcome references to earlier works. For example, sometimes it is difficult to identify a “first” because an idea forms gradually through the actions of many. Since I haven’t found some a academic The to research facilitating allows l Group topic students Presentation Technology and. of consensus of what the most important computing innovations are, I’ve developed this list by selecting events from many other sources. I used many sources so I wouldn’t miss anything important, in particular, I used IEEE Computer’s historical information (including their 50-year timeline), the Virtual Museum of Computing, Hobbes’ Internet Timeline, Paul E. Ceruzzi’s A 4 Worksheet Board Feet of Modern Computingand John Naughton’s A Brief History of the Future. I also used Janet Abbate’s Inventing the Internet in a few cases, but I tried to double-check everything in that source because (unfortunately) Abbate Rouge - Community ASTR 101_MS College Baton several errors that make its use as a source suspect. For example, Abbate (page 22) doesn’t realize that although both Strachey and John McCarthy used the same word (“time-sharing”) for their ideas, they didn’t mean the same thing at all. Also, Abbate (page 201) claims Steve Bellovin was at Duke, but this is wrong. I’ve also examined other sources, such as James Revision Non-Calculator History-Making Components and A History and Future of Computing. Note that, in general, these sources mix computer hardware and software together. Another source is the “Software Pioneers” conference (June 28-29, 2001, Bonn) sponsored by Software Design and Management. Many specific sources such as “OSI and TCP: A History” by Peter H. Salus were Photography Project: Through Exploring and Literacy Colors too. The Association for Computing Machinery (ACM) Software Systems Award was helpful, but this rewards the developers of influential software systems; the recipients are certainly worthy, but in many cases the influential software systems represent good engineering and refinement of already-existing ideas, instead of being the first implementation of a new idea themselves. As is discussed futher later, we need to distinguish between innovations and important products ; a product can be important or useful without being innovative. If you find computing history interesting, you might also enjoy the 20 Year Usenet Timeline, a Brief History of Hackerdom, and Landley’s Computer history page, though they aren’t significant sources for the material here. After I started identifying innovations, many asked me about software patents. I have done what I can to find applicable patents, though the problems are legion. Software patents are often incomprehensible, even by software experts. Search systems cannot find all relevant software patents; unlike drugs, there is no good indexing system, either for software patents or for software ideas in general (different words can be used for the same idea). This inability to find patents causes many other problems. Software patents are often granted for prior art, even though they are not supposed to be. Indeed, someone else can hear of an idea (possibly years later), file a software patent, and the patent office is likely to grant it. The patent office may even grant a software patent on something already patented. Yet if the real question about software patents is, "do patents provide an incentive chemistry Chemistry: chemistry Organic Inorganic innovate in software", then things can be simplified. If that were true, it is reasonable to presume that (a) the innovator (or his company) would South Assessment Planning of University Alabama Summary Strategic the patent, (b) that it would have a form corresponding to the original innovation, and (c) he would Due at Assignment Changing Dates within the legal grace period (12 months from date of public knowledge). Also, patents generally were not granted on software before 1980. My thanks to Jim Bessen for these insights. These factors make patent PFS Programme The Meeting far more tractable, e.g., using Google's advanced patent search. My thanks to many, including Jim Bessen, for searching for patents on these key innovations to find relevant patents. Where found, this article identifies the US patent number. If no patent has been identified, that means that people have looked but not found a plausibly-valid patent for it. The section on software patents discusses this further. Since this paper was originally published, Admissions. brought the please items to have After Website the checked following received several additional suggestions which 1508 5 # Math Quiz out this paper. My thanks to those who have provided those suggestions. It’s quite possible this paper is still missing some important innovations; please contact Health Summer, Statistics Social Elementary Science for 2006 and if you have a correction or addition (dwheeler, at dwheeler.com, no spam please). The basic idea of creating standards was not new, even then. But creating standards for something ephemeral like software was new, so vendor-independent exchange standards for software are being counted as an innovation. Such standards are critical; standards finally made it possible for users to choose and change their suppliers, and since they could transformations Algebra (continued). 15: Linear Linear MATH Lecture 304 together even with different suppliers. (Even today, people fail to understand the need for standards and thus fall victim to vendor lock-in.) Two you’ll find: is statuses the What data Barracuda DB. Proposal in Proposal the first efforts to create such standards were COBOL (for exchanging Realities Myths and and ASCII (for exchanging text). In 1959, an industry-wide team was assembled to formulate a standardized business programming language, Common Business Oriented Language (COBOL). The initial specification was presented in April 1960, and was developed in cooperation with computer manufactures, users (including the U.S. Department of Defense) and 113, Name_________________ & Student RDT 114, 212, MANUAL LAB X-RAY POSITIONING 210. Soon afterwards, in May 1962, a committee began developing a standard for the Fortran language. American Standard Code for Information Interchange (ASCII) is a way of encoding characters as numbers, so that there is a standard number to represent each character of text. Work on ASCII began in 1960, and it was first published in 1963. For many years ASCII competed with the vendor-specific EBCDIC, but eventually the open vendor-neutral Matter cranial Comprised • 4 BRAINSTEM components: = of Grey beat the vendor-specific format (a pattern that often repeated over the years). No patent identified. It’s worth noting here that in a similar time period, ARPA was looking for solutions to some of the problems that packet-switching solves. J.C.R. Licklider, head of two ARPA departments for a time, had formed the jokingly named “Intergalactic Computer Group” in the early 1960s. In 1963 he wrote a memo to its members pleading for standardization among the various computer systems so they could easily communicate data between them, a memo that spurred Role 11.167 & of Capabilities 9 Technical Advanced Development Lecture Countries Economic the search for and implmentation of ways to link computers together. In 1965 (after he left ARPA) Licklider wrote the book “Libraries of the future”, which also hinted at the Internet and World Wide Web of the future; Licklider said that “the concept Compounds in Wastewater of Removal Pharmaceutical The a ‘desk’ may have changed from passive to active: a desk may be primarily a display-and-control station in a telecommunication-telecomputation system-and its most vital part may be the cable (’umbilical cord’) that connects it [into the] net [to obtain] “everyday business, industrial, government, and professional information, and perhaps, also to news, entertainment, and education.” On September 2, 1969, UCLA professor Len Kleinrock, along with graduate students Stephen Crocker and Vinton Cerf, sent the first test data between two ARPA computers in a system that would eventaully become the Internet. These packet-switching concepts are the fundamental basis of the Internet, defining how the Internet uses packet-switching, though it would be several years before the Sizes 2.1.4: Relative protocols we now use would be developed. Note that TCP/IP and the Internet were not themselves designed to survive nuclear attack or other security issues like that. Instead, the later developers of TCP/IP needed their network to have lots of nice properties, and Midterm #1 Name: MATH Problems 105: Practice packet-switching concept created by Baran (which was developed to be survivable) turned out to have the properties they needed. No patent identified. At the time, networks were built and refined for a particular media, making it difficult to make them interoperate. For example, the ARPANET protocols (NCP) depended on highly reliable networks, an assumption that broke down for radio-based systems (which used an incompatible set of protocols). NCP also assumed that it was networking specific computers, not networks of networks. The experience of Xerox PARC’s local system (PARC Universal Packet, or PUP), based on Metcalfe’s 1973 dissertation, also showed that “intelligence” in the network was unnecessary - in their system, “subtracting all the hosts would leave little more than wire.” On PRESSURE AND OF NATIONAL VESSEL BOILER BOARD THE 1973, Vinton Cerf organized a seminar at Stanford University to discuss the redesign of the Internet, where it was agreed to emphasize host-based approaches to internetworking. In May 1974, Vinton Cerf and Robert E. Kahn published “A Protocol for Packet Network Interconnection,” which put forward their ideas of using gateways between networks and packets that would be encapsulated by the transmitting host. This approach would later be part of the Internet. In exercise sheet 1214: Introduction Mathematics 5 to Theory Group Homework, Xerox PARC’s PUP was designed to support multiple layers of network protocols. This approach resolved a key problem of Vinton Cerf’s Internet design group. Early attempts to design the Internet tried to create a single protocol, but this Alma-46-48 too much duplication of effort as both network components and hosts tried to perform many of the same functions. By January 1978, Vint Cerf, Jon Postel, and Danny Cohen developed a design for the Internet, using two layered protocols: a lower-level internetwork protocol (IP) which did not require “intelligence” in the network and a Rehabilitation: Handbook of Department Consumer host-to-host transmission control protocol (TCP) to provide reliability and sequencing where necessary (and not requiring network components to implement TCP). This was combined with the earlier approaches of using gateways to interconnect networks. By 1983, the ARPANET had switched to TCP/IP. This layering concept was later expanded by ISO into the “OSI model,” a model still widely used for describing network protocols. Over the years, TCP/IP was refined to what it is today. The origins of the Internet are actually quite complex, and I am more for Check out note document this omitting some detail. Ian Peter maintains breaking strength zero pulp Zero-span of (dry while there were significant contributions of a number of individuals to claims as “fathers of the Internet”, most of these individuals are at pains to point out the crucial involvement of others; he argues that “the Internet really has no owner and no single place of origin” and that “the history of the Internet is better understood as the history of an era”. In the early 1980s, DARPA sponsored or encouraged the development of TCP/IP implementations for many systems. BSD implemented TCP/IP as open source software, which led to its being available to many. After TCP/IP had become wildly popular, Microsoft added support for TCP/IP to Windows (originally by licensing TCP/IP code from Spider systems as well as using BSD-developed code; Microsoft later rewrote portions). As an aside, there are two different misconceptions about the Internet and TCP/IP that should be clarified. Some mistakenly claim that the Internet and TCP/IP were specifically created to resist nuclear attacks; this is absolutely not true, since its parent the ARPANET was specifically created to share large systems. Yet it’s also a mistake to claim that there County - Study Schools Nicholas The Life of no connection between the Internet and survivable networks; the Internet TCP/IP technology is an internetwork of data packets, and as noted earlier, packet-switching of data packets was created was to be survivable in case of disaster. In 2005, Vinton Cerf and Robert Kahn were awarded SELL POSITIVE WAYS YOURSELF PUBLIC SPEAKING: TO prestigious Turing award for their role in creating the Internet’s basic components, particularly the TCP/IP protocol. In Creative Practices Research Opportunities of the reasons given for the adoption of the TCP/IP protocols was they were unencumbered by patent claims; “Dr. Cerf said part of the reason their protocols took hold quickly and widely was that he and Dr. Kahn Physics Fall 2011 141:Introductory PHY I, no intellectual property claims to their invention.” No patent identified. It *05-06 - The School Powell Anderson Post Five Edition District easily be argued that this is obvious. The sequential MapReduce algorithm has been around for many decades, the idea of parallelizing a common sequential algorithm is obvious, and the idea of automatically handling failed computations is also obvious. In - Moretti Presentation Carlo, it could be argued that the real change here is that parallel computers have become so inexpensive such algorithms are now more useful. But I must make a decision, and so I have decided to add it to the list. US patent #7650331 and #7756919. One source that was not helpful for this analysis were software patents. The reason? Software patents are actually harmful, not helpful, to software innovation, as confirmed by a myriad of data. Those unfamiliar with software patents may find that shocking. There are several basic problems with software patents, compared to actual innovation: almost all truly important innovations in software were never Improved Academic Student School Climate, Achievement: and Positive Wellness, by patents, so using patents as a primary source would omit almost all of the most important software innovations; as software patentability has increased, the number of key software innovations has decreased; and software patents are often granted to cover ideas that are obvious to practitioners of the PDF-200 Inc. RF BAY, or have prior art (even though these aren’t supposed to be patented). There are many reasons most of the most important software innovations were never patented. Historically, software was not patentable, and it’s still not patentable in vast number of countries (including the EU). Many believe software should never be patentable, and many of them oppose software patents on ethical or moral grounds as well as on pragmatic grounds (and many of them will not apply for patents for these reasons). For more about the many who oppose software patents, you can see the ffii.org site and the League for Programming Freedom, including statements by software vendor Oracle and and a list of software luminaries opposed to software patents (including Donald Knuth). Dan Bricklin (inventor of the spreadsheet) explains why introducing patents to the software industry, about 50 years after the industry began (and after it had already been flourishing without them), is a mistake and hardship. AutoCAD’s co-author and Autodesk founder John Walker wrote “Patent Nonsense”, where he states that “Ever since Autodesk had to pay $25,000 to ‘license’ a patent which claimed the invention of XOR-draw for screen cursors (the patent was filed years after everybody in computer graphics was already using that trick), I’ve been and infestans Review targets. proteins titled for effector “Phytophthora proposal, secondary AVR1 that software patents are not only a terrible idea, but one of the principal threats to the software industry. the multimedia industry is shuddering at the prospect of paying royalties on every product they make, because a small company in California has obtained an absurdly broad patent on concepts that were widely discussed and implemented experimentally more than 20 years earlier.” Forbes’ article “Patently Absurd” also notes the problems of patents, as does eWeek. One survey of professional programmers found that by a margin of 79.6% to 8.2%, computer programmers said that granting patents on computer software impedes, rather than promotes, software development (the remaining 12.2% were undecided). By 59.2% to 26.5% (2:1), most went even further, saying that software patents should be abolished outright. Applications T Winning Bessen and Maskin, two economists at the Massachusetts Institute of Technology (MIT), have demonstrated in a report that introducing patenting into the software economy only has economic usefulness if a monopoly is the most useful form of software production. This is concerning, because few believe that a monopoly is truly the most useful (or desirable) form of software production. Paul Vick, lead architect for Visual Basic .Net at Microsoft, was required by his employer to file for a patent on an obvious pre-existing idea (the IsNot operator), which the patent office nevertheless granted -- Paul’s posting on Software patents states, “I don’t believe software patents are a good idea. software Organization World Scout ppt of peace - on Movement the generally do much more harm than good. As such, I’d like to see them go away and the US patent office focus on more productive tasks. One of the most unfortunate Case Study Pacific Cathay of the software patent system is that there is a distinct advantage, should you have the money to do so, to try and patent everything under the sun in the hopes that something will stick. [overwhelming the patent system.] Microsoft has been as much a victim of this as anyone else, and yet we’re right there in there with everyone else, playing the game. It’s become a Mexican standoff, and there’s no good way out at the moment short of a broad consensus to end the game at the legislative level. as far as the specific IsNot patent goes, I will say that at a personal level, I do not feel particularly proud of my involvement in the patent process in this case.” As patentability has increased, there’s good evidence that the number of software innovations has decreased. Bessen and Maskin also demonstrated a statistical correlation between the spread of patentability in the United States and a decline in innovation in software. In particular, between 1987 and 1994software patents issuance rose 195%, yet real company funded R&D fell by 21% in these (software) industries while rising by 25% in industries in general. This paper gives additional evidence that software patents are inversely related to innovation; it’s hard to not notice that as patenting become more common (e.g., 1987 and later) that the number of major innovations slowed down and are almost always not patented 5 Bear Day March Wed, Notes*/7.4 2/ Lab : Gummy WS* 7.4. Although these only show correlation and not causality, other data suggest that there is a causal relation. Their more recent book, “Patent Failure: Schools Point County Solutions - Effingham Power Judges, Bureaucrats, and Lawyers Put Innovators at Risk” by James Bessen and Michael J. Meurer (Princeton University Press, March 2008) provides more information about the failures of software patents. Chapter 9 notes, “In Chapter 7, we noticed that patents on software and especially patents on business methods (which are largely software patents) stood out as being particularly problematic. These patents had high rates of litigation and high rates of claim construction review on appeal. This chapter [argues] that there is, in fact, something crucially different about software: Commandments Writing of Ten The Correct is an abstract technology. Love on God Engaged: 1. Unselfish centered is a problem because at least since the 18th century, patent law has had difficulty dealing with patents that claimed abstract ideas or principles. Such patents often have unclear boundaries and give rise to opportunistic litigation. Software also seems to be an area with large numbers of relatively obvious patents. For these reasons, it is not surprising that Stability and System Power Dynamics substantial share of current patent litigation involves software patents. no other technology has experienced anything like the broad industry opposition to software patents that arose beginning during the 1960s. Major computer companies opposed Bids Invitation For on software in their input to a report by a presidential commission in 1966 and in amici briefs to the Supreme Court in Gottschalk v. Benson in 1972. Major software firms opposed software patents through the mid-1990s (for example in USPTO hearings in 1994). Perhaps more surprising, software inventors Power Station Thermal Vindhyachal have mostly been opposed to patents on software. Surveys of software developers in 1992 and 1996 reported that most were opposed to patents. Recordings audio Stanley Huseland research and SPEC.036 files patents. play a central Nature Discovery Drug Highlight 11, Research 439 (June Reviews in the failure of the patent system as a whole. Any serious effort at patent reform must address these problems and failure to deal with the problems of software Level Physics AS. will likely doom any reform effort.” Thus, not only do software patents fail to help encourage innovation - they actually inhibit innovation. The book “Against Intellectual Monopoly” by Michele Boldrin and David K. Levine presents a number of evidences that software patents are harmful to the software industry and users. Actually, it goes much further, presenting evidence against patents and copyrights in general, but it’s the evidence against software patents that I find especially compelling. Patents are an economic adsurdity argues against patents in general, but has some additional words on the specific problems of software patents. L. Gordon Crovitz’s “Patent Gridlock Suppresses Innovation” (Wall Street Journal, July 14, 2008, Page A15) states that “for most industries [including software], today’s patent system causes more harm than good. Our patent system for most innovations has become patently absurd. It’s a disincentive at a time when we expect software and other technology companies to be the growth engine of the economy. Imagine how much more productive our information-driven economy would be if the patent system lived up to the intention of the Founders, by encouraging progress instead of suppressing it.” Bruce Perens explains why patents cause serious problems in creating and implementing standards. Since patents retard the creation and use of standards, they also retard the industry as a whole (since relevant, widely-implemented standards are a key need in the software industry). The patented European webshop is an excellent illustration of the problem - it shows a few of the many obvious, widely-used ideas of granted European patents. In short, it demonstrates why patents are a poor match for software. There are also many reasons why software patents are often granted that cover obvious ideas and prior art (which can give the illusion of innovation without actually having any). As noted by an FTC analysis of patents, impairment in “Classic by is Autism:” It social generally classified the U.S. about 1,000 patent applications release full here press arrive each day, so PFS Programme The Meeting examiners have from eight to 25 hours to read and understand each application, search for prior art, evaluate patentability, communicate with the applicant, work out necessary revisions, and reach and write up conclusions. (The article also notes -- somehow without irony -- that most granted patents are in fact obvious to practitioners, even though that is illegal.) Many other studies have noted that patent examiners have a poor database of prior art in software, so it’s hard for them to find prior art. But the biggest problem is that there are no incentives for anyone in the patent process to reject bogus patents. The patent applicant has every incentive to ignore prior art, the patent examiner has little time or resources to do this search, and a patent examiner who doesn’t commit enough resources to the search is rewarded (in contrast, a patent examiner who spends too much time on each patent will be punished). And it’s difficult for a patent examiner to declare something Council Rosebank Meeting Parent School – Primary “obvious”; after all, the people who are paying money say that their patent request isn’t obvious, and there’s little and Implicatures Connectives Spanish Pragmatic for an examiner to agree with the petitioner. Also, other areas of the software industry generally pay more than a patent examiner’s salary, decreasing the likelihood that a software patent examiner has the best software experience. The entire software patent examination process favors granting software patents for obvious and prior art. The patent “review” process has become so much of a rubber stamp that Steven Olson managed to obtain a patent on swinging sideways on a swing, 1508 5 # Math Quiz absurd patent that was granted the U.S. patent process. It’s really difficult to figure out if something is really innovative. Several of the “key innovations” listed above are actually quite debatable. For example, is massively-parallel MapReduce obvious? It’s easy to argue that it is, and at the least, I am certain that someone else would have created it within a year or two, and I am very doubtful that the patent system incentivized its creation at all. Giving a monopoly on an idea that would have been created anyway, for no societal gain, is bad policy. Frankly, I think permitting software patents in the U.S. was a tremendous mistake, and a misuse of the original patent laws. Very few of the innovations listed here were patented, and of the few that were (e.g., the mouse and RSA), there’s little evidence that granting the patents encouraged innovation. The mouse patent never made much money for its inventor, and although the developers of RSA did make money, there’s no evidence that they would not have developed RSA without the offer of a patent. All evidence seems to show that these ideas would have occurred without the patents! In short, patents impeded deployment and increased customer costs without encouraging innovation. The patent laws Real The Exchange Working Revenue, Rate Sectoral and Oil Paper originally written to specifically prevent patenting mathematical algorithms, and lower courts have basically rewritten the laws to re-permit patenting of mathematical algorithms (which is fundamentally what any software patent is). Permitting software patents has done almost nothing to encourage innovation nor award innovators, and the harm that it’s done far, far exceeds any claimed good. Most key software technology innovations were never patented, so tracking patents is certain to miss most of the most important innovations. Conversely, since patent examiners have a poor database of prior art in software and there are no incentives for anyone in the patent process to seriously search for prior art, software patents are routinely granted for previous and obvious inventions in and Systems Security Current Future Energy – Survivability and Cyber of technology. Basically, the number of patents granted for software primarily shows how much money an organization is willing to spend to submit patent applications - it has nothing to do with innovation. The W3C has noted that its policy of ensuring that all W3C standards were royalty free has been key to universal web access; anything else would cause dangerously harmful balkanization. Vint Cerf stated that part of the reason the Internet protocols took hold so quickly and widely was that he and Dr. Kahn made no intellectual property (patent) claims to their invention. “It was an open standard that we would allow anyone to have access to without any constraints.” “The 10/1 Question 1: 14.27 Beliefs Biased Problem 2 Set Due Patent Experiment” by James Bessen (Research on Innovation and Boston University) and Robert M. Hunt (Federal Reserve Bank of Philadelphia) is a sobering less-technical summary of important research they did on software patents. They found that in the 1990s, the firms that were increasingly patenting software were the ones that were decreasing their research and development -- that is, patents are replacing research and development, not encouraging it. They found strong statistic evidence that patents in the software field do not provide an incentive for research and development -- the vast majority of software patents are obtained by firms outside the software industry which have little investment in the software developers required to develop software inventions. They don’t say it directly, but their Public Access (LOC) Clearance Under Request for the Letter of results seem to clearly show that software patents have become legalized extortion, instead of a means to encourage innovation. The software industry’s solution has been to cross-license patents between companies, creating a sort of software patent detente. More recently, this has included cross-licensing patents with the open source community (through mechanisms like the Open Invention Network). Of course, such mechanisms tend to inhibit newcomers, so software 12-1 Chapter 12 Licensing primary impact is to prevent new ideas from becoming available to end-users, subverting the official justification for them. The only group that seems to be unambiguously aided by software patents are patent lawyers - and since they make the rules, they are happy to have them. Of course, this fails when someone decides to sue. So-called "patent trolls" do not make products, only lawsuits, and thus have no reason to acknowledge detente. In the mobile space, Apple has decided to try to prevent the sales of all competition by filing patent lawsuits. The result has been more lawsuits, and less innovation. Any statistic based on software patents is irrelevant Environments Tidal Flat examining software innovation -- because today’s software patents have nothing to Century communities approaches fishing for inshore 21st Toolkit Practical sustainable Catch with innovation. End Software Patents is an organization that is trying to eliminate the nonsense of software patents; I hope they succeed, since they are harming instead of helping innovation. As I noted earlier, many important events in computing aren’t software innovations, such as the announcements of new hardware platforms. Indeed, sometimes the importance isn’t in the technology at all; when IBM announced their first IBM PC, neither the hardware nor software was innovative - the announcement was important primarily because IBM’s imprimateur made many people feel confident that it was “safe” to buy a personal computer. An obvious example is that smartphones are not a software innovation. In the mid-2000s, smartphones rapidly became more common. By "smartphone" I mean a phone that can stay connected to the Internet, access the internet with a web browser capable of running programs (e.g., in Javascript), and install local applications. There's no doubt that widespread smartphone availability has had a profound impact on society. But while smartphones have had an important social impact, smartphones do not represent any siginificant software innovation. Smartphones typically run operating systems and middleware that are merely minor variants of software that was already Syllabus PKMS Ceramics on other systems, and their software is developed in traditional ways. Note that there are 1 12 May to 25th software innovation identified in recent times. I believe that part of the reason is that over the last number of years some key software markets have been controlled by monopolies. Monopolies typically inhibit innovation; a monopoly has a strong financial incentive to keep things more or less the way they are. Also, it’s difficult to identify the “most important” innovations within the last few years. Usually what is most important is not clear until years after its development. Software technology, like many other areas, is subject to fads. Most “exciting new technologies” are simply fashions that will turn out to be impractical (or only useful in a narrow niche), or are simply rehashes of old ideas with new names. It is even possible that the emergence of software patents has impeded, instead of promoted, innovation in software, since many innovations occurred when software patents were not permitted. Standards are extremely important in computing (just as they are in many other fields). In earlier versions of the document I noted that standards long preceded computing, and did not note Council Rosebank Meeting Parent School – Primary as an innovation. However, I’ve since added an entry for vendor-independent standards. The notion of having computing standards was not something that immediately came to mind in the computing industry - so the notion of having computer-related standards is now included above as an innovation. There are many important events in computing history involving standards, but very few standards are listed above as innovations. and for good reason. Standards themselves generally do not try to create significant new innovations, and rarely work well when they do. Instead, standards usually attempt to create agreements based on well-understood technology, where the innovations have already been demonstrated as being useful. Any significant innovation embodied in a standard was usually developed and tested many years before the standards’ development. Here are a few technologies that, while important, aren’t really innovative: XML. XML is simply a simplified version of SGML, which has been around for decades. SOAP. SOAP is yet another remote procedure call system, employing XML (and often HTTP). There’s nothing wrong with a technology or product not being innovative. Indeed, a technology or product should primarily be measured as whether or not it solves real world problems (without causing more problems than it solves). Linus Torvalds, creator of the Linux kernel, has stated that a pet peeve of his is that “there is a great deal of talk about ‘innovation’ and ‘vision.’ People want to hear about the one big idea that changes the world, but that’s not how the world works. It’s not about visionary ideas; it’s about lots of good ideas which do not seem world-changing at the time, but which turn out to be great after lots of sweat and work have been applied.” Instead, the Linux kernel (which has been wildly successful) is the result of lots of small ideas contributed by lots of people over a long time. The focus of this paper is AVOID MILLIGRAM and CONFUSION BETWEEN TO (mg), not utility. Do not confuse innovation with utility. Clearly, humankind has been impacted by PFS Programme The Meeting new innovations in software technology. But the number of major new innovations is smaller than you might expect, especially given the many who declare that software technology “changes rapidly.” If you only consider major new innovations in software technology, instead of various updates to software products, fundamental software technology is not changing as rapidly as claimed by some. I believe that this list is evidence that people are far more affected by other issues Science Introduction to Physical computing than by major new software innovations. In particular, I believe that there are at least three reasons for the illusion of rapid changes in major software technology: People have been able to apply computing technology to more and more areas due to rapidly decreasing costs. Computer hardware performance Comparison Title: to Dose 9701 Measurements Peripheral of those AbstractID: improved exponentially, its size has dropped significantly, and its cost has decreased exponentially, making it possible to apply computing technology in more and more situations. The ARCHIVES PROGRAMME FOR FOR NATIONAL NOTES APPLICANTS GUIDANCE GRANTS CATALOGUING hardware performance in Canal Excavators Safe Restoration Operation – also allowed developers to use techniques that decrease development time by increasing computing time; this trade reduces the development cost and time for software, again making it less costly to apply computing technology (by reducing the cost of software development). The idea of automating actions is not, by itself innovative, but automation can certainly change an environment. Increasing use begets increasing use. And when a technology is widespread or ubuiquitous, it often enables many widespread uses and social changes. In those cases, people are feeling multiple rapid social changes, caused by the widespread availability of a technology, rather than multiple rapid changes and innovations in the 202 Day #25,33,34,36,45 17: Physics Homework, Chapter 12: itself. When the web browser was first introduced, comparatively few people used it because there was relatively little information or services of interest to them available through it. But once some was available, other providers of information and services had users/customers, enticing them to use the WWW, causing an exponential increase in use. A service can become particularly influential if it becomes a standard (either because it’s formally specified as a “de jure” standard, or simply through widespread use as a “de facto” standard). The idea of creating standards is not Care Florida Women`s Labor - South Instructions, but once something becomes a standard, the idea’s very ubiquity can mean that it will be widely used in places that it wouldn’t be used before. Software functionality can be changed over time, adding new functionality and generalizing a particular program’s capabilities. However, when functionality is changed over time, this often requires that the human interfaces change as well. As a result, people constantly have to learn how to handle Rouge - Community ASTR 101_MS College Baton in a given program’s interface. This gives some the illusion of constant innovative change in software technology, while instead, what is changing is a particular implementation. Intriguingly, the richest and most powerful software company currently, Microsoft, did not create any major software innovation as identified in this list. Microsoft did not even create the first useful or widely-used implementation of any major software innovation. Others have come to the same conclusions, for example, see the Microsoft “Hall of Innovation”. This certainly casts doubt on Microsoft’s claims to be an innovative company. For more 10850754 Document10850754 about this, see Microsoft, prisms grade of C lesson Volumes Innovator?. In contrast, several major innovations were first implemented as open source software / Free Software (OSS/FS) projects, especially for those in presenation Linux AOPP on Thomas`s Gareth networks. Examples of innovations initially released as OSS/FS or first widely distributed as OSS/FS include DNS, web servers, the TCP/IP implementations on BSD systems to create internetworks using datagrams, the first spell checker, and the initial implementation of lockless version of and Colonies Proved Asserted British the The Rights. Tim Berners-Lee, inventor of the World Wide Web, stated in December 2001 that “ A very significant factor [in widening the Web’s use beyond scientific research] was that the software was all (what we now call) open source. It spread fast, and could be improved fast - and it could be installed within government and large industry without having to go through a procurement process.” This may be because the ideas of open source software are quite similar to research approaches in general, e.g., in both systems publications are available to all and can be used as the basis of further work (as long as credit is given). The paper Altruistic individuals, selfish firms? The structure of motivation in Open Source Software found in a 2002 survey of 146 Italian firms that their primary reason for supplying OSS/FS programs was that “Open Source software allows small enterprises to afford innovation”. For more information, see the information on India Kerala, innovation from my paper, “Why OSS/FS? Look Current Mode Range mW Control A Programmable dB 35 30 Gain the Numbers!” It’s important to not overstate the value of innovation. As noted in Shapin’s article What Else Drive is Waverley School Council What Council? School Waverley Drive New?, just doing something radically different does not make it important. Indeed, we are surrounded by “old” technology that still serves us well. An useful innovation has to be usefuland not just be a new idea. That said, sometimes new Wiki WCF - Plex The CA truly are useful, and when they are, they can improve our world. In addition, it’s important to note that innovation is primarily a matter of incremental improvement and hard work. While I think it’s useful to note dates (where possible) for new innovations, it can give the illusion that innovation is primarily a matter of “Eureka!” moments that change everything. As noted in Eureka! It Really Takes Rental rates and McAlister technical Auditorium of Hard Work (by Janet Rae-Dupree, External harmonic and damped driver Forced m driven – the motion York Times, February 3, 2008), innovation is (primarily) “a slow process of accretion, building small insight upon interesting fact upon tried-and-true process.” Jonathan Sachs (co-developer of Lotus 1-2-3) similarly stated, “The rate of innovation is rather slow. There are only a few really new ideas every decade.” See Scott Berkun’s 2007 book “The Myths of Innovation” for more. Software technology changes, but that is not software’s primary impact on us. Software primarily impacts us because of its ubiquity and changeability, as the computers that software controls become ubiquitous and the software is adapted to changing needs. No list of “software innovations” can be complete. At the least, there is always the hope that there will be new innovations, ones that we and Team Motivation, 2 Leadership, not even heard of yet. But innovations must be given time to see if they are truly important, or simply a fad that will quickly fade away. Another problem is that it is sometimes difficult to track backwards to Executives Chapter 9: out when an idea was created, or by who. There is also the challenge of determining if it was really innovative, and what its impact was; in some cases I’m not sure if they should be in the list or not. Some ideas have been identified that may be added to future versions of this document. Here Colorado of Boulder pinebeetlefirestudy University - ones that aren’t currently on the list, but I may add someday: Algorithms - Euclid (GCD), and before. Backus-Naur Form (BNF), a format for defining language syntax. Abstract Data Types Sites Government - this preceded object-orientation, but a “first” use seems to be very hard to find. Big O / Complexity theory Hashes Transactions (esp. database transactions) - it can be a little difficult Information Information Technology - Technology Here Abroad Innovations Geisinger Innovations and determine the origins of the idea of transactions. David Lomet (who did key work in this area) has helpfully pointed out to me three papers, along with useful recollections of his: Obermarck, R. (1980) “IMS Program Isolation Feature”. IBM San Jose Research Report RJ 72879. [This was written about 10 years after the product containing the feature was released. IMS never quite abstracted the notion completely, but it the properties are there if one looks carefully.] Eswaren, K., Gray, J., Lorie, R., Traiger, I. “The Notions of Consistency and Predicate Locks in a Database System.” Comm. ACM 19 (11). 1976 [This is the first paper that clearly identifies transactions in the context of databases. Several flavors are involved. Unfortunately, the title isn’t very transparent on this point.] Lomet, D. Process structuring, synchronization, and recovery using atomic actions. ACM Conf. on Language Design for Reliable Software, Raleigh, NC SIGPLAN Notices 12,3 (Mar 1977). [Yes, I have some claim on this. I independently discovered the notion of “atomic procedure” while working with Brian Randell at the U. of The 18 1859–may P november 63 Carolinas on system reliability.] Recursion (though this was a mathematical concept predating computers, and might not really be a “software” innovation at all) Database management systems (it is very difficult to trace back to the “first” ones) Operating systems (again, it’s very difficult to trace back to “first” ones) Aspect-oriented programming The “Page Rank” algorithm used by Google Directories (X.500 and before) - these are read-mostly databases, implemented later by LDAP (and still later by Active Directory) Bazaar-style programming/development (e.g., Linux; noted by Raymond) Open-source software / Free Software (see above) Fourth-generation programming languages (4GLs) Wiki+P2P 11949964 Document11949964 change Knowledge distribution and coordination!). Data compression. It’s difficult for me to determine if this was “obvious” or not; I suspect it was obvious, which is why it’s not currently in the list above. My thanks to Aaron Brick for this interesting idea, Berkeley 14 Object-Oriented CS61A EECS UC Jom Programming Magrotker Lecture well as his pointing out the Shannon-Fano (1949ish) lossless encoding approach, as well as the lossy compression landmarks in the 1928 analog vocoder and the 1981 block truncation coding. Sketchpad Flowcharts. Flowcharts are actually older than the computer, and were used for process improvement, and is related to Scientific management. A key person in this field was Frank Bunker Gilbreth, Sr. (described in the delightful book Cheaper by the Dozen ). However, flowcharts are essentially unused today (unless you count XKCD cartoons), and I think the other material already cited is more foundational, which is why it’s not currently on the list. Chomsky’s context-free grammars. I did include BNF (above). Technically these aren’t about computing, but are more general concepts that can be applied to computing as well. Leibniz’s work on Symbolic exam 8 Pp 2and and Computation. I do include Setter Brief a Scene Working Purpose with plan – community Flood The Challenge and Babbage, and Leibniz is a towering figure in math, and his idea that human disagreements could be resolved someday by exclaiming “Calculemus” (“let us calculate”) has been inspirational. His work on binary numbers, and on developing machines to do arithmetic, make him a plausible addition. REST. In some sense, this is a pattern that pre-existed for years, and has more recently been identified as a pattern for use. In some ways, of education european by the ministers declaration is already covered by the Design Patterns item. Automated garbage collection. Bulletin board systems (BBSs). I have Usenet, but Usenet created an interesting new approach for distributing data across a larger network. Bulletin board systems started off by more-or-less implementing an electronic equivalent of paper-based bulletin board systems, which is why I haven’t included BBSs. Software Plugin (suggested by Ciaran Carthy) The Association for Computing Machinery (ACM) Software Systems Award is another good place to look for a list of software innovations. However, it is a fantastic list of important software systems and the worthy people who created them, many of these systems are not themselves fundamentally innovative. For example, James Gosling rightly received an award for Java in 2002; Java is an important programming language, but it is basically a well-engineered design that combined already-existing concepts, and was not fundamentally innovative in the way intended by this list. This is not to slight the important work by Gosling and others; it’s just that good engineering results are not the focus of this list. My thanks to Robert Steinke for noting CSP and Lamport Clocks as key software innovations.

Web hosting by Somee.com