Fact-checked by Grok 2 weeks ago

Taligent

Taligent was an American software company established in early 1992 as a between Apple Computer and to develop a next-generation, aimed at addressing the growing complexity of in the personal computing era. The venture originated from Apple's internal "" project, initiated in 1988, which envisioned a modular, extensible OS built around object-oriented principles to enable reusable software components across platforms. joined as a third major partner in early 1994, expanding the collaboration's resources and scope. Initially focused on creating —a unified operating system leveraging IBM's based on 3.0—the project sought to support multiple "personalities" compatible with existing systems like , AIX, and , thereby challenging Microsoft's dominance in the market. By 1993, amid delays and competitive pressures from and NeXT's , Taligent pivoted to developing CommonPoint, an object-oriented rather than a full OS, designed to run atop various kernels including AIX, , , , and even Apple's . CommonPoint featured over 100 frameworks and more than 1,000 classes, emphasizing visual development tools like cpConstructor for component-based applications and innovative paradigms such as "" for collaborative, . Despite critical acclaim for its advanced object-oriented technologies, which built on earlier explorations like Apple's MacApp and 's SOM/DSOM, Taligent faced significant challenges including lukewarm market adoption, internal setbacks such as the death of CEO Dick Gurino in October 1995, and subsequent staff reductions. In spring 1996, Taligent became a wholly owned of , and by January 1998, it was fully dissolved and integrated into 's software divisions, where its innovations influenced products like and contributions to internationalization efforts. The venture's legacy lies in advancing concepts that later informed modern cross-platform development, though it ultimately failed to disrupt the prevailing OS landscape dominated by .

Origins

Apple's Pink Project

Apple's Pink project originated in early as an internal initiative to address the growing limitations of the , particularly its lack of protected memory and true multitasking, which hindered advanced software development. The project emerged from a staff meeting where long-term ideas were noted on pink index cards to distinguish them from short-term "blue" tasks for enhancements, reflecting a vision for a fundamentally new operating system. Led initially by Erich Ringewald, with key contributions from Mike Potel, the effort began with a small "Gang of Five" team that quickly expanded to around 25 members, focusing on creating a modern platform compatible with Macintosh heritage but built from a clean slate without constraints. The Pink prototype emphasized an object-oriented design inspired by Smalltalk models, aiming to unify system services through a cohesive architecture. Core features included protected memory to prevent crashes from faulty applications, preemptive multitasking for efficient resource sharing, and a unified system that treated files and applications as interchangeable objects, enabling seamless integration. This approach sought to replace the procedural Macintosh Toolbox with a more modular, extensible foundation, allowing developers to build reusable components for both desktop and future environments. Pink's object model centered on as data containers, behaviors as definable methods for object actions, and as links facilitating interactions between GUI elements and system services, promoting a dynamic, interconnected . For instance, graphical interfaces could be assembled by connecting view objects with behavioral scripts, while system resources were managed through persistent object relationships, foreshadowing capabilities. These concepts drew from earlier Apple frameworks like MacApp but pushed toward a fully object-oriented paradigm for enhanced portability and . Development faced significant challenges due to resource constraints at Apple, including limited and competing priorities like , leading to slow progress and instability in prototypes. Initially targeting a release, the project encountered repeated delays, with Ringewald departing in amid frustrations, and only partial demonstrations achievable by 1990, showcasing basic object interactions but lacking full functionality. These hurdles transformed Pink from a standalone OS effort into a foundational concept later expanded through the partnership.

IBM's Workplace OS

In the early 1990s, IBM launched its project, later known as the Workplace microkernel, as part of its efforts to develop a next-generation operating system foundation, adopting the Mach 3.0 microkernel originally created by . This initiative aimed to create a modular base that could support diverse computing needs, drawing on Mach's proven ability to handle and virtual memory management efficiently. The core architecture of the project emphasized a design, where essential kernel services like thread management and messaging were isolated from higher-level "personality" layers. These personalities, including for compatibility and Presentation Manager for graphical interfaces, allowed the system to run multiple operating system environments simultaneously on the same hardware, promoting portability across platforms from personal devices to high-end servers. This separation enabled developers to swap or extend components without rebuilding the entire kernel, a key enabler for enterprise scalability in distributed and scenarios. By 1991, the project had matured into , incorporating aspirations for object-oriented extensions to facilitate more dynamic and reusable system components. committed roughly $2 billion to the endeavor over several years, integrating key elements from its existing platform to maintain while targeting robust performance in business-critical applications. This focus on enterprise environments positioned as a potential unified for workstations and servers, though performance challenges in the microkernel implementation ultimately limited its broader adoption. Under the AIM Alliance, IBM's Workplace OS efforts merged briefly with Apple's Pink project to underpin Taligent's development.

Formation

AIM Alliance

The , formally known as Apple/IBM/Motorola, was established in 1991 as a between Apple Computer, , and to challenge the growing dominance of and in the personal computing industry. The collaboration sought to foster innovation in and software, creating a new that would integrate advanced technologies and enable broader across systems. The alliance was publicly announced on July 3, 1991, through a between Apple and , with formal agreements signed on , 1991, incorporating . Key elements included joint development of the PowerPC reduced instruction set computing (RISC) processor by and , cross-licensing of operating system technologies such as Apple's to , and collaborative efforts on a new operating system emphasizing object-oriented design for personal computing applications. These agreements formed a five-point program covering networking integration between Apple Macintosh and systems, development, an open software platform, and joint ventures for object-oriented software and multimedia technologies. This focus on object-oriented systems aimed to revolutionize personal by enabling portable, reusable software components that could operate independently of specific hardware. Taligent Inc. emerged as the primary operational entity spun out from the AIM framework to drive these OS development initiatives.

Establishment of Taligent Inc.

Taligent Inc. was established as an independent on March 2, 1992, in , with Apple Computer and each owning a 50% stake. This formation stemmed from the , the strategic partnership announced in 1991 between Apple, , and Motorola to collaborate on advanced technologies. The venture secured substantial funding from Apple and , totaling approximately $250 million over the initial four years of the to support its operations and development efforts. Operations commenced with a core team of over 170 employees, primarily drawn from the existing staff of Apple's project and IBM's initiative, enabling an immediate focus on integrating these object-oriented technologies. Early leadership was headed by Joseph M. Guglielmi, a 30-year veteran and former champion of the platform, who served as CEO and emphasized the merger of the inherited projects to create a unified next-generation . In mid-1992, the company relocated from temporary quarters at Apple's Cupertino headquarters to dedicated facilities nearby, marking a key step in establishing operational independence. By 1993, Taligent had rapidly expanded its workforce to more than 400 employees, reflecting aggressive hiring to bolster engineering and development capabilities.

Development and Products

Shift from Operating System to Frameworks

Taligent's initial vision centered on developing , a next-generation that integrated the object model from Apple's project with the architecture of IBM's . This unified system was designed to support multiple operating system personalities, such as and AIX, while providing a portable environment across hardware platforms, with a targeted release in 1994 for PowerPC processors. By 1994, Taligent abandoned its full operating system ambitions due to significant delays stemming from the inherent complexity of building a comprehensive microkernel-based OS, alongside intensifying competition from Microsoft's and IBM's own , which were capturing more rapidly. The decision reflected a broader recognition that developers and customers prioritized with established platforms over a disruptive new OS, prompting a strategic pivot toward portable, object-oriented frameworks for application development. In 1994, joined the partnership with a 15% stake, aligning its object-oriented initiatives with Taligent's evolving focus on frameworks compatible with . This shift narrowed Taligent's scope from a standalone OS to reusable object-oriented components that ran atop existing operating systems, including AIX, , , and Mac OS, enabling cross-platform application development without requiring a full platform replacement.

CommonPoint and Supporting Technologies

CommonPoint was an object-oriented developed by Taligent and released in as a portable system for building software across multiple platforms, including AIX, , , Mac OS, , and . Implemented primarily in C++, it comprised nearly 100 reusable frameworks addressing key domains such as user interfaces (e.g., Presentation and Workspace frameworks for windows, controls, and views), networking (e.g., Messaging and Remote Object Call Services), and (e.g., Time Media for audio, video, and , alongside / ). This design insulated applications from underlying operating system APIs, enabling developers to create extensible, cross-platform solutions with minimal platform-specific code. At the core of CommonPoint lay the Taligent Application Environment (TalAE), a comprehensive implementation of an object-oriented programming model that provided over 100 frameworks for services including graphics, database access, multimedia, user interfaces, internationalization, networking, and distributed computing. TalAE emphasized portability, running on 32-bit multitasking operating systems such as OS/2, AIX, and HP-UX, with initial deployment targeted for mid-1995 on platforms from Apple, HP, and IBM. Supporting globalization efforts, TalAE incorporated the International Components for Unicode (ICU) library, originally developed at Taligent to handle Unicode-based text processing, collation, formatting, and localization for multilingual applications. For distributed computing, it included an object request broker compliant with the Object Management Group's CORBA specification, allowing seamless remote object interactions in multisystem environments. CommonPoint's architecture was built on the Hierarchical Object Model (HOM), which structured object relationships through , , and to facilitate modular, extensible designs. It supported development on both PowerPC and x86 architectures, with integrated tools such as compilers (e.g., Borland C++ 4.5 for Windows and IBM C Set++ 2.1 for OS/2) and the cpProfessional for source-level analysis and testing. The Taligent Development Environment (TalDE), later rebranded as cpProfessional, further aided framework-based development with features like dynamic object browsers and GUI constructors. A hallmark of CommonPoint's framework-based approach was its promotion of reusability and , where developers extended generic structures rather than building from scratch, reducing duplication and enhancing across projects. For instance, the Text Framework exemplified this by providing robust handling of rich, styled text through classes like TText and TStandardText, which supported strings up to 2 billion characters, dynamic styling (e.g., fonts, colors, bold/italic), multilingual input via virtual keyboards and input methods, and automatic font substitution for missing glyphs. This framework also integrated localization features, such as hierarchies for region-specific , boundary analysis, and number/time formatting, ensuring intuitive behavior like seamless font changes during text configuration switches.

Dissolution

Transition to IBM Subsidiary

In late 1995, acquired the stakes held by and in Taligent Inc., transforming the into a wholly owned subsidiary focused on object-oriented . This restructuring followed years of shifting priorities in the original partnership, with Taligent retaining its base in , while assumed full responsibility for marketing and distribution of its technologies. and secured licensing rights to existing Taligent , allowing continued access without ongoing investment obligations. The transition involved significant operational changes, including the layoff of approximately 190 employees—roughly half of Taligent's workforce of 375—to streamline the under IBM's direction. Renamed the Taligent Object Technology Center, the entity shifted emphasis from standalone operating system ambitions to enterprise-level object frameworks, particularly integrating with emerging standards like . This refocus supported IBM's broader push into cross-platform development tools, including contributions to for Java, which leveraged Taligent's expertise in building reusable components for server-side and web applications. Under IBM ownership, Taligent continued advancing its CommonPoint application framework, releasing subsequent versions that enhanced support for on platforms like AIX and OS/2. These efforts positioned the center as a hub for innovation, emphasizing modular tools over comprehensive operating environments.

Final Closure and Asset Handling

In January 1998, Taligent Inc. was fully dissolved and absorbed into , marking the end of its independent operations as the remaining teams were integrated as IBM employees. This followed an announcement in September 1997 that the company would wind down by year's end, with approximately 100 software engineers reassigned to IBM's Santa Teresa laboratory in , to continue work on Java-based technologies. The dissolution stemmed from Taligent's inability to gain significant market traction for its CommonPoint framework, overshadowed by the rapid emergence of as a dominant cross-platform platform in the mid-1990s, alongside escalating expenses that exceeded $100 million in investments from its partners by 1995. As part of the asset handling, CommonPoint's components were unbundled: the (ICU) library, originally developed at Taligent, was open-sourced by and has since been widely adopted in software for and support, powering applications across industries. Patents and other were transferred to for integration into its broader portfolio. Apple and retained licensing rights to Taligent's technologies for internal use, allowing them to leverage elements like object-oriented frameworks in their own products without further joint development. Notably, no full operating system from Taligent was ever commercially shipped, with efforts shifting from an ambitious OS vision to component libraries that influenced subsequent industry standards.

Reception and Legacy

Contemporary Reception

The formation of Taligent in March as a joint venture between Apple and generated substantial early hype in the trade press, positioning it as a revolutionary capable of unifying disparate platforms and challenging Microsoft's dominance in business computing. Industry leaders described the project as a potential industry reshaper, with Taligent's CEO M. Guglielmi stating, “We think the operating system we’re developing is one that can recast the shape of the industry,” emphasizing its use of modular to enable faster and hardware adaptability. Praise focused on its promise to lower barriers for developers and foster open standards, drawing widespread attention as a collaborative effort to address the growing complexity of personal computing environments. By 1994, persistent delays in delivering a full operating system led to growing criticisms, with the project increasingly viewed as amid broader industry concerns over premature announcements without viable products. Reviews of CommonPoint, Taligent's flagship released in 1995, further underscored these issues, noting its technological sophistication but extreme complexity, including nearly 1,940 classes that imposed a steep even for experienced C++ developers, often requiring at least three months to achieve productivity. The 1995 launches of and intensified competition, overshadowing Taligent's efforts as developers gravitated toward Java's simpler cross-platform model and Windows 95's widespread hardware compatibility, which captured significant and developer mindshare. Analyst reports in 1996 highlighted the venture's challenges, estimating a total investment exceeding $2 billion across the related initiatives—with Taligent as a core component—yet yielding minimal due to shifting priorities and failure to achieve broad ecosystem support.

Long-term Influence

Taligent's most enduring technical legacy lies in its contributions to software and support. The (ICU) library, originally developed at Taligent under the leadership of Mark Davis, became foundational for 's capabilities. classes for created at Taligent were licensed and incorporated into the (JDK) 1.1, providing core support for handling diverse languages, calendars, and text formats in applications. This work extended to broader standards, with Taligent's efforts influencing the design of text processing that persists in modern software ecosystems. Post-Taligent, Davis continued advancing technology as co-founder and president of the , shaping standards for algorithms and mechanisms used globally today. Taligent's object-oriented frameworks also left a mark on subsequent development practices. Its C++ programming guidelines, which emphasized robust and , influenced in various environments. In terms of industry impact, Taligent's technologies were integrated into IBM's tools following its acquisition. Key components, including object-oriented libraries, were incorporated into IBM C++, particularly through the Open Class framework, which abstracted 2 interfaces for cross-platform development. Additionally, Taligent's patents on object-oriented distributed systems, such as methods for managing software components across networks (US5761499A) and object-oriented interfaces for portability (US6606742), have been referenced in architectures for scalable, distributed applications. Beyond specific technologies, Taligent serves as a in computing history, exemplifying the risks of ambitious operating system projects during the amid rapid market shifts toward commoditized platforms like Windows. Analyses of era-defining failures highlight how Taligent's and feature bloat, alongside competition from established ecosystems, contributed to its downfall, informing later strategies in OS development that prioritized incremental over wholesale reinvention. This legacy underscores the challenges of joint ventures in fostering under shifting industry dynamics.

Publications and Patents

Key Publications

Taligent produced a series of whitepapers, books, and technical reports between 1993 and 1997 that documented its object-oriented technologies, with over 10 major documents released during this period to support developer adoption. These publications consistently emphasized the portability and reusability of across platforms, leveraging frameworks to enable efficient application in heterogeneous environments. A prominent whitepaper, "The Power of Frameworks" (1995), provided an in-depth overview of the CommonPoint architecture, illustrating how object-oriented frameworks facilitated reusable components for building cross-platform applications on Windows and OS/2. It highlighted the role of frameworks in abstracting complex behaviors, allowing developers to extend and customize systems while maintaining portability through standardized interfaces. Similarly, "Taligent's Object Technology" explored the Hierarchical Object Model (HOM), detailing how it supported layered abstractions for persistent and distributed objects, promoting reusability in design. In book form, "Inside Taligent Technology" (1995), authored by Sean Cotter with Mike Potel and published by , offered comprehensive guidance on application development using Taligent's frameworks. The volume covered topics from object modeling to , underscoring reusability through and polymorphism in the CommonPoint environment. Accompanying this were developer manuals for the CommonPoint (SDK), such as "Taligent's Guide to Designing Programs: Well-Mannered Object-Oriented Design in C++" (1994), which provided practical conventions for creating portable, maintainable code. Additional technical reports focused on specific components, including those on the (ICU), originally developed at Taligent for multilingual text handling and localization to enhance application portability. Reports on the Taligent Application Environment (TalAE) described its implementation of the model, distributed at conferences like OOPSLA '94 to demonstrate framework-based development. These materials collectively served as foundational resources for developers, bridging theoretical object models with practical reusability strategies.

Patents

Taligent filed numerous patents during its active years, primarily focusing on innovations in programming environments, system architectures, and supporting technologies. Between 1993 and 1996, the company experienced a peak in patent filings, reflecting its intensive research into extensible software frameworks and distributed systems. By 1997, Taligent had secured dozens of U.S. patents, with many more pending and later assigned to following its acquisition as a . These patents covered a broad spectrum of OO innovations, including user interfaces, internationalization, and integrations with designs, totaling more than 50 directly or indirectly assigned to Taligent or its parent entity. Key patents highlighted Taligent's advancements in -based application development. For instance, U.S. Patent 5,544,302 (issued August 6, 1996), titled "Object-oriented for creating and using container objects with built-in properties," described a for building applications using reusable container that organize data with built-in editing and navigation behaviors, enabling developers to extend base classes for custom functionality. Another significant example is U.S. Patent 5,659,751 (issued August 19, 1997), titled "Apparatus and method for dynamic linking of computer software components," which outlined an apparatus and method for dynamic linking of software components at , allowing modular assembly of libraries and objects without recompilation, thus supporting flexible application environments. In the realm of distributed object communication, Taligent's work emphasized networked OO systems. U.S. Patent 5,553,282 (issued September 3, 1996), titled "Software project history database and method of operation," provided mechanisms for managing and configuring program components across client-server architectures, facilitating seamless object interactions in heterogeneous networks. Focus areas also included OO user interfaces, such as U.S. Patent 5,615,326 (issued March 25, 1997), titled "Object-oriented viewing framework having view grouping," which introduced a hierarchical view model for grouping and manipulating windows as logical units with spatial constraints. Internationalization methods were addressed more directly in U.S. Patent 5,551,055 (issued August 27, 1996), titled "System for providing locale dependent user interface for presenting control graphic which has different contents or same contents displayed in a predetermined order," enabling applications to dynamically adjust for languages, graphics, and cultural conventions. Microkernel integrations appeared in patents like U.S. Patent 5,566,346 (issued October 15, 1996), titled "System for constructing hardware device interface software systems independent of operating systems including capability of installing and removing interrupt handlers," which abstracted interrupt handling into OO servicers compatible with lightweight kernel designs for efficient peripheral management. Many of Taligent's patents have since expired, but their legacy endures through licensing and influence on industry standards. Technologies from these patents, particularly in text handling and , were licensed to and incorporated into (JDK) 1.1, enhancing Java's global support features. Similarly, OO distributed computing concepts contributed to the evolution of standards like CORBA, with Taligent's framework ideas informing portable object models in enterprise environments.

References

  1. [1]
    Taligent Company History
    Taligent was founded in early 1992 as part of a historic agreement between IBM and Apple Computer to develop the next generation microcomputer operating system.
  2. [2]
    The Secrets of Pink, Taligent and Copland - RoughlyDrafted
    Nov 25, 2006 · Taligent was initially focused on delivering Apple's Pink. IBM contributed its WorkPlace OS, a new Mach 3.0 microkernel which eventually aspired ...
  3. [3]
    Pink: Apple's First Stab at a Modern Operating System - Low End Mac
    Apr 27, 2014 · Ringewald left the project in disgust, and it was turned over to an Apple VP, Ed Birss, and renamed the Object Oriented Systems Group.Missing: Smalltalk | Show results with:Smalltalk
  4. [4]
    A brief history of Taligent
    Taligent was founded in early 1992, Apple and IBM had already committed substantial resources to the exploration of object-oriented programming (OOP).
  5. [5]
    [PDF] Oral History of Gary Davidian, part 2 of 2
    Mar 14, 2019 · was Phil Goldman and Erich Ringewald who were on the Jaguar Project and asked you--. Davidian: Yeah, I think they were working on the Jaguar ...
  6. [6]
    [PDF] Chapter 10 Apple Computer in the 1980's
    In March 1988, a software project called Pink was started to develop a next-generation operating system. ... Erich Ringewald was the initial project leader.
  7. [7]
    [PDF] FRAMEWORKS - Bitsavers.org
    1994) It has strong "wired-in" connections among its objects. These ... Provide standard tests for common object behaviors, including hashing and ...
  8. [8]
    Workplace Microkernel and OS: A Case Study - OSnews
    Nov 25, 2013 · IBM's Microkernel, named Workplace OS microkernel, was the core components of Workplace OS, a portable successor of OS/2. The basic premise ...Missing: history | Show results with:history
  9. [9]
    Experience with the development of a microkernel-based, multiserver operating system
    **Summary of IBM's Workplace OS:**
  10. [10]
    Workplace OS History: IBM's $2 Billion Microkernel of Failure - Tedium
    Feb 28, 2019 · How IBM bet big on the microkernel being the next big thing in operating systems back in the '90s—and spent billions with little to show for it.Missing: 3.0 | Show results with:3.0
  11. [11]
    New Alliance : IBM and Apple Officially Unveil Accord
    Oct 3, 1991 · International Business Machines and Apple Computer on Wednesday signed their wide-ranging cooperation agreement, a landmark accord that ...<|control11|><|separator|>
  12. [12]
    IBM, Apple detail five-point alliance - UPI Archives
    The five points of the program call for: --Networking between IBM's systems and the Apple Macintosh. This will enable Apple to integrate its ...Missing: parts | Show results with:parts
  13. [13]
    Executives Appointed To I.B.M.-Apple Venture - The New York Times
    Feb 25, 1992 · Taligent's goal is to produce a next generation of operating system software for personal computers based on object-oriented technology. Such ...Missing: stake | Show results with:stake
  14. [14]
    [PDF] Taligent: What Went Wrong? - Hot Chips
    What went wrong? ▫ In 1992, a “deal” was struck between John. Sculley and Jim Cannavino, 50/50 JV Apple ...
  15. [15]
    SOFTWARE ENTERS BRAVE NEW WORLD Apple, IBM hope ...
    Taligent is an independent joint venture of Apple Computer Inc. and the International Business Machines Corp., with a mandate to develop ...
  16. [16]
    The Executive Computer; Apple-I.B.M. Venture, With New Leaders ...
    Mar 8, 1992 · Taligent Inc. officially opened for business last week with 170 experienced employees, two new leaders, the most impressive venture backing ...
  17. [17]
    SP 94: The Architecture of the Taligent System
    The Architecture of the Taligent System. A web of frameworks leads to People, Places, and Things. Mike Potel and Jack Grimes. The authors are software ...
  18. [18]
    MICROSOFT HURRIES OBJECT-ORIENTED CAIRO FORWARD AS ...
    Oct 11, 1993 · The twin worries are identified as what is now clearly a very slow take-up of Windows NT, and the looming threat from Taligent Inc, which is ...
  19. [19]
    [PDF] Most Significant Bits: 1/24/94 - CECS
    Jan 24, 1994 · Hewlett-Packard Joins Taligent. HP has decided to take a side in the great object war, agreeing to support Taligent's operating system and.<|separator|>
  20. [20]
    I.B.M. Is Set to Acquire a New Subsidiary - The New York Times
    Dec 20, 1995 · Under the new arrangement, Taligent will operate as a development center for I.B.M., which will assume responsibility for marketing and ...Missing: control | Show results with:control
  21. [21]
    Inside Taligent Technology - The Taligent product suite
    Taligent has created a new kind of system software: the CommonPoint(tm) application system. Portable across multiple host operating systems.
  22. [22]
    [PDF] A Beginner's Guide to Developing with the Taligent Application ...
    Sep 6, 1995 · This paper was written to help you plan your learning path. Keywords. Application development, application frameworks, learning of frameworks, ...
  23. [23]
    ICU - International Components for Unicode
    ICU is a mature, widely used set of C/C++ and Java libraries providing Unicode and Globalization support for software applications.C++ · Why Use ICU4J? · Downloading ICU · Source Code Access
  24. [24]
    [PDF] Text handling and localization in Taligent's CommonPoint ...
    Mountain View, CA (1993). 5. Taligent, Inc., The Power of Frameworks, Addison-Wesley. Publishing Co., Reading, MA (1995). 6. S. Cotter and M. Potel, Inside ...
  25. [25]
    TECHNOLOGY - Dec. 20, 1995 - Los Angeles Times
    Dec 20, 1995 · Taligent was formed in 1992 to develop a new operating system based on “object-oriented” design, in which parts of programs stand on their own ...
  26. [26]
    IBM FINALLY ABSORBS TALIGENT, FIRING 190: APPLE AND ...
    Jan 4, 1996 · Apple and Hewlett-Packard get rights to the technology developed so far and possible access to future IBM-created Taligent enhancements – if ...Missing: March 1992
  27. [27]
    dsn5h.asc - IBM
    ... CommonPoint object-oriented application development environment from Taligent, Inc. ... Oracle and Sybase. IBM also plans parallel access capabilities for DB2 for ...
  28. [28]
    Taligent - Apple Wiki | Fandom
    Taligent was a joint venture formed by Apple Computer and IBM in March 1992 to develop a next-generation operating system.
  29. [29]
    IBM, Apple Will Close Door on Kaleida Labs : Software
    Nov 18, 1995 · IBM, Apple Will Close Door on Kaleida Labs : Software: A second joint venture, Taligent, will soon close, sources predict, in another sign of ...Missing: 1997 dissolution
  30. [30]
    [PDF] ICU User Guide - IBM
    Aug 31, 2006 · The team has received significant input from the open source community worldwide. Java™ classes developed at Taligent were incorporated into ...
  31. [31]
    [PDF] Public Hearing on Use of the Patent System to Protect Software ...
    Jan 27, 1994 · unclear, vaporware is rampant, early disclosure is common, ... Taligent, as an example, is a new, founded in 1992, small, starting ...
  32. [32]
    Java Cookbook: Creating Global Applications
    The bulk of the international support in Java 1.1 was licensed from Taligent, with data supplied by IBM's Native Language Technical Center (NLTC) in Toronto.
  33. [33]
    Conference Biography - Macchiato
    Dr. Mark Davis co-founded the Unicode project and has been the president of the Unicode Consortium since its incorporation in 1991.
  34. [34]
    UTC/1994-032 - Unicode
    This paper was prepared by Mark Davis (Taligent), who proposed a small standardized set of glyphs, each representing a particular script block, to be used ...
  35. [35]
    [PDF] Supporting Students in C++ Programming Courses with Automatic ...
    Some industrial guidelines for C++ programming have been published, such as by Taligent Inc. ... Symbian OS C++ coding standards. Retrieved April 7, 2004, from.
  36. [36]
    Apple's Copland Project - Low End Mac
    Nov 8, 2005 · In the early 90s, Apple teamed up with IBM to create Star Trek, a version of System 7 for the IBM PC. That project eventually became Taligent, ...
  37. [37]
    [PDF] ÉÂÔ - IBM
    The Framework, which is the first injection of Taligent Technology into IBM Open Class, provides an abstraction from OLE 2 into higher-level classes. The ...
  38. [38]
    Welcome to the April, 1996 Issue of the C/370 Newsletter - IBM
    The Framework, which is the first injection of Taligent Technology into IBM Open Class, provides an abstraction from OLE 2 into higher level classes as well ...
  39. [39]
    Method for managing globally distributed software components
    A method and apparatus are disclosed for managing software components in a network of computers such as a local area network or the Internet.<|separator|>
  40. [40]
    Patents Assigned to Taligent, Inc. - Justia Patents Search
    Patents Assigned to Taligent, Inc. Object-oriented interface for portability to diverse operating systems or hardware platforms. Patent number: 6606742.Missing: enterprise | Show results with:enterprise
  41. [41]
    [PDF] Leveraging Object-Oriented Frameworks
    frameworks and Taligent's design approach, how you can benefit from frameworks, ... Lessons Learned from Early Adopters of Object Technology, Taligent, Inc., 1993.
  42. [42]
    Inside Taligent Technology: | Guide books | ACM Digital Library
    Mar 1, 1995 · Inside Taligent TechnologyMarch 1995 · Addison-Wesley Longman Publishing Co., Inc. · 75 Arlington Street, Suite 300 Boston, MA · United States.
  43. [43]
    Inside Taligent Technology
    Mike Potel, Vice President, Technology Development Taligent, Inc. The ... This Web page provides excerpts from the book along with information on how to order ...
  44. [44]
    [PDF] TALIGENT'S GUID.E TO DESIGNING PROGRAMS - Bitsavers.org
    Taligent s Guide to Designing Programs is a collection of guidelines and conventions that Taligent® engineers follow as they design and build the Taligen t ...Missing: TalAE | Show results with:TalAE
  45. [45]
    Apparatus and method for dynamic linking of computer software ...
    An apparatus and method for the dynamic (execution time) linking of object oriented software components is disclosed. The present invention comprises a ...