DOCSLIB.ORG

Taligent:Taligent: Whatwhat Wentwent Wrong?Wrong?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Taligent:Taligent: Whatwhat Wentwent Wrong?Wrong? Taligent:Taligent: WhatWhat WentWent Wrong?Wrong? JackJack D.D. GrimesGrimes August,August, 2003,2003, 1010 yearsyears later….later…. HOT Chips 15, Stanford, CA 66 minuteminute videovideo WhatWhat isis aa “Taligent?”“Taligent?” SimilarSimilar toto Java,Java, crosscross--platform,platform, writewrite onceonce runrun anywhere,anywhere, 17001700 classes,classes, fullyfully OO,OO, butbut C++,C++, 22 millionmillion LOCLOC SimilarSimilar toto OSOS X,X, i.e.,i.e., MachMach OS,OS, "classic""classic" environmentenvironment ++ newnew OOOO appapp environmentenvironment runningrunning onon samesame kernel;kernel; SimilarSimilar toto BeOS,BeOS, interactive,interactive, multimedia,multimedia, 3D,3D, sound,sound, animationanimation Well,Well, wewe diddid somesome thingsthings rightright DemoDemo ofof thethe texttext && i18ni18n systemsystem isis partpart ofof 33--44 hourshours ofof videovideo onon TaligentTaligent TechnologyTechnology VideoVideo createdcreated inin 19931993 byby jdg,jdg, voice/demovoice/demo byby TomTom Chavez,Chavez, applicationsapplications dudedude ThisThis capabilitycapability isis partpart ofof thethe SunSun JDK,JDK, v1.1v1.1 andand laterlater (years(years ago)ago) SawSaw aa similarsimilar demodemo ~2~2 yearsyears agoago atat aa SunSun HeadquartersHeadquarters JavaJava BriefingBriefing AndAnd …… 140+140+ USUS patents,patents, moremore internationalinternational HoldingHolding company,company, OTLCOTLC HowHow toto valuevalue thethe asset?asset? LicensesLicenses SunSun JDKJDK forfor text/internationaltext/international subsystemsubsystem SunSun JDKJDK forfor 2D2D graphicsgraphics OracleOracle forfor text/int’ltext/int’l NetscapeNetscape forfor text/int’ltext/int’l HPHP forfor C++C++ compilercompiler WhatWhat wentwent wrong?wrong? InIn 1992,1992, aa “deal”“deal” waswas struckstruck betweenbetween JohnJohn SculleySculley andand JimJim Cannavino,Cannavino, 50/5050/50 JVJV Apple/IBMApple/IBM 170+170+ peoplepeople whenwhen thethe doorsdoors openedopened 400+400+ highhigh waterwater markmark (including(including contractors)contractors) JoeJoe GG appointedappointed CEOCEO ofof Taligent,Taligent, 30yr30yr IBMIBM veteran,veteran, OS/2OS/2 championchampion GetGet eveneven withwith BillBill GG forfor OS/2OS/2 C++,C++, neededneeded forfor systemsystem developmentdevelopment butbut wrongwrong forfor targettarget appapp developersdevelopers SumSum ofof everyone’severyone’s requirementsrequirements == resultresult waswas tootoo big,big, slow,slow, complexcomplex TooToo manymany cookscooks AppleApple -- didn’tdidn’t carecare thatthat muchmuch lost interest after Sculley left + Mac antibodies + wanted a client, media-rich OS IBMIBM -- strongstrong interest,interest, ownown agendaagenda really wanted technology farm for own products + expected to control the outcome while getting others to share costs + not committed to Apple partnership once Cannavino left + wanted a enterprise, client/server OS HPHP -- seriouslyseriously interestedinterested inin technologytechnology worried about missing the OO boat + Sun and HP due diligence for about a year, HP bought in, Sun didn't => HP lost interest TaligentTaligent -- makemake aa standalonestandalone businessbusiness andand unseatunseat MicrosoftMicrosoft withwith aa newnew OSOS TheThe “Big“Big Switch”Switch” HadHad aa functioningfunctioning standstand--alonealone OS,OS, gotgot redirectedredirected toto Mach,Mach, thenthen redirectedredirected toto dropdrop OSOS altogetheraltogether (claiming(claiming “no“no oneone wantswants aa newnew OS,”OS,” eveneven thoughthough subsequentlysubsequently therethere waswas NT,NT, OSOS X,X, Linux,Linux, Java,Java, etc.)etc.) AppleApple andand IBMIBM engineersengineers started,started, andand failedfailed at,at, theirtheir ownown effortsefforts likelike OpenOpen DocDoc toto dodo thethe “same”“same” thingthing (frameworks)(frameworks) forfor theirtheir existingexisting OS’sOS’s TaligentTaligent miscmisc Too many smart CS people, not product savvy Run like a big company, not a start-up Performance bonuses, but no stock options Business model problem (from too many cooks) Spent $250 Million in 4 years of JV, too much money $7-8 Million for furnishing of main building on De Anza Patent portfolio could stop existing companies Joe G bails, Dick Guarino comes in with new direction and new biz model, but he dies, and so does Taligent. Taligent acquired by IBM, wholly owned subsidiary, then absorbed, logo gone. :-(.
Load more

Recommended publications
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Rights Reserved. Permission to Make Digital Or Hard Copies of All Or Part Of
    Copyright © 1994, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 Microsoft Windows NT And The Competition for Desktop Computing January 1994 Department ofElectrical Engineering and Computer Sciences University ofCalifornia Berkeley, California 94720 Abstract This report contains two papers, An Introduction to Microsoft Windows NT And Its Competitors, and The Status ofWindows NT and Its Competitors At The End of1993. The first paper, written in April 1993,presents an overview of the technology of Windows NT, and analyzes the competitors and competitive factors in the desktop operating system race.
    [Show full text]
  • Moving FLASK to BSD Systems
    MovingMoving FLASKFLASK toto BSDBSD SSystemsystems SELinux Symposium 2006 Chris Vance Information Systems Security Operation, SPARTA, Inc. Vance_20060301_01 Overview • Security Frameworks • A Brief History • SELinux Inspired… – Security Enhanced BSD – Security Enhanced Darwin Vance_20060301_02 Security Frameworks • Traditional UNIX security isn’t enough – OS hardening – Mandatory protection – Flexible, manageable, scalable protection • Support required in the operating system for new security services – Costs of locally maintaining security extensions are high – Framework offers extensibility so that policies may be enhanced without changing the base operating system • There does not appear to be one perfect security model or policy – Sites may have different security/performance trade-offs – Sites may have special local requirements – Vendors unlikely to adopt a single policy • Bottom Line: Frameworks for Linux, FreeBSD, Darwin Vance_20060301_03 How We Got Here… Vance_20060301_04 Focus and Reuse • Don’t “reinvent” security – Learn from the past – The research is often decades old – A good design is durable, doesn’t require constant change – FLASK hasn’t changed much recently, what’s that mean? • Leverage existing technology, focus on “new” issues – Focus on improving operating system security – Spend the time to get Frameworks correct – Work with vendor for acceptance – Develop rule sets that work – Develop effective tools to manage policy • Do innovate – Don’t stop thinking! – Don’t squash new ideas – Re-factor old ideas Vance_20060301_05
    [Show full text]
  • Automatic Graph Drawing Lecture 15 Early HCI @Apple/Xerox
    Inf-GraphDraw: Automatic Graph Drawing Lecture 15 Early HCI @Apple/Xerox Reinhard von Hanxleden [email protected] 1 [Wikipedia] • One of the first highly successful mass- produced microcomputer products • 5–6 millions produced from 1977 to 1993 • Designed to look like a home appliance • It’s success caused IBM to build the PC • Influenced by Breakout • Visicalc, earliest spreadsheet, first ran on Apple IIe 1981: Xerox Star • Officially named Xerox 8010 Information System • First commercial system to incorporate various technologies that have since become standard in personal computers: • Bitmapped display, window-based graphical user interface • Icons, folders, mouse (two-button) • Ethernet networking, file servers, print servers, and e- mail. • Sold with software based on Lisp (early functional/AI language) and Smalltalk (early OO language) [Wikipedia, Fair Use] Xerox Star Evolution of “Document” Icon Shape [Wikipedia, CC BY-SA 3.0] 1983: Apple Lisa [Wikipedia, CC BY-SA 2.0 fr] Apple Lisa • One of the first personal computers with a graphical user interface (GUI) • In 1982, Steve Jobs (Cofounder of Apple, with Steve Wozniak) was forced out of Lisa project, moved on into existing Macintosh project, and redefined Mac as cheaper, more usable version of Lisa • Lisa was challenged by relatively high price, insufficient SW library, unreliable floppy disks, and immediate release of Macintosh • Sold just about 10,000 units in two years • Introduced several advanced features that would not reappear on Mac or PC for many years Lisa Office
    [Show full text]
  • Operating System Structure
    Operating System Structure Joey Echeverria [email protected] modified by: Matthew Brewer [email protected] Nov 15, 2006 Carnegie Mellon University: 15-410 Fall 2006 Overview • Motivations • Kernel Structures – Monolithic Kernels ∗ Kernel Extensions – Open Systems – Microkernels – Exokernels – More Microkernels • Final Thoughts Carnegie Mellon University: 15-410 Fall 2006 1 Motivations • Operating systems have a hard job. • Operating systems are: – Hardware Multiplexers – Abstraction layers – Protection boundaries – Complicated Carnegie Mellon University: 15-410 Fall 2006 2 Motivations • Hardware Multiplexer – Each process sees a “computer” as if it were alone – Requires allocation and multiplexing of: ∗ Memory ∗ Disk ∗ CPU ∗ IO in general (network, graphics, keyboard etc.) • If OS is multiplexing it must also allocate – Priorities, Classes? - HARD problems!!! Carnegie Mellon University: 15-410 Fall 2006 3 Motivations • Abstraction Layer – Presents “simple”, “uniform” interface to hardware – Applications see a well defined interface (system calls) ∗ Block Device (hard drive, flash card, network mount, USB drive) ∗ CD drive (SCSI, IDE) ∗ tty (teletype, serial terminal, virtual terminal) ∗ filesystem (ext2-4, reiserfs, UFS, FFS, NFS, AFS, JFFS2, CRAMFS) ∗ network stack (TCP/IP abstraction) Carnegie Mellon University: 15-410 Fall 2006 4 Motivations • Protection Boundaries – Protect processes from each other – Protect crucial services (like the kernel) from process – Note: Everyone trusts the kernel • Complicated – See Project 3 :) – Full
    [Show full text]
  • Chapter 2 Operating System Structures
    Operating Systems Associate Prof. Yongkun Li 中科大-计算机学院 副教授 http://staff.ustc.edu.cn/~ykli Chapter 2 Operating System Structures 1 Objectives • Operating System Services – User Operating System Interface – System Calls • Operating System Structure • Operating System Design and Implementation • MISC: Debugging, Generation & System Boot 2 Operating System Services Services Overview, User Interface 3 Operating System Services • Operating systems provide – an environment for execution of programs and – services to programs and users • Services may differ from one OS to another • What are the common classes? – Convenience of the user – Efficiency of the system 4 Overview of Operating System Services 5 OS Services for Helping Users • User interface - Almost all operating systems have a user interface (UI). – Three forms • Command-Line (CLI) – Shell command • Batch – Shell script • Graphics User Interface (GUI) – Windows system 6 OS Services for Helping Users • Program execution – Load a program into memory – Run the program – End execution • either normally or • abnormally (indicating error) 7 OS Services for Helping Users • I/O operations - A running program may require I/O, which may involve a file or an I/O device – Common I/Os: read, write, etc. – Special functions: recording CD/DVD • Notes: Users usually cannot control I/O devices directly, so OS provides a mean to do I/O – Mainly for efficiency and protection 8 OS Services for Helping Users • File-system manipulation - The file system is of particular interest – OS provides a variety of file systems • Major services – read and write files and directories – create and delete files and directories – search for a given file – list file Information – permission management: allow/deny access 9 OS Services for Helping Users • Communications: information exchange between processes – Processes on the same computer – Processes between computers over a network • Implementations – Shared memory • Two or more processes read/write to a shared section of mem.
    [Show full text]
  • Darwin: Mac OS X's Core OS
    ADC April 2001 3/8/01 1:57 PM Page 1 Apple Developer Connection Direct Darwin: Mac OS X’s Core OS eneath Mac OS X’s user-friendly and attractive user interface, Most of the reference documents can be Aqua, and the application frameworks (Classic, Carbon and found in the /Developer/Documentation/ BCocoa) is Darwin: Mac OS X’s core OS. Unseen by users, Kernel directory on any Mac OS X system Darwin provides a strong yet flexible foundation with features like with the Mac OS X Developer Tools package preemptive multitasking, protected memory and real-time support installed. that make Mac OS X a truly modern operating system. The focus of this article is to provide a brief overview of Components of Darwin Darwin and its components as well as give an introduction to Just like in the old Reese’s Peanut Butter developing kernel extensions—modules that extend Darwin’s Cups commercials (“You’ve got chocolate in functionality. For more in-depth information, you should read my peanut butter… No, you’ve got peanut butter on my choco- Inside Mac OS X: Kernel Environment which is available, along late!”), Darwin blends a mixture of mature industry standard com- with other documents referred to in this article, on the Apple ponents such as Mach and BSD with Apple-engineered components Developer Connection (ADC) web site in the Mac OS X to provide Mac OS X with a stable, reliable and extensible founda- Documentation section: tion. Darwin consists of five main components: Mach, I/O Kit, File http://developer.apple.com/techpubs/macosx/macosx.html System, Networking and BSD.
    [Show full text]
  • This Is a Fairy Tale •.• NOT! a Primer on Moving SAS® Applications
    This is a Fairy Tale•.• NOT! A Primer on Moving SAS® Applications Across Graphical Operating Systems James Hefner, Entergy Corporation, Beaumont, TX lineup. The PowerPC's PowerOpen operating system should be ABSTRACT able to run Windows, Windows NT, OS/2, Macintosh, and UNIX applications unmodified (using SoftPC to run Windows & OS/2 Currently, most SAS Software application developers have on~ apps). Current plans are to offer these new machines at prices one or two graphical operating systems (such as Microsoft that are highly competitive with the current top-of-the-!ine WindowsTN, or OSFlMoti~ to support. However, the pending offerings by IBM PC manufacturerS and Apple, nol 10 mention release of the SAS System for the Apple® Macintosh®I and the UNIX workstations. This could mean a change in the platform you introduction of new hardware and software such as the PowerPC are currently using, as well as the ability (or need) to be able to and Wabi, means that application developers may have to use and write applications using any of the five operating support two or more graphical operating systems. systems. This paper is intended to assist application developers, both in New Graphical Operating Systems the teaching of the fundamentals of graphical operating systems, and in Ihe moving of SAS/Af® and SAS/EIS® applicalions from In addition to the platforms mentioned above, Apple and IBM are one operating system to another. currently working on the Taligent operating system, which will have an object-oriented, graphical front end. IBM is also INTRODUCTION discussing porling its object·orienled 0512 2.x Workplace Shell 10 a new ver.sion of PC DOS® and AIX®, IBM's version of UNIX (to If you are a SAS' application developer, you may currently be be called Workplace OS).
    [Show full text]
  • Mach-O Internals
    Mach-O Internals William Woodru February 10, 2016 1 / 31 General Agenda 1. Who are you? 2. What is Mach-O? 3. An Extremely Brief History of Mach and Mach-O 4. Structure of a Mach-O File 5. Quirks Encountered 6. Concluding Notes 2 / 31 Who are you? My name is William Woodru. I'm a Computer Science major and Philosophy minor at the University of Maryland, College Park. Outside of school, I'm a member of the Homebrew project and a regular contributor to several open source groups. My work for Homebrew is largely concerned with the underlying system interface and reconciling OS X's intricacies/irregularities with the package manager. 3 / 31 What is Mach-O? Mach-O is the Mach Object binary format. Mach-O is used primarily by Apple in OS X and iOS. Apps on both platforms are really just directory trees containing Mach-O binaries and resources (fonts, icons, congurations). Metadata is stored in a number of places, but mainly within bundled plists (XML) and the binaries themselves. Like its cousins on Linux (ELF) and Windows (PE), Mach-O supports multiple object types: I Executable I Core dump I Shared library/object I Prelinked object le I etc. 4 / 31 . and multiple architectures: I m68k/m88k (yes, it's still supported!*) I x86 I AMD64 I POWER I ARMv6/7/8 Unlike ELF or PE, Mach-O has been extended to allow multi-architecture fat binaries. This has resulted in some interesting properties not shared by the other two. More on that later.
    [Show full text]
  • Volume 15, 1~L~Mber 2 April 1994
    ISSN 1035-7521 AUUG Inc. Newsletter Volume 15, 1~l~mber 2 April 1994 Registered by Australia Post, Publication Number NBG6524 The AUUG incorporated Newsletter Volume 15 Number 2 April 1994 CONTENTS AUUG General Information ...................... 3 Editorial ............................ 5 AUUG President’s Page ....................... 6 AUUG Corporate Sponsors - A New Level of Participation ............ 7 AUUG Institutional Members ..... : ............... 8 Letters to the Editor ........................ 11 Announcements AUUG Appoints New Business Manager ................ 15 AUUG Freephone Number .................... 16 McKusick does Oz T-shirt .................... 17 Call for Articles for the Australian .................. 18 AUUG & Zircon Systems Reach Agreement ............... 19 AUUG & the Express Book Store Reach Agreement ............ 20 AUUG Local Chapters AUUG Regional Contacts .................... 21 AUUG Inc. - Victorian Chapter ................... 22 Update on AU-tJG Inc. - Victorian Chapter Activities Stephen Prince . 23 From the Western Front Janet Jackson .... 24 WAUG - Meeting Reviews Adrian Booth .... 25 1994 Perth AUUG Summer Conference Overview Adrian Booth .... 26 Impressions of the 1994 Perth AUUG Summer Conference Janet Jackson .... 28 AUUG NSW Chapter Julian Dryden .... 30 AARNet Mail Affiliation., ...................... 31 Book Reviews .......................... 35 Prentice Hall Book Order Form ................... 41 WOodsLane Information ..................... 42 Open System Publications ...................... 43 !AUUGN
    [Show full text]
  • Michael J. Harper Standalone Code
    Michael J. Harper Standalone Code LLC 57195 Beaver Drive, PO Box 3846 (541) 362-1840 Sunriver OR 97707 [email protected] @doktahahpah, @standalonecode, www.github.com/mharper, www.standalonecode.com Summary I have been a software developer since 1982 and an independent contractor/consultant since 1992. For the past several years, I have focused on two areas of development: mobile development with iOS and Android and web development with Ruby on Rails. I conceived and implemented the TRX FORCE app — the 12-week conditioning program designed for the US Military — on both iOS and Android — which appeared in the Apple "Strength" commercial. In addition, I have collaborated on the Norton Online Backup iOS app and I built an app named “Circle 8” that helps tourists find their way around Sunriver, OR and its 33+ miles of bike paths. Another project was a trifecta of Rails, iOS, and Android development showcasing how to “Live Like a Local” when visiting the Hotel Monaco DC. I have also implemented Android versions of Circle 8, Analog Analytics, and PEAR Sports (Bluetooth LE heart-rate based real-time coaching). For Star Wars Celebration in Anaheim, CA in April 2015, I implemented an iBeacon-based "Scanner" app that displays "trading cards" for each character scanned. I have been working with iBeacon/AltBeacon technology on iOS, Android, and Linux for Radius Networks for the past year. I discovered Ruby on Rails via the Java Posse podcast when I was doing Java EE development for Symantec circa 2006. I have collaborated on numerous Rails apps since then including Norton Online Backup for Symantec and Hubbub Health for Regence.
    [Show full text]
  • Leveraging Object-Oriented Frameworks
    Leveraging Object-Oriented Frameworks Leveraging Object-Oriented Frameworks Table OF contents Introduction Software Development Approaches Procedural Programming Object-Oriented Programming Framework-Oriented Programming Applying Frameworks - An Overview Applying Application-Level Frameworks Applying System-Level Frameworks Key Advantages of Frameworks Taligent's Approach to Frameworks Taligent Frameworks - An Architectural Perspective Taligent Application-Level Frameworks Taligent System-Level Frameworks Taligent Development Environment Frameworks How Taligent is Changing the Programming Model Domain-Specific Frameworks Summary Next Steps Additional Reading Taligent White Papers INTRODUCTION Over the last two decades, software development has changed significantly. Its evolution has been motivated largely by the quest to help developers produce software 1 of 16 Leveraging Object-Oriented Frameworks faster and to deliver more value to end-users. Despite gains, the industry still faces long development cycles which produce software that usually doesn't address business problems adequately--pointing to the limitations of traditional programming and today's system software environments. These limitations have moved the software industry to embrace object-oriented technology (OOT) because of its potential to significantly increase developer productivity and encourage innovation. Taligent believes that OOT indeed has the potential to dramatically improve the software development process. However, we believe the focus should not only be on OOT, but on how this technology is delivered in order to fully realize the benefits that it has to offer. In our view, object-oriented frameworks--extensible sets of object-oriented classes that are integrated to execute well-defined sets of computing behavior--provide the necessary foundation for fully exploiting the promises of OOT. Which is why Taligent is building a new system software platform and integrated development environment based entirely on OOT and object-oriented frameworks.
    [Show full text]