Taligent

Taligent (a portmanteau of "talent" and "intelligent")[3][4] was an American software company. Based on the Pink object-oriented operating system conceived by Apple in 1988, Taligent Inc. was incorporated as an Apple/IBM partnership in 1992, and was dissolved into IBM in 1998.

Taligent
IndustrySoftware development
FateBought by IBM
FoundedMarch 2, 1992 (1992-03-02) in Cupertino, California, United States
FounderApple and IBM
DefunctJanuary 1998 (1998-01)
Headquarters
Cupertino, California
,
United States
Number of locations
1
Key people
Erich Ringewald, Mike Potel, Mark Davis
ProductsCommonPoint, Places for Project Teams
Number of employees
400[1]:xiv (1995)
ParentApple Inc., IBM, Hewlett-Packard
Websitetaligent.com at the Wayback Machine (archived March 28, 1997)
Footnotes / references
[2][1]

In 1988, after launching System 6, Apple initiated the exploratory project named Pink to design the next generation of Mac OS. Pink soon diverged into an entirely new system, but development at Apple was beset by problems. In 1992, the new AIM alliance spawned an Apple/IBM partnership corporation named Taligent Inc., with the purpose of bringing Pink to market. IBM positioned it as a layer on top of their own multiplatform operating system, Workplace OS, while Apple continued with its original plans to make an entirely new OS based on it. In 1994, Hewlett-Packard joined the partnership with a 15% stake.

After years of goal-shifting delays, in 1995 Apple sold its share of the project back to IBM and Taligent as an operating system was canceled. HP also withdrew from the project. IBM continued to work with the underlying object-oriented application framework, which was released as CommonPoint in 1995 for AIX and in beta for OS/2. The formerly joint-company was officially absorbed into IBM in January 1998. CommonPoint was merged into IBMs ongoing Java efforts, porting them into the Java Development Kit 1.1 (especially internationalization) and converting Taligent compiler technology components into VisualAge C++.

Along with Workplace OS, Copland, and Cairo, Taligent is cited as a death march project of the 1990s, suffering from development hell as a result of feature creep and the second-system effect.

History

Pink team

In 1988, Apple released System 6, a major release of the flagship Macintosh operating system. The system's architectural limitations, set forth by its original 1984 release, now required increasingly ingenious solutions for incremental gains such as cooperative multitasking, and System 6 had a lackluster reception. A group of accomplished but restless senior engineers nicknamed the Gang of Five – Erich Ringewald, David Goldsmith, Bayles Holt, Gene Pope, and Gerard Schutten – gave an ultimatum that they should either be allowed to break from their disliked management and take the entrepreneurial and engineering risks needed to develop the next generation of the Macintosh operating system, or else leave the company.[5]:96[6]

In March 1988,[lower-alpha 1] the Gang, their management, and software manager and future Taligent CTO Mike Potel, met at the Sonoma Mission Inn and Spa. To roadmap the future of the operating system and thus of the organizational chart, ideas were written on colored index cards and pinned to a wall. Ideas that were incremental updates to the existing system were written on blue colored cards, those that were more technologically advanced or long-term were written on pink cards, and yet more radical ideas were on red cards because they "would be pinker than Pink".[5]:96–97[1]:6[6] The Blue group would receive the Gang's former management duo, along with incremental improvements in speed, and size of random-access memory (RAM) and hard disk drive (HDD). Pink would receive the Gang with Erich Ringewald as technical lead, plus pre-emptive multitasking and a componentized application design. Red would receive speech recognition and voice commands.[5]:96–97

Erich Ringewald led the Gang of Five as the new Pink group, located one floor below the Apple software headquarters in the De Anza 3 building, to begin a feasibility study with a goal of product launch in two years. Remembering the small but powerful original Macintosh group, he maintained secrecy and avoided the micromanagement of neighboring senior executives, by relocating the team off the main Apple campus. They used the nondescript Bubb Road warehouse which was already occupied by the secret Newton project.[5]:97–98[6] Pink briefly garnered an additional code name, "Defiant".[7]:35

Pink system

The Pink team was faced with the two possible architectural directions of either using legacy System 6 code or starting from scratch. Having just delivered the System 6 overhaul MultiFinder, Ringewald was aware that Pink's ambitious features could not be delivered in a two-year timeframe unless the team incorporated legacy compatibility code. He warned that "We're going to have enough trouble just reimplementing the Mac." This mandate was soon challenged; David Goldsmith resigned from the team after making a counter-ultimatum for a complete redesign, while other staff escalated their complaints to upper management. Months later, a senior executive finally overrode Ringewald, thus redeveloping Pink from scratch as a new and unique system with no System 6 legacy.[5]:97–98[6]

The Pink team numbered eleven when the six-person kernel team within Apple's Advanced Technology Group (ATG) was merged into Pink to begin designing its new microkernel[5]:98[6] named Opus.[8][9][10] Going well beyond the features of the original index card plans, Pink's design goals were now complete object-orientation, memory protection, preemptive multitasking, internationalization, and a new graphics library. Many ideas from the red cards would later be absorbed into the project as well. After its first two months, Pink had a staff of about 25.[5]:97–98

By October 1988, the Gang of Five had become only one Bayles Holt, because Gene Pope, Gerard Schutten, and Erich Ringewald then exited the sprawling Pink. The former leader held "grave doubts" over the feasibility of this "living, breathing, money-consuming thing" which was "out of control". Meanwhile, the remaining group and all of Apple were enamored and doubtless of Pink's world-changing vision, trying to join its staff of more than 100 by April 1989. It was a flourishing project that drained personnel from various other departments. All groups outside of Blue became defensively secretive in a company-wide culture of empire-building. Pink's secretive and turf warring culture didn't share source code or product demonstrations, even with the next generation Jaguar workstation design group, until so ordered by CEO John Sculley, and only then under extreme security and monitoring.[5]:99–100[6] Throughout Apple, the project and the system were considered successful, but from April 1989 and on into the 1990s, the running joke had always been and would always be, "When is Pink going to ship? Two years."[5]:99–100[6]

In 1990, Pink became the Object Based Systems group with Senior Vice President Ed Birss and a staff of 150, including marketing and secretaries.[5]:99–100 Meanwhile, the hundreds of personnel in the Blue design group[6] were continuing work with the existing code base, which required them to refuse many new features, earning them the nickname "Blue Meanies". This group was making significant progress and would release their efforts in 1991 as System 7. RAM chips and hard drives were expensive and most personal computers were resource-constrained, so System 7 already had problems running on existing Macintosh systems. Pink would, therefore, have little room to include backward compatibility for System 7 applications atop itself. This physical and economical constraint is a crucial aspect of the second-system effect.

By late 1989, Pink was a functional prototype of a desktop operating system on Macintosh hardware, featuring advanced graphics and dynamic internationalized text. Engineer Dave Burnard, Ph.D., said it was "a real OS that could demonstrate the core technology" much deeper than System 6 could do.[5]:99–100 In the early 1990s, Pink's graphical user interface (GUI) was based on a faux 3D motif of isometric icons, beveled edges, non-rectangular windows, and drop shadows. One designer said "The large UI team included interaction and visual designers, and usability specialists."[11] That essential visual design language would be an influence for several years into Copland, Mac OS 8, and CommonPoint.[12] Magazines[13] throughout the early 1990s showed various mock-ups of what Pink would look like. The People, Places, and Things metaphor was widely noted in articles, it would provide the user with tools to move documents around between people and things (like fax machines) as easily as they could print. The system had a component-based document model that is similar to what would become OpenDoc.

In mid-1991, Apple CEO John Sculley bragged that Apple had written 1.5 million lines of code for Pink.[13] An IBM engineer described the first impression of this sophisticated prototype in 1991:

[Pink] had proven that an operating system ... could, in fact, be built on a microkernel. ... This microkernel then exported C++ interfaces, providing an object-oriented 'wrapper'. ... All the code that traditionally had resided in a kernel was implemented in system frameworks. This was not a monolithic kernel, but a collection of object-oriented servers performing specific kernel-type tasks. There were frameworks for file systems, for device drivers, for databases, for networking, and so on. But they all resided outside the kernel. And in the [Pink] world, these things were objects.[14]:4

AIM alliance
In 1992, the earth shook: IBM and Apple clasped hands and pronounced themselves allies. From this union sprang Taligent ... developing nothing less than a universal operating system.

MacWorld[15]

Main articles: AIM alliance, Workplace OS, and Kaleida Labs

On October 2, 1991, the historic AIM alliance was formed and announced by Apple, IBM, and Motorola. It was conceived to cross-pollinate Apple's personal products and IBM's enterprise products, to better confront Microsoft's monopoly, and to design a new unified platform for the computing industry meant to rival the dominance of Microsoft. This alliance spun off two partner corporations: Kaleida Labs to develop multimedia software, and Taligent Inc. to bring the Pink operating system to market sometime in the mid-90s.[3][7]:69[16][17]

Pink was a massive draw for this alliance, where Apple had been initially approached by two different parts of IBM. One IBM group sought customers for its new POWER CPU hardware, therefore discovering Pink and a desire to port it to the new chipset.[7]:69[6] The other IBM group sought third party interest in its Grand Unifying Theory of Systems (GUTS) as the solution to the deeply endemic crisis that is software development,[1]:9 which would soon result in Workplace OS.[14]:3–4 Pink was demonstrated to IBM on April 12, 1991. The operating system and the architecture profoundly impressed IBM and its GUTS outline was immediately impacted.[14]:4[7]:69 By 1993, IBM's ambitious global roadmap would include the unification of the diverse world of computing by converting Pink to become one of many personalities of Workplace OS. There would be no more need to write new major applications. They could instead become smaller additions to Pink's generalized frameworks.[18]:14–15

Even before the signing of the alliance contract, the very existence of Pink was identified as a potential second-system threat if its seemingly revolutionary aura could prompt customers to delay their adoption of OS/2.[3]

Taligent Inc.

On March 2, 1992, Taligent Inc. was launched as the first product of the AIM alliance.[8][16][17] Moving from a temporary lease at Apple headquarters[16][19] to an office down the street in Cupertino, the company launched with 170 employees,[1]:xiv most of whom had been re-hired directly from Apple plus CEO Joe Guglielmi.[20] At age 50, he was a 30 year marketing veteran of IBM and former leader of the OS/2 platform up to its soon-launched version 2.0.[21] The company's mission was to bring Pink to market.[1]:xiii

Culture and purpose

Dismissing industry skepticism, he said Taligent would form its own corporate culture, independent of the established cultures and potential failures of its two founding investors and future customers, Apple and IBM. The two were recent allies carrying five other joint initiatives, and a deep rivalry of more than a decade.[21] Dr. Dobb's Journal reflected, "It was fairly surreal for the Apple and IBM employees who went to Taligent and found themselves working for bosses still loyal to the opposition. Not a typical Silicon Valley career move, maybe, but perhaps a portent of other weird twists to come. Ignoring the politics as much as possible, the Taligent programmers buckled down and wrote a lotta lines of code."[22] Commenting on the corporate culture shock of combining free-spirited Apple and formal IBM personnel, Fortune compared the company's cultural engineering challenge as possibly exceeding its software engineering challenge. The openminded but sensible CEO reigned it in, saying, "I'm tired of [Apple] folklore ... I want some data."[20] Comparing the eager startup Taligent to its billion dollar investors, a leader at Kaleida said "The culture of IBM and Apple is largely about getting more benefits, perks, larger offices, fancier computers, and more employees".[5]:289

Apple and IBM did share a progressive culture looking to the future as object orientation. This is seen in their deep software portfolios since the early 1980s. IBM had delivered objects on System/38 and AS/400, and System Object Model (SOM) and Distributed SOM were already integral to OS/2 and AIX. Apple had already delivered Lisa, prototyped the fully object-oriented Pink operating system, and delivered object-oriented frameworks using MacApp. Both companies had worked with Smalltalk.[1]:6,119

Within one month of its founding, there was immediate industry-wide confusion about Taligent's purpose and scope. An industry analyst said "IBM and Apple blew it ... they should have announced everything [about Taligent] or nothing." Especially regarding Taligent's potential relationship to the Macintosh, Apple reiterated that its existing flagship legacy would continue indefinitely with System 7 and Macintosh hardware. COO Michael Spindler said "The Mac is not dead" and others said that they had never claimed that Pink would supersede the Macintosh. Charles Oppenheimer, Director of Marketing for Macintosh system software, said "We can't say for sure how [the two] will fit together."[23] The industry was further confused as to the very existence of any Taligent software, not realizing that it was already beyond the concept stage and in fact consisted of volumes of Pink-based software in development by Apple for years.[6] One year later in February 1993, Wired magazine would assert its suspicion that Apple and IBM's core messengers are maintaining "the big lie"—that Taligent's technology is merely a concept, has no existing software, and is actually years away from production—in order to protect their established multi-billion-dollar core legacy of Macintosh and OS/2 products from a potentially superior replacement and to divert the second system effect.[13]

Upon its launch, CEO Joe Guglielmi soon organized the company into three divisions: a native system group for its self-hosted Pink OS, a development tools group, and a complementary products group for application frameworks to be ported to other OSes.

Taligent spent much of its first two years developing its operating system and simultaneously trying to find a market for it. They started a large project surveying potential customers, only to find little interest in a new OS. It is a point of controversy whether the lack of interest was real or the survey fell prey to question-framing problems and political issues with investors. If asked the question "Do you want a new OS?", there were few who would say yes. The survey did, however, show there was sufficient support for the benefits TalOS would bring.

Technology

The Pink operating system is now named Taligent Object Services (TOS or TalOS) whether hosted natively on its microkernel or non-natively on a third party OS, but the nickname will always remain industry lore,[1] such as with the developer phone number 408-TO-B-PINK.[24] The entire graphics subsystem is 3D, including the 2D portions which are actually 3D constructs.[25][9] It is based extensively on object-oriented frameworks from the kernel upward, including device drivers, the Taligent IO system, and ensembles.[26] By 1993, IBM discussed decoupling most of TalOS away from its native Opus microkernel, and retargeting most of TalOS onto the IBM Microkernel which was already used as the base for IBM's tandem project, Workplace OS.[1]:119[9][10][18]:14–15[27]

By April 1993, the company had grown to about 260 employees, mostly from Apple or "some other loose Silicon Valley culture".[20]

On June 23, 1993, Apple preannounced MacApp's direct successor, the new object-oriented crossplatform SDK codenamed Bedrock. Positioned as "the most direct path for migration" from System 7 to Pink, it was intended to provide source code compatibility between System 7, Windows 3.1, Windows NT, OS/2, and Pink.[28] Bedrock would be abruptly discontinued 18 months later with no successor, and leaving Apple with no connection between System 7 and Pink.[29]

[Taligent engineer Tom Chavez's] theory is that for the past few years [the industry's] hardware has become very fast and that it's traditional OSes that have been slowing [users] down.

Taligent CTO, Mike Potel[25]

The platform soon consisted of Taligent Object Services (TOS or TalOS), Taligent Application Environment (TAE or TalAE), and the Taligent Development System (TDS or TalDS).[25][8][1]:22 The initial plan is to deploy TalAE in early 1994 to help seed the market with a base of applications for TalOS, which is intended to be launched in 1995, with the whole platform going mainstream in two to five years—surely expecting a modern OS from Apple by 1994 or 1995.[30] Influenced by the results of the survey effort, Taligent deemphasized its yet-unreleased natively hosted TalOS, to focus on its TalAE application framework programming environment that would run on any modern operating system. Developed mainly upon AIX, the plan was to port to HP-UX, OS/2, Windows NT, and whatever Apple might someday produce as a System 7 successor. Those vendors are intended to port and bundle TalAE directly with their operating systems, and Taligent will port for those who don't.[25][8] CEO Joe Guglielmi acknowledged the unavoidable risk of creating its own second-system effect, if the TalAE enhancements could make third party operating systems into competitors of native TalOS. The initial development environment was an IBM RS/6000 running AIX,[8] with TalOS running as a native operating system on the 68k Macintosh.[25]

In March 1994, the first Taligent technology demonstration was at SFA as a "very fast" and crash-tolerant five-threaded 3D graphics application on a Macintosh IIci.[25] In November 1994, the debut of third-party TalAE applications was on an RS/6000 running AIX to demonstrate prototypes made by seven vendors at Comdex.[31][8]

HP, CommonPoint beta
We used to joke that the [CommonPoint] frameworks were so powerful that you could write any program in three lines of code, but it would take you 6 months to figure out what those three lines were.

Stephen Kurtzman, project lead on the IBM Microkernel[9]

[NeXT is] ahead today, but the race is far from over. ... [In 1996,] Cairo will be very close behind, and Taligent will be very far behind.

Steve Jobs, 1994[32]:13

When is Pink going to ship? Two years.

—a running joke

In January 1994, fellow object technology pioneer Hewlett-Packard joined Apple and IBM as the third co-owner of Taligent at 15% holding. HP held deeply vested experience in object technology since the 1980s with the NewWave desktop environment, the Softbench IDE, Distributed Smalltalk, and cofounding the Object Management Group.[1]:6 Taligent's object-oriented portfolio was broadened with HP's Distributed Object Management Facility and compilers, and HP's intention to integrate Taligent natively into HP-UX.[32] HP had already partnered with Taligent's well-established competitor NeXT to integrate OPENSTEP into HP-UX, and Taligent had pursued partnerships with both Sun and HP for several months, all serving to improve HP's competitive bargaining in its offer to Taligent. A Taligent engineer reportedly said, "It wasn't that HP was driven by OpenStep to go to Taligent, but that OpenStep allowed them to make a much better deal."[32]:16 NeXTWORLD described it as "[HP covering] all bets in the race for the object market", and Sun CEO Scott McNealy derided the partnership as HP being Taligent's "trophy spouse".[32]:13 Dobb's described the increased abstraction in corporate culture, "Now you could be [a former] Apple programmer working for [a former] IBM boss who reported [externally] to HP. Or some combination thereof. Twisteder and twisteder."[22]

Also in 1994, TalAE was renamed to CommonPoint, TalDE was renamed to cpProfessional development environment, and Taligent User Interface Builder was renamed to cpConstructor user interface builder.[1]:22 CommonPoint was being beta tested at 100 sites, with an initial target market of internal corporate developers. TalOS was still scheduled to ship in 1996. Apple considered MacApp's lifespan to have "run its course" as the primary Macintosh SDK,[8] while Taligent considers MacApp to be prerequisite experience for its own platform.[33] Meanwhile, Apple and CILabs had begun an internal mandate for all new development to be based on the complementary and already published OpenDoc. CILabs was committed to publishing its source code, while Taligent was committed against publishing its own.[8]

Taligent’s role in the world is to create an environment in which all the applications we buy individually are built directly into the operating system. Because the apps are programmable, you can put together your own custom-made suites. Taligent could mean the end of all applications as we know them. ... The suites are here to battle Taligent.

— John C. Dvorak[34]

Taligent was now considered to be a venerable competitor in the desktop operating system and enterprise object markets even with no product release, and being late. John C. Dvorak described Taligent as a threat in the desktop market of integrated application software suites, particularly to the "spooked" Microsoft which responded with many vaporware product announcements (such as Chicago, Cairo, Daytona, and Snowball) to distract the market's attention from Taligent.[34] ComputerWorld described the enterprise computing market as shifting away from monolithic and procedural application models and even application suites, toward object-oriented component-based application frameworks – all in Taligent's favor.[35] Its theoretical newness was often compared to NeXT's older but mature and commercially established platform. Sun Microsystems held exploratory meetings with Taligent before deciding upon building out its object application framework OpenStep in partnership with NeXT as a "preemptive move against Taligent and Cairo".[32] Having given up on seeing Pink go to market, Apple announced Copland in March 1994 in competition with the upcoming Windows 95.[7]:225

In June 1994, Taligent shipped its first deliverable, considered to be somewhat late for its three investors and approximately 100 developer companies. It is a prebeta developer preview called the Partners Early Experience Kit (PEEK), consisting of 80 frameworks for AIX only.[36]

Apple was and will remain the only vendor of a desired target OS which is physically incapable of receiving Taligent's heavy payload due to System 7's critical lack of modern features such as preemptive multitasking. However, Taligent reportedly remains so committed to boosting the industry's confidence in Apple's modernization that it is considering creating a way to hybridize TalOS applications for the nascent System 7, and Apple reportedly intends for the upcoming Power Macintosh to boot native TalOS as a next-generation alternative to System 7. The second-system effect is uniquely intensified because Apple is beginning to view the architecturally superior TalOS as a competitor against the protractedly weak System 7 which has no successor in sight. InfoWorld reported this: "Developers and analysts also said that Taligent's fate is closely tied to that of OS/2 and the other as-yet-undelivered operating systems that it is designed to run on top of." This would include Apple, Windows NT, and the yet unreleased Windows 95.[36] A 1994 detailed report by INPUT assesses that Taligent's "very risky" future will depend not on its technology, but on support from IBM and major developers, the rapid and cheap development of applications and complex integration tasks, and the ability to create new markets.[37]

At this point, Apple was reportedly "hedging its bets" in formulating a strategy to deliver the second-system TalAE, while remaining primarily devout to System 7. The company intended to soon introduce the PowerOpen platform of PowerPC AIX, which would deliver TalAE for running a hopefully forthcoming class of applications, simultaneously alongside Macintosh Application Services for running legacy System 7 personal applications.[36]

CommonPoint
CommonPoint
Developer(s)Taligent Inc.
Written inC++
Operating systemAIX, OS/2
LicenseProprietary
No company is going to bet their project or job on a piece of software that is a 1.0 release. [Taligent has] another year or year and a half's worth of work ahead, because you only prove reliability from being out there.[38]

Steve Jobs, 1995

On July 28, 1995, Taligent shipped its first product, CommonPoint 1.1 (originally named TalAE) for AIX. It was initially priced at US$1,500 for only the runtime framework, or US$5,900 for the runtime framework and the software development kit (which requires the US$1,800 Cset++ compiler). The runtime has an overhead of 18MB RAM for each machine[39] and 32 MB total system RAM is recommended.[36] Though essentially on schedule by the company's own PEEK projections last year,[36] some analysts considered it to be "too little, too late" especially compared to NeXT.[38] Several beta test sites were very pleased with the platform.[39][8] Hewlett-Packard wrote a beginner's guide for CommonPoint programmers, saying that its survey showed that experienced C++ framework programmers needed at least three months to even approach their first application.[33]

Meanwhile at Apple, the one-year-old Copland reached a primitive and notoriously unstable developer preview release, and Apple's frustrated lack of operating system strategy still had not shipped anything physically capable of running CommonPoint.

New leadership

By 1995, it was estimated that the three investors had spent more than $100 million on Taligent, Inc.[40]

In September 1995, CEO Joe Guglielmi unexpectedly exited Taligent to become VP of Motorola, intensifying the industry's concerns. Dick Gurino was named the interim CEO in search of a permanent CEO.[40] In October 1995, Gurino died of a heart attack while jogging, leaving the company without a CEO. On December 19, 1995, founding Taligent employee and Apple veteran Debbie Coutant was promoted to CEO.[41][2][22]

On the same day as receiving what would be its final CEO, Taligent Inc. also ended its partnership form. Apple and HP sold out their holdings in the company, making Taligent Inc. a wholly owned subsidiary of IBM alone. While dissolving the partnership, each of the three former partners expressed approval of Taligent's progress. In what they called overall enterprise-wide cost-cutting processes, Apple and HP wanted to simply maintain technology licenses, IBM wanted to use its own redundant marketing and support departments, and Taligent wanted to focus only on technology. In the process, nearly 200 of the 375 employees were laid off, leaving only engineering staff. Apple veteran and Taligent cofounding employee, Mike Potel, was promoted from VP of Technology to CTO, saying, "We're better protected inside the IBM world than we would be trying to duke it out as an independent company that has to pay its bills every day."[2]

Now, the company's mission became to unbundle the technology of CommonPoint, and to redistribute it across IBM's existing products or license it to other companies – all with a special overall focus on Java.[22] Dr. Dobb's Journal observed, "I guess it's easier to develop hot technology when the guys before you have already written most of it. Like inheriting from a rich uncle. And having another rich uncle to sell it for you doesn't hurt, either."[22]

In November 1996, the final public demonstration of the complete native TalOS was given, titled "The Cutting Edge Scenario". While referring to the original codename of "Pink", Taligent had already officially abandoned the never-published native TalOS in favor of CommonPoint.[42]

TalOS was unique in its architecture. It was object oriented from the kernel up, and provided true pre-emptive multi-threaded multi-tasking. The end user experience revolved around a compound document-centric, multi-user networked, direct manipulation interface with infinite session undo. The principal interface theme was People, Places and Things. The networked interface represented remote users, as well as collaborative work spaces. In many ways it was more a graphic MOO (multi-user dimension-object oriented) than a traditional operating system.[42]

Tom Dougherty, Taligent engineer

In February 1997, Taligent started contributing some CommonPoint frameworks to VisualAge for C++ 4.0., which PC Mag said were "unmatched" in "sheer breadth of features".[43] Taligent was at the core of IBM's companywide shift to a Java-based middleware strategy in 1997.[44] Taligent provided all Unicode internationalization support for Java Development Kit 1.1.[22] In 1997, Taligent was still leasing the same building from Apple, and JavaSoft was located across the street. But its parent IBM, and the related Lotus, were located on the east coast and was not fully aware of Taligent's activities.[45]

Apple canceled the unstable Copland in August 1996, which had already been renamed "Mac OS 8". Apple's own book Mac OS 8 Revealed (1996) had been the definitive final roadmap for Copland, naming the platform's competitors and allies, and yet its 336 pages contain no mention of Pink or Taligent.[46] In late 1996, Apple was more desperately scrambling to find any operating system strategy whatsoever beyond System 7 even with a planned announcement of such in December 1997.[7]:228–229 The company had failed to deliver even a functional developer preview of Copland in two years; and it discarded the successful A/UX and PowerOpen platforms in 1995, and the new AIX-based Apple Network Server of 1996-1997. To build the future Mac OS, the company seriously explored licensing other third party OSes such as Solaris, Windows NT, and TalOS.[7]:228–229

Dissolution

On September 16, 1997, IBM announced that Taligent Inc. would be dissolved by the end of the year, with its approximately 100 software engineers being "offered positions at IBM's Santa Teresa Laboratory to work on key components for IBM's VisualAge for Java programming tools, including VisualAge for Smalltalk, and at the recently announced Java porting center that IBM is setting up with Sun Microsystems and Netscape".[47]

Reception

By 1993, one year after incorporation and two years before shipping its first product, Taligent was nonetheless seen as a significant competitor in the industry. UnixWorld said that "NeXT needs to increase its volume three-fold [over its existing 50,000 installations] in order to build enough momentum to forestall Microsoft and Taligent in the object-oriented software business."[48]

In a survey we conducted, learnability was mentioned as a main inhibitor to framework use by developers familiar with frameworks, and early developers with Taligent experienced "a stiff learning curve" even for experienced C++ programmers. ... The time it takes to become a productive developer with Taligent frameworks is long (at least three months until you can approach your first application)."

A Beginner's Guide to Developing with the Taligent Application Frameworks, Hewlett-Packard, 1995[33]

In 1994, several beta test sites were impressed with CommonPoint, including one production success story at American Express which replaced its existing six month legacy application in only six weeks. At first in 1994, they'd said "We are almost overwhelmed by the complexity of [CommonPoint]. I don't know if the typical corporate developer is going to be able to assimilate this in their shop."[36] but in 1995 they concluded the project with, "The CommonPoint frameworks – and I'm not exaggerating – are brilliant in the way they cover the technical issues [of that project]."[39]

Taligent's frameworks are all coordinated much better than others I've seen. They're designed to work together with the underlying kernel, in a fashion similar to the Mac's ROM Toolbox calls, but on a supremely more advanced level. Nextstep is the closest thing to Taligent but it's already old and not nearly as advanced—despite the fact that until now it's been the fastest development platform, bar none. We have spoken with people who have used Nextstep and we considered it, but it's clear to us that CommonPoint is the next Nextstep, if you will.

Jerzy Lewak, CEO of Nisus Software, 1995[8]

In February 1997, PC Mag said "Although the technology was lauded by many, the size and complexity of the CommonPoint frameworks proved too daunting for practical purposes. ... For sheer breadth of features, the Taligent frameworks are unmatched".[43]

PCWorld named the native Taligent OS as #4 of 15 of the top vaporware products of all time.[49]

Due to the second-system effect and corporate immune response, Wired writer Fred Davis compared Taligent's relationship with Apple and IBM to a classic Greek tragedy: "A child is born, destined to kill its father and commit even more unspeakable acts against its mother. The parents love their child and are unwilling to kill it, so they imprison it in a secret dungeon. Despite its mistreatment, the child grows stronger, even more intent on committing its destined crimes."[13]

In 1995, writer Don Tennant asked Bill Gates to reflect upon "what trend or development over the past 20 years had really caught him by surprise". Gates responded with what Tennant described as biting, deadpan sarcasm: "Kaleida and Taligent had less impact than we expected." Tennant believed the explanation to be that "Microsoft's worst nightmare is a conjoined Apple and IBM. No other single change in the dynamics of the IT industry could possibly do as much to emasculate Windows."[50]

Legacy

The founding lead engineer of Pink, Erich Ringewald, departed Apple in 1990 to become the lead software architect at Be Inc. and design the new Be OS.[51] Mark Davis cofounded the Unicode Consortium, was Taligent's Director of Core Technologies and architect of all its internationalization technology, became IBM's Chief Software Globalization Architect, moved to Google to work on internationalization and Unicode,[22] and now helps to choose the emojis for the world's smartphones.[52] Ike Nassi had been VP of Development Tools at Apple, launched MkLinux, served on the boards of Taligent and the OpenDoc Foundation, and worked on the Linksys iPhone.[53]

IBM used parts of CommonPoint to create the Open Class libraries for VisualAge for C++, and spawned an open-source project called International Components for Unicode from part of this effort. Resulting from Taligent's work led by Mark Davis, IBM published all of the internationalization libraries that are in Java Development Kit 1.1 along with source code[22][45] which was ported to C++ and partially to C. Enhanced versions of some of these classes went into ICU for Java (ICU4J) and ICU for C (ICU4C).[54] Davis's group became the Unicode group at the IBM Globalization Center of Competency in Cupertino.[54]

Taligent created a set of Java- and JavaBeans-based development tools called WebRunner, a groupware product based on Lotus Notes called Places for Project Teams, and licensed various technologies to Sun Microsystems which are today part of Java, and to Oracle Corporation and Netscape Communications Corporation. HP released the Taligent C++ compiler technology (known within Taligent as "CompTech") as its "ANSI C++" compiler, aCC. HP also released some computer graphics libraries that had been developed at Taligent.

Some of Apple's personnel and design concepts from Pink and from Purple (the original iPhone codename)[55][56] would resurface in the late 2010s and blend into the Google Fuchsia operating system. Intended to envelop and succeed Android, its open-source software repository was launched in 2016 with the phrase "Pink + Purple == Fuchsia".[57]

Notes
  1. Primary sources Erich Ringewald[5]:96 and Mike Potel[1]:xiii,6 date the start of Pink as "March 1988" or "early 1988", and Apple Confidential 2.0 says "March 1987".[7]:69
gollark: This demonstrates many things:- images (externally linked, admittedly)- the existence of an edit button- URLs which exist- wikilinks with nonexistence checking apioids
gollark: Here is an image from earlier.
gollark: YOU *CANNOT* STOP MINOTEAUR.
gollark: I WILL CONTINUE TO DO THINGS.
gollark: NO.

References
  1. Cotter, Sean; Potel, Mike (1995). Inside Taligent Technology. Addison-Wesley. ISBN 0-201-40970-4. OCLC 1072525751. Retrieved February 10, 2019.
  2. Einsetin, David (December 20, 1995). "Taligent to Be IBM Subsidiary / Nearly 200 workers to lose their jobs". SF Chronicle. Retrieved January 31, 2019.
  3. Pollack, Andrew (October 3, 1991). "I.B.M. Now Apple's Main Ally". The New York Times. Retrieved March 5, 2019.
  4. Metz, Cade (October 3, 2008). "Apple surrenders the Pink (to Microsoft)". The Register. Retrieved February 13, 2019.
  5. Carlton, Jim (1999) [1997]. Apple: The Inside Story of Intrigue, Egomania and Business Blunders (hardback) (2nd ed.). London: Random House Business Books. ISBN 978-0099270737. OCLC 925000937.
  6. Hormby, Tom (April 27, 2014). "Pink: Apple's First Stab at a Modern Operating System". Low End Mac. Retrieved February 1, 2019.
  7. Linzmayer, Owen (2004). Apple Confidential 2.0: The Definitive History of the World's Most Colorful Company. No Starch Press. ISBN 1-59327-010-0.
  8. Santalesa, Rich (1995). "Taligent Readies a New Development Paradigm" (PDF). IEEE Software. Retrieved October 3, 2017.
  9. "Why did Taligent fail?". Retrieved January 31, 2019.
  10. Reimer, Jeremy (November 24, 2013). "Half an operating system: The triumph and tragedy of OS/2". Ars Technica. Retrieved February 12, 2019.
  11. Silberling, Robin. "Taligent Portfolio". Robin Silberling. Archived from the original on May 19, 2007. Retrieved February 9, 2019.
  12. "About the CommonPoint human interface". Taligent, Inc. 1995. Archived from the original on June 24, 2007. Retrieved February 9, 2019.
  13. Davis, Fred (February 1, 1993). "Surrender the Pink!". Wired. Condé Nast. Retrieved February 1, 2019.
  14. Christopher, Ken; Winters, Scott; Wright, Mary Pollak (1995). IBM's Official OS/2 Warp Connect PowerPC Edition: Operating in the New Frontier. Foster City, CA: IDG Books. ISBN 978-1-56884-458-9. OCLC 832595706.
  15. . Tom Moran, ed. "Taligent Rising". MacWorld: 34–35. August 1994. Retrieved February 10, 2019.CS1 maint: others (link)
  16. Engst, Adam (February 24, 1992). "Taligent Up & Running". Tidbits. Retrieved February 10, 2019.
  17. Pitta, Julie (November 18, 1995). "IBM, Apple Will Close Door on Kaleida Labs". LA Times. San Francisco. Retrieved January 31, 2019.
  18. Transforming Your Business With Object Technology. Austin, TX: IBM. November 1993. p. 15. Retrieved February 9, 2019.
  19. Fisher, Lawrence M. (February 25, 1992). "Executives Appointed To I.B.M.-Apple Venture". The New York Times. Retrieved February 10, 2019.
  20. "Corporate Culture Shock: An IBM-Apple Computer Joint Venture". Fortune. April 5, 1993. Retrieved February 9, 2019.
  21. "Taligent plans to earn business with a better OS". InfoWorld: 110. March 2, 1992. Retrieved February 5, 2019.
  22. Swaine, Michael (September 1, 1997). "Phoenix in Cupertino". Dr. Dobb's. Retrieved February 9, 2019.
  23. Wylie, Margie (March 16, 1992). "Apple won't pin all of its future hopes on Taligent". Network World. Retrieved February 1, 2019.
  24. Taligent (1993). Leveraging Object-oriented Frameworks. IBM. p. 15. Retrieved February 12, 2019.
  25. "SFA Atlanta 1994". March 1994. Retrieved January 31, 2019.
  26. Andert, Glenn. "Object Frameworks in the Taligent OS" (PDF). Taligent Inc. Retrieved February 13, 2019. Cite journal requires |journal= (help)
  27. Potel, Mike; Grimes, Jack (1994). "The Architecture of the Taligent System". Dr. Dobb's Journal: The Interoperable Objects Revolution (Special ed.). Retrieved February 21, 2019.
  28. Addison, Ken (July 1992). "MacApp is Bedrock is MacApp". MacTech. 4 (6). Retrieved February 13, 2019.
  29. Ticktin, Neil (March 1994). "Shaking, Changing, Looking For Bedrock". MacTech. 10 (3).
  30. "Taligent's Guglielmi eyes future of object technology". InfoWorld: 6. January 24, 1994. Retrieved February 10, 2019.
  31. Barney, Doug (November 14, 1994). "Taligent applications begin to surface". InfoWorld. Retrieved February 1, 2019.
  32. Tribble, Bud (February 1994). "Bud Tribble Explains It All". NeXTWORLD (Interview). Interviewed by NeXTWORLD. p. 23-24. Retrieved February 10, 2019.
  33. Laubsch, Joachim (September 6, 1995). "A Beginner's Guide to Developing with the Taligent Application Frameworks" (PDF). Hewlett-Packard Laboratories. Retrieved October 3, 2017. Cite journal requires |journal= (help)
  34. Dvorak, John C. (April 26, 1994). "IBM's Workplace OS Explained". PC Magazine. p. 93. Retrieved March 4, 2019.
  35. Scannell, Ed; Brandel, William (April 11, 1994). "Industry turning to components". ComputerWorld: 1. Retrieved February 13, 2019.
  36. "Taligent's leader discusses firm's first PEEK at PC Expo". InfoWorld: 1,8. June 27, 1994. Retrieved February 9, 2019.
  37. Object-Oriented Platforms for Client/Server Systems. INPUT. 1994. Retrieved February 10, 2019.
  38. Abate, Tom (June 6, 1995). "Analysts wary of late software by Taligent". SF Gate. Retrieved February 10, 2019.
  39. Cox, John (June 12, 1995). "IBM to release app framework on AIX". NetworkWorld: 35–36. Retrieved February 10, 2019.
  40. Picarille, Lisa (September 11, 1995). "CEO exits, Taligent future unclear". Computerworld. Retrieved February 3, 2019.
  41. "executive team". Taligent. 1997. Archived from the original on July 7, 1997. Retrieved February 14, 2019.
  42. Dougherty, Tom (November 1996). "What does Pink sound like? Designing the Audio Interface for the TalOS". International Conference on Auditory Display. Retrieved February 9, 2019.
  43. Gagnon, Gabrielle (February 4, 1997). "VisualAge for C++ 4.0: Previewing Taligent". PC Mag: 206. Retrieved February 12, 2019.
  44. "IBM Embraces Java Everywhere". InfoWorld. Vol. 19 no. 8. 1997-02-24. p. 8. ISSN 0199-6649. Retrieved 2019-08-14 – via Google.
  45. Tennant, Don. "Taligent could still be a strategic IBM asset". FoRK Archive.
  46. Francis, Tony (1996). Mac OS 8 Revealed. Reading, Mass.: Addison-Wesley, Apple Press. ISBN 9780201479553. OCLC 951335545. Retrieved February 23, 2019.
  47. "Taligent Transition Into IBM Scheduled by Year-End". Taligent Inc. 1997. Archived from the original on December 11, 1997. Retrieved February 12, 2019.
  48. "Steve's Gone Soft". UnixWorld. McGraw-Hill: 44. April 1993. In its existence, Next has sold a total of 50,000 copies of Nextstep, says Jobs. It's not much of an installed base, so he predicts the company will ship 50,000 Nextstep packages in 1993. But Next needs to increase its volume three-fold in order to build enough momentum to forestall Microsoft and Taligent in the object-oriented software business.
  49. Townsend, Emru (May 4, 2008). "The Top 15 Vaporware Products of All Time". PC World. Retrieved February 11, 2019.
  50. Tennant, Don (March 3, 2008). "Emasculating Windows". ComputerWorld. IDG. Retrieved February 23, 2019.
  51. "Be Newsletter". 3 (8). March 25, 1998. Retrieved February 1, 2019. Cite journal requires |journal= (help)
  52. NPR Staff (October 25, 2015). "Who Decides Which Emojis Get The Thumbs Up?". NPR. Retrieved February 10, 2019.
  53. Nassi, Ike (August 26, 2016). "Nassi, Ike oral history" (Video). CHM Oral History Collection. Interviewed by John Markoff. Text transcript. Computer History Museum. 102717191. Retrieved February 9, 2019.
  54. "Introduction to ICU". ICU. Retrieved February 10, 2019.
  55. Murtazin, Eldar; Antonenko, Maxim; Nikolaychuk, Olexandr; translators (June 20, 2010). "Apple's Phone: From 1980s' Sketches to iPhone. Part 3". Mobile-Review. Retrieved March 5, 2019.
  56. Lambert, Terry (December 19, 2016). "Here's what it was like to work on the original iPhone, codenamed 'Project Purple'". Business Insider. Retrieved March 4, 2019.
  57. Matte, Daniel (April 10, 2017). "Open-Source Clues to Google's Mysterious Fuchsia OS". IEEE Spectrum. IEEE. Retrieved March 4, 2019.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.