Xref: utzoo comp.sys.misc:1766 comp.os.misc:556 comp.misc:3749 comp.arch:6564 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!cmcl2!yale!spolsky-joel From: spolsky-joel@CS.YALE.EDU (Joel Spolsky) Newsgroups: comp.sys.misc,comp.os.misc,comp.misc,comp.arch Subject: Re: The NeXT machine has been announced! (long) Message-ID: <40382@yale-celray.yale.UUCP> Date: 14 Oct 88 19:25:13 GMT References: <360@elan.UUCP> <17479@gatech.edu> <10634@reed.UUCP> Sender: root@yale.UUCP Reply-To: spolsky-joel@CS.YALE.EDU (Joel Spolsky) Organization: Yale University Computer Science Dept, New Haven CT 06520-2158 Lines: 30 In article <17479@gatech.edu> ken@gatech.UUCP (Ken Seefried iii) writes: | Will they be including any development tools for | the DSP, like the Motorola assembler or (better) C compiler? (reprinted without permission from Byte:) "There is [sic] also a number of library functions (not objects) that allow you to tap into the processing capabilities of the DSP. These libraries provide some 50 functions for performing tasks like fast Fourier transforms, and spectral filtering." BYTE claims the primary compiler is the GNU-C compiler, with the GNU debugger and Emacs, plus Objective-C 4.0, (in which widgets like buttons, scroll bars, etc are "objects" and can be treated as such), and an "Interface Builder" that's kind of like programming hypertalk only it generates full blown programs, not hyperstacks. | I spent a little time doing work with optical disk technology, | and it was far, far to slow to be primary main storage. What | magic has NeXT worked to make it suitable? None. Average seek time = 96 ms. +----------------+---------------------------------------------------+ | Joel Spolsky | bitnet: spolsky@yalecs uucp: ...!yale!spolsky | | | arpa: spolsky@yale.edu voicenet: 203-436-1483 | +----------------+---------------------------------------------------+ #include