Re: non-Cocoa functions at times was Re: address of method in a class instance
Re: non-Cocoa functions at times was Re: address of method in a class instance
- Subject: Re: non-Cocoa functions at times was Re: address of method in a class instance
- From: Matthew Formica <email@hidden>
- Date: Thu, 06 Sep 2001 13:38:21 -0700
on 9/6/01 11:31 AM, Erik M. Buck at email@hidden remarked:
>
> This is not possible under the circumstances where he is using it. There
>
> are, *SHOCK HORROR* reasons to use non-Cocoa functions at times, in case
>
> you hadn't noticed.
>
>
>
>
Only because Apple has removed functionality, broken many things, and
>
created new non-Cocoa APIs. In NeXTstep and Openstep, there was no Carbon
>
like API. There were many C functions just are there are in Cocoa now.
>
>
NeXtstep had the following APIs:
>
Mach (messaging, memory allocation, swap file, threading, process
>
management)
>
BSD (Network stack, file systems, countless utilities, pre-POSIX versions of
>
math, stdlib, stdio, etc.)
>
DisplayPostscript (DPS client lib functions and PSWraps)
>
Objective-C classes (IOKit for drivers, SNDKit for sound, NeXTtime for
>
movies, AppKit, Indexing Kit for searching, PhoneKit, 3DKit, MusicKit,
>
NIAccess for netinfo, a standard and capable installation system with
>
uninstall, DBKit and later EOF)
>
>
Apple has removed the equivalents of IOKit, SNDKit, NeXTTime, IndexingKit,
>
PhoneKit, 3dKit, MusicKit, and NIAccess and when Apple provides any
>
replacement at all, the replacement is Carbon based, and often inferior.
Feel free to file enhancement requests on any of these on
bugreporter.apple.com - looking through those is part of the process Apple
uses to decide what to implement/bring back. Sending email to
email@hidden is good to - those are official forums that
decision-makers read, while this list is not (stuff can get lost in the
noise here, etc.).
>
>
A) What was wrong with IOKit ?
>
B) Sherlock is CRAP (not to mince words). What were they thinking?
>
IndexingKit had a horrible implementation, but its functionality dwarfed
>
current Sherlock.
>
C) Sound, music, and movies have all been subsumed in QuickTime. QuickTime
>
has many great features, but its legacy on an OS without memory protection
>
and its fetish to pretend that pointers do not exist make it a real bitch to
>
program.
>
D) IndexingKit did need an overhaul, but why replace it with the
>
embarrassment of Sherlock. There is a whole team that needs to go back to
>
school and or change careers. Sherlock ranks up there with HelpViewer.
No need to get personal.
>
E) Why was NIAccess killed ? Where is the replacement ?
Like I said, feel free to file an enhancement request asking for the
functionality/API you want.
>
F) Where is the standard and capable software installation system with
>
uninstall support ?
>
G) Why kill EOF for the desktop ?
>
>
Apple has delivered an OS-X that is less complete than NeXTstep was in 1992.
Oh, please.
>
While they were at it, they made it slower than it was in 1992 on 1992
>
hardware. From a Cocoa/Openstep/NextStep programmer's point of view, they
>
have removed functionality.
>
>
What is wrong with Apple ?
Hey, at least we give you a list to complain on. ;->
>
Can the collective Net experience think of any
>
computer companies that say what they are going to do and then do it ? It
>
is called reliability. It is called good business practices. Does Apple
>
expect its suppliers to treat it as badly as it treats its developers?
>
Apple is just an API supplier for OUR products. We are NOT suppliers for
>
Apple. Apple works for US or else they don't get our money or our
>
applications. Can the collective Net experience think of any computer
>
company besides Apple that hides basic information about the future
>
directions of the company from its suppliers and developers ?
>
_______________________________________________
>
cocoa-dev mailing list
>
email@hidden
>
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Matthew Formica
Apple DTS Engineer - Dev Tools and Cocoa
email@hidden