Oral History of Gordon Bell
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
PVB Weekly Market View the Fed a Dovish Or a Hawkish Cut 25 October
Macro Strategy | 25 October 2019 Weekly Market View 1 A Fed rate cut next week, with a dovish tone, is likely to further boost risk appetite, in our view Equities: US Q3 earnings from the financial and technology sectors have beaten forecasts, supporting our bullish view on US equities Bonds: Any decline in Treasury yields after the Fed meeting may be used to add EM USD exposure; EM local currency bonds look attractive The Fed – a dovish or a hawkish cut? FX: GBP, AUD, CAD look attractive as the USD peaks This commentary reflects the views of the Wealth Management Group of Standard Chartered Bank. Important disclosures can be found 1 in the Disclosures Appendix. Standard Chartered Bank weekly market view | 25 October 2019 Contents The Fed – a dovish or a hawkish cut? 1 What does this mean for investors? 4 What are the best opportunities if the USD is peaking? 5 Market performance summary 6 Economic and market calendar 7 Disclosures 8 Chart of the week: Markets pricing in a Fed cut on 31 October Probability of a 25bps Fed rate cut at the 31 October policy meeting based on money market pricing 95 80 65 50 Probability (%) Probability 35 20 Jul-19 Aug-19 Sep-19 Oct-19 October Fed meeting - probability of a cut Source: Bloomberg, Standard Chartered Editorial The Fed – a dovish or a hawkish cut? Global equity markets and commodities extended their rally over the past week amid further signs of progress in US-China trade As the risk rally extends with further signs of progress in US- talks China trade talks, the focus turns towards the Fed meeting on Benchmark market performance w/w* 31 October. -
Pdf and SANS '99 ( Are Worth a Read
motd by Rob Kolstad Dr. Rob Kolstad has long served as editor of ;login:. He is also head coach of the USENIX- sponsored USA Computing Olympiad. <[email protected]> Needs In the late 1960s, when the psychological world embraced behaviorism and psychoanalysis as its twin grails, Abraham Maslow proposed a hierarchy of needs. This hierarchy was brought to mind because I am hosting the Polish computing champion for a short visit, and he often asks questions of the sort, "Why would anyone need such a large car?" Maslow listed, in order: • Physiological needs, including air, food, water, warmth, shelter, etc. Lack of these things can cause death. • Safety needs, for coping with emergencies, chaos (e.g., rioting), and other periods of disorganization. • Needs for giving and receiving love, affection, and belonging, as well as the ability to escape loneliness/alienation. • Esteem needs, centering on a stable, high level of self-respect and respect from others, in order to gain satisfaction and self-confidence. Lack of esteem causes feelings of inferiority, weakness, helplessness, and worthlessness. "Self-actualization" needs were the big gun of the thesis. They exemplified the behavior of non-selfish adults and are, regrettably, beyond the scope of this short article. As I think about the context of "needs" vs. "wants" or "desires" in our culture, economy, and particularly among the group of readers of this publication, it seems that we're doing quite well for the easy needs (physiological needs and safety). I know many of my acquaintances (and myself!) are doing just super in their quest for better gadgetry, toys, and "stuff" ("whoever dies with the most toys wins"). -
Microkernel Mechanisms for Improving the Trustworthiness of Commodity Hardware
Microkernel Mechanisms for Improving the Trustworthiness of Commodity Hardware Yanyan Shen Submitted in fulfilment of the requirements for the degree of Doctor of Philosophy School of Computer Science and Engineering Faculty of Engineering March 2019 Thesis/Dissertation Sheet Surname/Family Name : Shen Given Name/s : Yanyan Abbreviation for degree as give in the University calendar : PhD Faculty : Faculty of Engineering School : School of Computer Science and Engineering Microkernel Mechanisms for Improving the Trustworthiness of Commodity Thesis Title : Hardware Abstract 350 words maximum: (PLEASE TYPE) The thesis presents microkernel-based software-implemented mechanisms for improving the trustworthiness of computer systems based on commercial off-the-shelf (COTS) hardware that can malfunction when the hardware is impacted by transient hardware faults. The hardware anomalies, if undetected, can cause data corruptions, system crashes, and security vulnerabilities, significantly undermining system dependability. Specifically, we adopt the single event upset (SEU) fault model and address transient CPU or memory faults. We take advantage of the functional correctness and isolation guarantee provided by the formally verified seL4 microkernel and hardware redundancy provided by multicore processors, design the redundant co-execution (RCoE) architecture that replicates a whole software system (including the microkernel) onto different CPU cores, and implement two variants, loosely-coupled redundant co-execution (LC-RCoE) and closely-coupled redundant co-execution (CC-RCoE), for the ARM and x86 architectures. RCoE treats each replica of the software system as a state machine and ensures that the replicas start from the same initial state, observe consistent inputs, perform equivalent state transitions, and thus produce consistent outputs during error-free executions. -
These Innovators Sail Against the Prevailing Winds, Discovering Whole New Worlds in Biotech and Software
FORTUNEMARCH 17, 2003 EXCERPT Heroes of manufacturing These innovators sail against the prevailing winds, discovering whole new worlds in biotech and software. by Gene Bylinsky Dan Dodge and Gordon Bell: When software really, really has to work Is software hopeless? Ask anyone whose computer has just con- to smart manufacturing and process-control engineers, who have fessed to an illegal operation or whose screen has locked up. De- installed more than one million QNX systems around the spite decades of effort, a wisecrack from the software industry’s world—and beyond. Cisco uses QNX to power some of its net- early days still stings: “If builders constructed buildings the way work equipment; Siemens uses it to run its medical systems. QNX programmers write software, the first woodpecker to come along enables the high-speed French TGV passenger trains to round would cause the collapse of civilization.” curves without tilting too far; it runs U.S. Postal Service mail- There’s one notable exception. As far as anyone can tell, soft- sorting machines, directs GE-built locomotives, and will soon ware created by a Canadian company called QNX Software Sys- control all of New York City’s traffic lights. The Federal Avia- tems simply doesn’t crash. QNX’s software has run nonstop with- tion Administration (FAA) has purchased 250 copies of QNX out mishaps at some customer sites since it was installed more for air-traffic control. And the system operates the Canadian- than a decade ago. As a delighted user has put it, “The only way built robotic arm on both the space shuttle and the interna- to make this software malfunction is to fire a bullet into the com- tional space station. -
Systemsevaluate Advanced Architectures for Large-Scale
DOCUMENT RESUME ED 344 869 IR 015 479 TITLE Federal High Performance Computing and Communications Program. The Department of Energy Component. INSTITUTION Department of Energy, Washington, D.C. Office of Energy Research. REPORT NO DOE/ER-0489P PUB DATE Jun 91 NOTE 51p.; Color photographs will not reproduce well. AVAILABLE FROM National Technical Information Service, U.S. Department of Commerce, 5285 Port Royal Rd., Springfield, VA 22161. PUB TYPE Information Analyses (070) -- Reports - Descriptive (141) EDRS PRICE MF01/2CO3 Plus Postage. DE3CRIPTORS Agency Cooperation; *Computer Networks; Computer Science; Computer Software; *Computer System Design; Databases; Federal Programs; *Research and Development; Technological Advancement IDENTIFIERS *High Performance Computing; *Supercomputers ABSTRACT This report, profusely illustrated with color photographs and other graphics, elaborates on the Department of EnergY (DOE) research program in High Performance Computing and Communications (HPCC). Tte DOE is one of seven agency programs within the Federal Research and Development Program working on HPCC. The DOE HPCC program emphasizes research in four areas: (1) HPCC Systemsevaluate advanced architectures for large-scale scientific and engineering applications; (2) Advanced Software Technology and Algorithmsresearch computational methods, algorithms, and tools; develop large-scale data handling techniques; establish HPCC research centers; and exploit extensive teaming among scientists and engineers, applied mathematicians, and computer scientists; () National Research and Education Networkresearch and develop high-speed computer networking technologies through a multiagency cooperative effort; and (4) Basic Research and Human Resources--encourage research partnerships between national laboratories, industry, and universities; support computational mathematics and computer science research; establish research and educational programs in computational science; and enhance K through 12 education. -
A Bibliography of Publications in Communications of the ACM : 1970–1979
A Bibliography of Publications in Communications of the ACM : 1970{1979 Nelson H. F. Beebe University of Utah Department of Mathematics, 110 LCB 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Tel: +1 801 581 5254 FAX: +1 801 581 4148 E-mail: [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe/ 28 January 2021 Version 2.55 Title word cross-reference [Ehr74]. RC [Bou76, Mar72a]. R × C [Bou74, Han75a]. sin(x)=x [GK70b, Gau66]. t [Hil70a, Hil70b, Hil73a, Hil81a, Hil81b, eL79b]. wew = x [FSC73]. w exp(w)=x #9627 [GH79, Lai79]. [Ein74]. X + Y [HPSS75]. 0 [Fia73]. 1 [Fia73]. 2n [IGK71]. S -Distribution [Hil70a, Hil81a, eL79b]. -f AX + XB = C [BS72b]. [a ;b ] [FW78a]. i i [Sal72c]. -Quantiles [Hil70b, Hil81b]. cos(x)=x [GK70b, Gau66]. ex=x -Splines [ES74]. -word [IGK71]. [GK70b, Gau66]. Ei(x) [Pac70]. Ei(x) [Ng70, Red70]. f(x)=A cos(Bx + C) 1 [Rus78]. 1.5 [Bak78b]. 10 [Sp¨a70b]. g [ES74]. i [Bro76, FR75a]. R 1 [BKHH78, BBMT72]. 149 [Mer62]. 176 [exp(−ct)dt=(t)1=2(1 + t2)] [Act74]. k 0 [Art63, Sch72c]. 179 [BB74, Lud63]. 191 [Fox75, Law77]. K (z) [Bur74]. K (z) 0 1 [Kop74, Rel63]. 195 [Sch72d, Thu63]. 1966 [Bur74]. L [BR74, FH75, RR73a]. m 1 [Ame66]. [LT73, Cha70a]. n [Bra70a, Bra70b, Bro76, FR75a, LT73, RG73, Wag74, Cha70a]. O(n) 2048-Word [Wil70a]. 219 [Kas63]. 222 [Chi78]. pn [Ack74]. [Sal73c]. [Gau64a]. 236 [Gau64b]. 245 [Flo64, Red71]. f(f(f(···f(x) ···))) [Sal73c]. R 1 2 246 [Boo64]. -
What We Learned from the PDP-11
ABSTRACT Gordon Bell, William Il. Strecker November 8, 1975 COMPUTER STRUCTURES: WHAT HAVE WE LEARNED FROM THE PDP-ll? Over the FDP-11’S six year life behave in a particular way? about 20,000 specimens have been Where does it get inputs? HOW built based on 10 species (models). does it formulate and solve Al though range was a design goal, problems? it was unquantified; the actual range has exceeded expectations 3. The rest of the DEC (5OO:l in memory size and system organization--this includes price]. The range has stressed the applications groups assoc ia ted baa ic mini (mall computer with market groups # sales, architecture along all dimensions. service and manufacturing. The marn PM.5 structure, i.e. the UNIBUS, has been adopted as a de 4. The user, who receives the facto standard of interconnection final OUtQUt. for many micro and minicomputer systems. The architectural Note, that if we assume that a experience gained in the design and QrOduc t is done sequentially, and use of the PDP-11 will be described each stage has a gestation time of in terms Of its environment about two years, it takes roughly (initial goals and constraints, eight years for an idea from basic technology, and the organization research to finally appear at the that designs, builds and user’s site. Other organizations distributes the machine). ala0 affect the design : competitors (they establish a deaign level and determine the product life): and government IsI 1.0 TNTRODUCTTON and standards. There are an ever increasing number Although one might think that of groups who feel compel led to computer architecture is the sole control all products bringing them determinant of a machine, it is all common norm : the merely the focal point for a government (“5) , testing groups such specification. -
Gordon's Personal View of Personal Computing: Before the PC
Gordon’s Personal View of Personal Computing: before the PC Vintage Computer Society 27 September 1998 Gordon Bell [email protected] http://www.research.microsoft.com/~gbell Apple II First personal computer Micral In the beginning: Manchester “Baby” ran the first program 22 June 1948 English Electric Deuce Console 1955 Whirlwind c1953 … 1st generation, 16-bit word; 4 KB memory; 8 K drum Whirlwind begot TX-O/TX-2 begot DEC PDP-1 Real time, first compiler, ECAD, text editor Whirlwind console, drum, 1 Kw core SAGE Control Room c 1962. Whirlwind used for first experiments. SAGE (Semi-Automatic Ground Environment) Operator Console TX-0 Console c1959… one of the first transistorized personal computers Speech, handwriting recognition, neuro data analysis, etc. Interactive editors, debuggers, etc. MIT Speech group with TX-0, c1959. DEC Computer before PDP-11 1957 1961 1963 DEC PDP-1 c1961 Wes Clark & LINC c1962: Personal computers for bio-medical research PDP-5 c1964: PDP-8 predecessor Process control, real time experiments. Fortran ran in 4 K, 12 bit words Gbell with LINC and PDP-8 c1965 PDP-8: first mini First OEM computer. OS/8 (from timesharing) begot RT-11 begot CPM PDP-8 Modules PDP-8/E PDP-8 and Linc Family Tree PDP-8 12 bit word price (t) PDP-8 prices (t) Timesharing: given everyone their own, low cost, personal computer PDP-6 c1965 : First commercial time shared computer. Gbell & Alan Kotok PDP-6 Development team c1965 PDP-6/10/ DECsystem 10/20 family tree TThheerree iiss nnoo rreeaassoonn aannyyoonnee wwoouulldd wwaanntt aa ccoommppuutteerr iinn tthheeiirr hhoommee. -
Thesis May Never Have Been Completed
UvA-DARE (Digital Academic Repository) Digital Equipment Corporation (DEC): A case study of indecision, innovation and company failure Goodwin, D.T. Publication date 2016 Document Version Final published version Link to publication Citation for published version (APA): Goodwin, D. T. (2016). Digital Equipment Corporation (DEC): A case study of indecision, innovation and company failure. General rights It is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), other than for strictly personal, individual use, unless the work is under an open content license (like Creative Commons). Disclaimer/Complaints regulations If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the Library know, stating your reasons. In case of a legitimate complaint, the Library will make the material inaccessible and/or remove it from the website. Please Ask the Library: https://uba.uva.nl/en/contact, or a letter to: Library of the University of Amsterdam, Secretariat, Singel 425, 1012 WP Amsterdam, The Netherlands. You will be contacted as soon as possible. UvA-DARE is a service provided by the library of the University of Amsterdam (https://dare.uva.nl) Download date:26 Sep 2021 Digital Equipment Corporation (DEC) (DEC) Corporation Digital Equipment David Thomas David Goodwin Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure David Thomas Goodwin Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure David Thomas Goodwin 1 Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure ACADEMISCH PROEFSCHRIFT ter verkrijging van de graad van doctor aan de Universiteit van Amsterdam op gezag van de Rector Magnificus prof. -
Bell's Law of Computer Classes
Bell’s Law; P,M,S Structures; Rules of thumb; and Taxonomies 1957-1998. 41 yrs. 4 generations: Tubes > transistors > ICs, VLSI (micros) > clusters - winner take all How computer classes form, evolve …and die (according to economically based laws) Gordon Bell Microsoft Research, Silicon Valley Laboratory References Moore’s Law http://www.computerhistory.org/semiconductor/timeline/1965-Moore.html Bell’s Law: http://research.microsoft.com/research/pubs/view.aspx?0rc=p&type=technical +report&id=1389 Bell, C. G., R. Chen and S. Rege, "The Effect of Technology on Near Term Computer Structures," Computer 2 (5) 29-38 (March/April 1972). IEEE History Center's Global History Network: http://ieeeghn.org/wiki/index.php/STARS:Rise_and_Fall_of_Minicomputers In retrospect…by 1971, the next 50 years of computing was established 1. Moore’s Law (1965) transistors/die double every 18 mos. 2. Intel 4004, Processor-on-a-chip (1971) Clearly, by 1978 16-bit processor-on-a-chip 3. Bell et al 1971 observation...computer evolution 1. Computers evolve at constant price (Moore’s Law) 2. Computer clases form every decade (Bell’s Law) New technology, manufacturers, uses and markets How I think about computers • P,M,S describes architectures i.e. the components and how they are interconnected and interact – Reveals structure (size, cost, performance, power, etc.) – Parallelism, bottlenecks, and rules of thumb – Functional evolution to compete with larger computers • Bell’s Law determines classes birth & death • Rules of thumb determine goodness • Taxonomies enumerate alternatives A Walk-Through Computer Architectures from The Largest & Fastest to the Digestible Computers have evolved from a bi-furcation of: • calculating (P) aka scientific and record keeping (M) aka commerce to • control (K), • interfacing (T/Transduction) including GUIs, NUI, and • Communication (L), switching (S) and networking (N) Every information carrier from greeting cards to phones is an embedded computer. -
Oral History Interview with Joseph F. Traub
An Interview with JOSEPH F. TRAUB OH 94 Conducted by William Aspray on 29 March 1985 Columbia University (New York, NY) Charles Babbage Institute The Center for the History of Information Processing University of Minnesota, Minneapolis Copyright, Charles Babbage Institute 1 Joseph F. Traub Interview 29 March 1985 Abstract The main topic is institutions in computing. Traub begins by discussing why computer science has developed as a discipline at some institutions but not others. Institutions that are highlighted include Stanford, Berkeley, University of Pennsylvania, MIT, and Carnegie-Mellon. Traub discusses his experiences as chairman of the computer science departments at Carnegie-Mellon and later Columbia. Other topics include: industrial and government funding of computer science departments (in particular the role of the Advanced Research Projects Agency of the Defense Department); the relationships between academic centers, such as M.I.T., Stanford, Columbia, and Carnegie-Mellon; and the importance of educational institutions to regional centers of industrial computing. At the end of the interview Traub returns to a topic of his earlier interviews, his experiences at Bell and Watson Laboratories. 2 JOSEPH F. TRAUB INTERVIEW DATE: 29 March 1985 INTERVIEWER: William Aspray LOCATION: Columbia University (New York, NY) ASPRAY: This is a session on the 29th of March, 1985, with Joseph Traub in his office at Columbia University. It is the third in a series of interviews, and the main topic in this session is institutions in computing. Why don't we start by talking about why certain universities - Pennsylvania, Harvard, Columbia, which had strong early activities in computing - didn't develop into first-rate research and teaching centers in computer science? TRAUB: It seems to me that in each of the institutions, that have become the major centers one can usually identify one or two people who were responsible. -
Computing History: a Personal and Industry View
or attempted designs; seven reaIly suc- ceeded, about 20 are still trying, and a COMPUTING HISTORY: A whoIt flock are no longer with us. including American Computet, Atron, BIT, and Viatron. With some under- PERSONAL AND INDUSTRY standing of the historic generational patterns my goal was to get DEC into VIEW/GORDON BELL large scale integrated circuits and to establish the YAX line as a new stan- lis. and Herbert Simon wrote a letter to dard. And ironically, this year 20 years Science and identified computer sci- after the first PDP-8 was built, sales of ence. The next steps, what we now call the machine were higher than ever “the third and fourth generations’’ weren’t at all clear. At Carnegie, Allen Newel1 and I collected materials and years objects from past machines to build Ironically, his year 20 theories. This resulted in a book en- 1 der he fint PDP$ was titled Computer Srructuras that in- fluenced at least two generations of built des of the muchine computer architects. The concepts of the DEC Unibus and general registers were higher hnever. came from this work. Other Carnegie alumni extended and implemented thae ideas in subsequent (and future) since it is implemented on a single chip DEC computers. These developments and embedded in a word processor. came from a deep knowIedgc of past Now one of my goals is to con- computers, and how they were used sider not just the development of a sin- and gave some insights about the fu- gle company, but of the entire industry ture trajectory of computer evolution.