Content deleted Content added
m Adding archives WP:LINKROT |
|||
Line 134:
=====Technology=====
The Pink operating system is now formally named Taligent Object Services (TOS or TalOS) whether hosted natively on its microkernel or non-natively on a third party OS, but the nickname "Pink" will always remain industry lore,<ref name="Inside Taligent Technology"/> such as with the developer phone number 408-TO-B-PINK.<ref name="Leveraging">{{cite book |title=Leveraging Object-oriented Frameworks |publisher=IBM |author=Taligent, Inc. |date=1993 |url=https://archive.org/stream/IBMTaligent/TALOOF |page=15 |access-date=February 12, 2019}}</ref> The entire graphics subsystem is 3D, including the 2D portions which are actually 3D constructs.<ref name="SFA 1994">{{cite web |title=SFA Atlanta 1994 |date=March 1994 |url=http://preserve.mactech.com/articles/frameworks/8_3/1994_Conference_Report.html |access-date=January 31, 2019}}</ref><ref name="Why did Taligent fail">{{cite web |title=Why did Taligent fail? |url=https://www.quora.com/Why-did-Taligent-fail |access-date=January 31, 2019}}</ref> It is based extensively on object-oriented frameworks from the kernel upward, including device drivers, the Taligent [[input/output]] (I/O) system, and ensembles.<ref name="Object Oriented Application Frameworks">{{cite book |title=Object Oriented Application Frameworks |chapter=Chapter 9: Frameworks in Taligent's CommonPoint |pages=231–235 |first=Glenn |last=Andert |publisher=Prentice-Hall |date=1995 |isbn=9780132139847 |oclc=221649869}}</ref><ref name="Object Frameworks in the Taligent OS">{{cite journal |journal=Proceedings of COMPCON '94
|title=Object Frameworks in the Taligent OS |first=Glenn |last=Andert |publisher=Taligent Inc. |pages=112–121 |volume=1 |date=1994 |doi=10.1109/CMPCON.1994.282936 |isbn=0-8186-5380-9 |s2cid=35246202 |url=https://www.semanticscholar.org/paper/Object-Frameworks-in-the-Taligent-OS-Andert/c93c4b37373b3ab641b3aa74f182c034a5b940ac |access-date=March 15, 2019}}</ref> 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]].<ref name="Inside Taligent Technology"/>{{rp|119}}<ref name="Why did Taligent fail"/><ref name="Half an operating system"/><ref name="Transforming Your Business"/>{{rp|14–15}}<ref name="Architecture of Taligent">{{cite magazine |magazine=Dr. Dobb's Journal |edition=Special |title=The Architecture of the Taligent System |first1=Mike |last1=Potel |first2=Jack |last2=Grimes |date=1994 |url=http://collaboration.cmc.ec.gc.ca/science/rpn/biblio/ddj/Website/articles/DDJ/1994/9416/9416f/9416f.htm |access-date=February 21, 2019}}</ref><ref name="IEEE Software March 1995"/> Its text handling and localization via [[Unicode]] was intended to begin enabling the globalization of software development, especially in simplifying Japanese.<ref name="Creating global">{{cite magazine |magazine=IBM Systems Journal |title=Creating global software: Text handling and localization in Taligent's CommonPoint application system |volume=36 |issue=2 |date=1996 |publisher=[[IBM]] |first1=Mark |last1=Davis |first2=Jack |last2=Grimes |first3=Deborah |last3=Knoles |pages=227–243 |url=https://dev.antiguru.de/davis.pdf |archive-url=https://ghostarchive.org/archive/20221009/https://dev.antiguru.de/davis.pdf |archive-date=2022-10-09 |url-status=live |access-date=August 16, 2020}}</ref>
In January 1993, Taligent's VP of Marketing said the strong progress of native TalOS development could encourage its early incremental release prior to the full 1995 schedule for TalAE. Apple's business manager to Taligent [[Chris Espinosa]] acknowledged the irony of Apple and IBM building competing Taligent-based platforms, which had originated at Apple as Pink. He forecast Apple's adoption of Taligent components into the irreplaceably personal Mac OS{{mdash}}while empowering its competitiveness with IBM's future Taligent-based general purpose systems, and easing corporate users' migration toward Apple's Enterprise Systems Division's future Taligent-based computers.<ref name="MacWEEK vol 7 #4">{{cite magazine |magazine=MacWEEK |title=Taligent moves up ship dates, may offer components in '93 |volume=7 |issue=4 |date=January 25, 1993 |url=https://archive.org/details/MacWEEKV07N04/page/n1 |page=3 |access-date=February 22, 2019}}</ref>
Line 242:
In 1994, several PEEK 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."<ref name="Taligent first PEEK"/> 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]."<ref name="IBM to release"/> Others were disappointed in the marked lack of crossplatform presence on HP/UX, Mac OS, and Windows NT which strictly limited any adoption of CommonPoint even among enthusiasts.<ref name="Taligent show"/><ref name="IBM to release"/><ref name="IEEE Software March 1995"/>
{{quote box |text=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)." |source=''A Beginner's Guide to Developing with the Taligent Application Frameworks'', Hewlett-Packard, 1995<ref name="A Beginner's Guide">{{cite book |title=A Beginner's Guide to Developing with the Taligent Application Frameworks |date=September 6, 1995 |first=Joachim |last=Laubsch |publisher=Hewlett-Packard Laboratories |url=http://www.hpl.hp.com/techreports/95/HPL-95-106.pdf |archive-url=https://ghostarchive.org/archive/20221009/http://www.hpl.hp.com/techreports/95/HPL-95-106.pdf |archive-date=2022-10-09 |url-status=live |access-date=October 3, 2017}}</ref>
}}
{{quote box |text=Once you learn CommonPoint and Taligent's system you will be [an] expert C++ programmer, whether you want to or not. ... Basing apps on CommonPoint results in programs that are more consistent internally, cleaner, and allows the framework to do significant grunt work in cooperation with the Taligent environment. ... 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. |author=Nisus Software, March 1995, after three months of Taligent training and three of coding<ref name="IEEE Software March 1995">{{cite journal |title=Taligent Readies a New Development Paradigm |journal=IEEE Software |publisher=[[IEEE]] |first=Rich |last=Santalesa |date=March 1995 |url=https://www.computer.org/csdl/mags/so/1995/02/s2103.pdf |archive-url=https://ghostarchive.org/archive/20221009/https://www.computer.org/csdl/mags/so/1995/02/s2103.pdf |archive-date=2022-10-09 |url-status=live |doi=10.1109/MS.1995.10019 |pages=103–109 |volume=12 |access-date=March 15, 2019}}</ref>
}}
| |||