Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #52065 > unrolled thread
| Started by | polymorph self <jackvanc3@gmail.com> |
|---|---|
| First post | 2016-10-20 14:55 -0700 |
| Last post | 2016-10-22 19:08 +1000 |
| Articles | 8 — 6 participants |
Back to article view | Back to comp.lang.forth
GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. polymorph self <jackvanc3@gmail.com> - 2016-10-20 14:55 -0700
Re: GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. polymorph self <jackvanc3@gmail.com> - 2016-10-20 15:10 -0700
Re: GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. polymorph self <jackvanc3@gmail.com> - 2016-10-20 15:10 -0700
GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. clozaga@gmail.com - 2016-10-20 20:58 -0700
Re: GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. Paul Rubin <no.email@nospam.invalid> - 2016-10-20 22:35 -0700
Re: GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. Roelf Toxopeus <rt4all@nothishetnet.nl> - 2016-10-23 01:36 +0200
Re: GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. hughaguilar96@gmail.com - 2016-10-22 21:32 -0700
Re: GEOS managed to offer nearly all the functionality of the originalMac in a 1 MHz computer with 64 Kilobytes of RAM. "HAA" <someone@microsoft.com> - 2016-10-22 19:08 +1000
| From | polymorph self <jackvanc3@gmail.com> |
|---|---|
| Date | 2016-10-20 14:55 -0700 |
| Subject | GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. |
| Message-ID | <3a1a81cc-ca21-4370-b3ba-85abb2fcf3ba@googlegroups.com> |
http://mobile.osnews.com/story.php/15223/GEOS_The_Graphical_Environment_Operating_System can forth do better?
[toc] | [next] | [standalone]
| From | polymorph self <jackvanc3@gmail.com> |
|---|---|
| Date | 2016-10-20 15:10 -0700 |
| Message-ID | <9bc571e0-3e8a-47e2-9553-a332fbde71a1@googlegroups.com> |
| In reply to | #52065 |
On Thursday, October 20, 2016 at 5:55:56 PM UTC-4, polymorph self wrote: > http://mobile.osnews.com/story.php/15223/GEOS_The_Graphical_Environment_Operating_System > > can forth do better? https://en.wikipedia.org/wiki/Commodore_Plus/4
[toc] | [prev] | [next] | [standalone]
| From | polymorph self <jackvanc3@gmail.com> |
|---|---|
| Date | 2016-10-20 15:10 -0700 |
| Message-ID | <79b880e7-f6c6-49c3-ac43-a74016f26855@googlegroups.com> |
| In reply to | #52068 |
On Thursday, October 20, 2016 at 6:10:06 PM UTC-4, polymorph self wrote: > On Thursday, October 20, 2016 at 5:55:56 PM UTC-4, polymorph self wrote: > > http://mobile.osnews.com/story.php/15223/GEOS_The_Graphical_Environment_Operating_System > > > > can forth do better? > > https://en.wikipedia.org/wiki/Commodore_Plus/4 https://en.wikipedia.org/wiki/Chuck_Peddle
[toc] | [prev] | [next] | [standalone]
| From | clozaga@gmail.com |
|---|---|
| Date | 2016-10-20 20:58 -0700 |
| Message-ID | <84ed6d47-be56-4a71-a004-79f7659f9a5d@googlegroups.com> |
| In reply to | #52065 |
Forth generates very compact threaded code it could be ideal for a 64k machine in that regard. However it may not be as performing as assembler, which much of GEOS depended on.
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2016-10-20 22:35 -0700 |
| Message-ID | <87insmnu12.fsf@nightsong.com> |
| In reply to | #52078 |
clozaga@gmail.com writes: > Forth generates very compact threaded code it could be ideal for a 64k > machine in that regard. However it may not be as performing as > assembler, which much of GEOS depended on. I expect most Forth systems of that era relied on asm code for the speed sensitive parts. The Canon Cat code was posted here not that long ago. It was mostly in Forth but had a fair amount of Z80(iirc) assembly code.
[toc] | [prev] | [next] | [standalone]
| From | Roelf Toxopeus <rt4all@nothishetnet.nl> |
|---|---|
| Date | 2016-10-23 01:36 +0200 |
| Message-ID | <580bf7fb$0$1807$e4fe514c@textnews.kpn.nl> |
| In reply to | #52081 |
On 21/10/2016 07:35, Paul Rubin wrote: > clozaga@gmail.com writes: >> Forth generates very compact threaded code it could be ideal for a 64k >> machine in that regard. However it may not be as performing as >> assembler, which much of GEOS depended on. > > I expect most Forth systems of that era relied on asm code for the speed > sensitive parts. The Canon Cat code was posted here not that long ago. > It was mostly in Forth but had a fair amount of Z80(iirc) assembly code. > Sorry nitpicking: Canon Cat = Motorola 68000 Jupiter Ace = Z80
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-10-22 21:32 -0700 |
| Message-ID | <7f58d58a-e820-450d-b1cb-c34be0643d0d@googlegroups.com> |
| In reply to | #52081 |
On Thursday, October 20, 2016 at 10:35:54 PM UTC-7, Paul Rubin wrote: > clozaga@gmail.com writes: > > Forth generates very compact threaded code it could be ideal for a 64k > > machine in that regard. However it may not be as performing as > > assembler, which much of GEOS depended on. > > I expect most Forth systems of that era relied on asm code for the speed > sensitive parts. The Canon Cat code was posted here not that long ago. > It was mostly in Forth but had a fair amount of Z80(iirc) assembly code. The Canon Cat was for the MC68000.
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2016-10-22 19:08 +1000 |
| Subject | Re: GEOS managed to offer nearly all the functionality of the originalMac in a 1 MHz computer with 64 Kilobytes of RAM. |
| Message-ID | <nuf6qm$1kfd$1@gioia.aioe.org> |
| In reply to | #52078 |
clozaga@gmail.com wrote: > Forth generates very compact threaded code it could be ideal for a 64k machine in that > regard. However it may not be as performing as assembler, which much of GEOS depended > on. Speed aside, simple functions can be more compact in assembler than threaded Forth. A good number of bytes can be shaved from a Forth kernel applying such a strategy. In practice the C64 had much less memory available to programs than 64K. At the end of the day it was just a games machine (as was the Amiga).
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.forth
csiph-web