On Sat, Nov 16, 2024, 3:14 PM Jon Elson via cctalk
wrote:
> They SHOULD have started with a clean sheet, of course.
I guess the iAPX 432 wasn't sufficiently "clean sheet" :-)
>
>
> >
> >
> > On 11/15/2024 8:49 PM, Mike Katz wrote:
> >> Which "The Book" are you talking about.
> >>
> >
> > BASIC PROGRAMMING Second Edition By John G. Kemeny and Thomas E. Kurtz
> >
> > Is there any other authority on BASIC?
> >
> > bill
> >
>
>
Kurtz came to VCF East, did a talk, and gave o
On 11/16/24 15:43, Mike Katz via cctalk wrote:
Think of how much better the state of the microprocessor
would be IBM had chosen the 68000 Linear Architecture
rather than the 8086 Segment:Offset with separate I/O
instructions and only 1 interrupt architecture.
I don't mean to start a huge arch
On Sat, Nov 16, 2024, 3:48 PM Mike Katz wrote:
> The IAPX432 came out the same year that the IBM PC came out which was 3
> years after the 8086
I'm fairly sure design work on the 432 began first.
On 11/16/24 16:24, Fred Cisin via cctalk wrote:
> So, Intel went with the "quick fix" rather than the long-term good.
Okay, I vass dere and know what we were being told by Intel marketing in
the late 70s. The 8086 was not intended to be the eventual migration
target for larger-scale applications
In order to have the "world beat a path" to a new microprocessor is has
the be sufficiently better than what is there to justify the time and
expense. Intel doesn't know how to architect a decent CPU. They just
keep kludging their previous successes.
From what I heard from some inside source
I got my book at the Kiewit Computation Center at Dartmouth in 1972 and
by then it was 6th Edition. Currently I have the 7th Edition book.
My first book on basic was Basic Basic by James S. Coan also in 1972.
On 11/16/2024 7:25 PM, Bill Gunshannon via cctalk wrote:
On 11/15/2024 8:49 PM, Mi
Because the majority of buyers were businesses. - they nearly always
choose the low risk, low reward option.
Only people with vision look forward.
On Sun, 17 Nov 2024, 01:56 Wayne S via cctalk,
wrote:
> Why did those processors not catch on?
> It seems to me that hardware people had a “if we
Why did those processors not catch on?
It seems to me that hardware people had a “if we build it, they will come”
mentality and hoped other companies would adopt it and actually write software
to make it useful.
Sent from my iPhone
> On Nov 16, 2024, at 17:38, Chuck Guzis via cctalk
> wrote:
It didn't hurt that when IBM decide to go with the 8088 they bought
something like 12.5% of Intel's stock.
On 11/16/2024 7:37 PM, Chuck Guzis via cctalk wrote:
On 11/16/24 16:24, Fred Cisin via cctalk wrote:
So, Intel went with the "quick fix" rather than the long-term good.
Okay, I vass de
Was just me or did everyone think 32K words was all a single process
needed in the 70's?
Start with 4K and use paging to give you 32K 12 bit words. Welcome to
the PDP-8 world!!!
Wow you could be running in one 4K field and have your data in another
4K field. Amazing!
And all core me
On 11/15/2024 8:49 PM, Mike Katz wrote:
Which "The Book" are you talking about.
BASIC PROGRAMMING Second Edition By John G. Kemeny and Thomas E. Kurtz
Is there any other authority on BASIC?
bill
On 2024-11-16 2:43 p.m., Mike Katz via cctalk wrote:
Think of how much better the state of the microprocessor would be IBM
had chosen the 68000 Linear Architecture rather than the 8086
Segment:Offset with separate I/O instructions and only 1 interrupt
architecture.
I don't mean to start a hug
> On Nov 16, 2024, at 4:24 PM, Fred Cisin via cctalk
> wrote:
>
> The Mac was released with MacWrite and MacPaint; how long was it before a
> spreadsheet program and other word processors were available?
>
Not to take away from the main thrust of your argument, which is sound, but…
Micros
/So, Intel went with the "quick fix" rather than the long-term good.
<-- Grumpy Old Fred
/And the world has been putting up with that decision with hardware and
software that have gotten klugier and klugier as time goes on.
The 6809 was amazing with what could be done with a random logic 8-b
The IAPX432 came out the same year that the IBM PC came out which was 3
years after the 8086 and 2 years after the 68000.
It was slow and clunky compared to the 68000 and the 8086 was firmly
entrenched in the IBM-PC.
The 8086 used an extension of the very familiar 8080 instruction set and
th
On Sat, 16 Nov 2024, Mike Katz via cctalk wrote:
Think of how much better the state of the microprocessor would be IBM had
chosen the 68000 Linear Architecture rather than the 8086 Segment:Offset with
separate I/O instructions and only 1 interrupt architecture.
I don't mean to start a huge arc
Think of how much better the state of the microprocessor would be IBM
had chosen the 68000 Linear Architecture rather than the 8086
Segment:Offset with separate I/O instructions and only 1 interrupt
architecture.
I don't mean to start a huge architecture argument so please don't flame me.
On
On 11/16/24 12:09, Sid Jones via cctalk wrote:
Purely as a matter of interest, my first hands-on
code-cutting experience with a microprocessor, an 8008,
was at a Swansea University seminar in November 1974...
Where does the off half-century go?
Yup, on my first real job, I did the controller
Purely as a matter of interest, my first hands-on code-cutting experience
with a microprocessor, an 8008, was at a Swansea University seminar in
November 1974...
Where does the off half-century go?
Regards
Sid Jones
-Original Message-
From: Murray McCullough via cctalk
Sent: Saturd
Which "The Book" are you talking about.
For me it would be Dartmouth Basic 6th Edition that I got in 1972 at
Keiwit Computation Center at Dartmouth College in Hanover New Hampshire.
Unfortunately my copy of 6th edition is long bone but I still have my
copy of TM115 Basic 7 User's Guide Dartmo
On 11/15/2024 9:29 AM, Murray McCullough via cctalk wrote:
Today another giant in the ‘microcomputer’ industry has passed: Thomas
Eugene Kurtz a computer scientist, co-creator/inventor with John Kemeny of
the BASIC language that I grew up with. Somewhat dates me!
I still have my copy of T
22 matches
Mail list logo
