Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Taligent
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=====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 conference |first=Glenn |last=Andert |book-title=Proceedings of COMPCON '94 |title=Object frameworks in the Taligent OS |publisher=Taligent Inc. |pages=112โ121 |volume=1 |date=1994 |doi=10.1109/CMPCON.1994.282936 |isbn=0-8186-5380-9 |s2cid=35246202 }}</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 |archive-date=August 11, 2014 |archive-url=https://web.archive.org/web/20140811004402/http://collaboration.cmc.ec.gc.ca/science/rpn/biblio/ddj/Website/articles/DDJ/1994/9416/9416f/9416f.htm |url-status=dead }}</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> On January 10, 1993, ''[[The Wall Street Journal]]'' reported on the state of Taligent, saying the company and its platform had the broad optimistic support of [[Borland]], [[WordPerfect]], and [[Novell]]. Borland CEO Philippe Kahn said "Technically, [Pink] is brilliant, and Taligent is running much faster than I expected." A software venture capitalist expected new entrepreneurs to appreciate the platform's newness and lack of legacy baggage, and the industry expected Apple loyalists to embrace a new culture. Regardless of genuine merit, many in the industry reportedly expected Taligent's success to depend upon wounding Microsoft's monopoly.<ref name="Venture Accel">{{cite news |newspaper=[[The Wall Street Journal]] |title=IBM-Apple System Venture Accelerates - Taligent Project Rushes To Challenge Microsoft |first=G. Pascal |last=Zachary |location=[[Brussels]] |date=January 13, 1993 |page=4 |via=[[ProQuest]] |url=https://www.proquest.com/docview/308115472/61BEA5CBC1274C5BPQ/ |access-date=January 10, 2021}}</ref> On January 18, ''[[InfoWorld]]'' reported, "Taligent draws rave reviews from software developers".<ref name="Taligent draws rave reviews">{{cite magazine |magazine=[[InfoWorld]] |title=Taligent draws rave reviews from software developers |first1=Ed |last1=Scannell |first2=Tom |last2=Quinlan |date=January 18, 1993 |url=https://books.google.com/books?id=5DsEAAAAMBAJ&q=taligent&pg=PA3 |page=3 |access-date=March 5, 2019}}</ref> By April 1993, Taligent, Inc. had grown to about 260 employees, mostly from Apple or "some other loose Silicon Valley culture".<ref name="Culture shock"/> ''[[MacWEEK]]'' reported that the company remained on schedule or ahead through 1993 into 1994.<ref name="MacWEEK vol 7 #4"/>{{verify source|date=January 2021}} On June 23, 1993, Apple preannounced MacApp's direct successor, the new object-oriented crossplatform SDK codenamed [[Bedrock (framework)|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.<ref name="MacApp is Bedrock is MacApp">{{cite magazine |first=Ken |last=Addison |url=http://preserve.mactech.com/articles/frameworks/6_4/MacApp_is_Bedrock_Addison.html |title=MacApp is Bedrock is MacApp |magazine=MacTech |volume=4 |issue=6 |date=July 1992 |access-date=February 13, 2019}}</ref> Bedrock would be abruptly discontinued 18 months later with no successor, and leaving Apple with no connection between System 7 and Pink.<ref name="Shaking, Changing, Looking For Bedrock">{{cite magazine |first=Neil |last=Ticktin |url=http://preserve.mactech.com/articles/mactech/Vol.10/10.03/Mar94EditorsPage/index.html |title=Shaking, Changing, Looking For Bedrock |magazine=MacTech |volume=10 |issue=3 |date=March 1994}}</ref> {{quote box |width=25% |align=right |text=[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. |author=Taligent CTO, Mike Potel<ref name="SFA 1994"/> }} By 1994, the platform consisted of Taligent Object Services (TOS or TalOS), Taligent Application Environment (TAE or TalAE), and the Taligent Development System (TDS or TalDS).<ref name="SFA 1994"/><ref name="IEEE Software March 1995"/><ref name="Inside Taligent Technology"/>{{rp|22}} The initial plan was to deploy TalAE in early 1994 to help seed the market with a base of applications for TalOS, which was 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.<ref name="Taligent's Guglielmi eyes">{{cite magazine |magazine=InfoWorld |date=January 24, 1994 |page=6 |title=Taligent's Guglielmi eyes future of object technology |url=https://books.google.com/books?id=_DoEAAAAMBAJ&q=Guglielmi&pg=PA6 |access-date=February 10, 2019}}</ref> Influenced by the results of the survey effort,{{citation needed|date=February 2019}} 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.<!--<ref name="As Taligent Reveals">{{cite journal |magazine=CBR |title=...As Taligent Reveals Object-oriented Strategy |date=April 28, 1993 |author=Staff |url=https://www.cbronline.com/news/as_taligent_reveals_object_oriented_strategy/ |access-date=February 10, 2019 |quote=The potential pitfall of this approach is that the Taligent add-ons could make the conventional offerings so attractive as to damage the acceptance of the native product itself. Guglielmi acknowledges this but says that if his company had ignored the market it would have given competitors free rein. This way, he says, when native Taligent, finally arrives in mid-1995 it will find an industry well stocked with Taligent-compliant tools and objects โ and developers, claims Guglielmi, just love what they have seen so far.}}</ref>--> The first internal development environment was an IBM [[IBM RS/6000#Type 7011|RS/6000 model 250]] with a [[PowerPC 601]] CPU running AIX,<ref name="IEEE Software March 1995"/> building TalOS natively for the 68k Macintosh.<ref name="SFA 1994"/>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)