Groups | Search | Server Info | Login | Register

Groups > comp.lang.logo > #115

Re: Does Logo need a refresh?

Show all headers | View raw

Hi Mike,

I'm thinking for quite some time about a refresh of Logo. It was my programming language back in the 80 and always felt that there are still dark corners that need to be lightened. Over the last years I saw all implementations ageing and vanishing. So I sat down and made a list what would be important for me:

- UCBLogo (BerkeleyLogo) primitive set (for it is the most complete I know)
- App to be used offline
- Open Source, well documented, programmed in a language available on all platforms
- Reference implementation for all common platforms (Linux, macOS, Windows, ...)
- Especially the editor window has to be up to modern standards (prim highlighting)
- Not sure if a multi-window or one window with fixed regions environment serves best
- Beside a reference book there should be a book with ideas for enthusiasts
- There also has to be a book for students and accompanying a teachers book

You see that my approach comes from another angle which adds to yours. Still these are just my ideas open for discussion.

Have a great day

Qitam


On Wednesday, 3 February 2021 at 18:06:00 UTC+1, daum...@gmail.com wrote:

> Let me introduce myself. I am the author of Terrapin Logo (since 1993, actually). Terrapin Logo is still used to teach young students all over the world, and I continue to see feedback and provide support. 
> 
> I have all kinds of feedback at Terrapin, mostly from teachers who want to teach Logo, and I think that Logo shows its age. What I would like to do is to define and create an updated version of the Logo programming language which should be more children-friendly in terms of syntax, and easier to compile. 
> 
> Here are a few random thoughts: 
> 
> - Get away with the colon notation for variables. Kids and teachers struggle a lot with this feature. 
> - Simpler strings (with two single or double quotes) to make it more compatible with other languages and to allow multiline strrings and embedded variables in a {NAME} syntax. 
> - Variables are either local or global, but no scope chain across the call stack (what you would call lexically scoped). Accidentally accessing a variable that a grand-grandparent caller introduced is not helpful. 
> - Remove DEFINE and TEXT; PRINOUT could print a procedure, but it may look differently due to optimizations - makes it easier to compile Logo. 
> - A centralized definition of a standard library. 
> 
> I’d set up a Github repo, and start producing documentation that we could work on together. When the dust settles, we could add a reference implementation in Javascript (Terrapin Logo is written in Javascript, and it is pretty darn fast, able to drive up to 1000 turtles). 
> 
> Thoughts and comments are most welcome.

Back to comp.lang.logo | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Does Logo need a refresh? Michael Daumling <daumling@gmail.com> - 2021-02-03 09:05 -0800
  Re: Does Logo need a refresh? Bruce Axtens <snetxa@hotmail.com> - 2021-02-08 15:12 +0800
    Re: Does Logo need a refresh? Michael Daumling <daumling@gmail.com> - 2021-02-12 03:32 -0800
  Re: Does Logo need a refresh? Bruce Axtens <snetxa@hotmail.com> - 2021-02-08 15:23 +0800
  Re: Does Logo need a refresh? Qitam Nova <qitam.nova@gmail.com> - 2021-02-13 02:41 -0800
    Re: Does Logo need a refresh? Michael Daumling <daumling@gmail.com> - 2021-02-13 06:54 -0800
  Re: Does Logo need a refresh? Bruce Axtens <snetxa@hotmail.com> - 2021-02-15 10:47 +0800
  Re: Does Logo need a refresh? "yews...@gmail.com" <yewsiedu@gmail.com> - 2021-06-04 11:50 -0700

csiph-web