Re: Language design evolution vs. revolution

On 20 Nov., 18:03, James Harris <james.harri...@xxxxxxxxxxxxxx> wrote:
From what I read people prefer evolution in language design to
revolution. Programmers prefer a language that is similar to what they
already know. They don't like a whole new set of rules - syntax and
otherwise.

Is this how programmers in general feel?

In general I tend to agree with the above view. If I see a new
language I look for familiar constructs to see how understandable it
is. Unless there's an overriding reason to put forth the effort, any
language that is too unfamiliar doesn't seem to be worth learning.

The problem is my language design isn't based on an existing language
and as it is developing it is tending to look rather different and
work slightly different too. Doubtless it is not possible to design in
isolation and any design must be influenced by other languages even if
that is not the intention. However, I have tried to design based on
the fundamentals of programming as I see them (and discover them as
time goes on) rather than anything pre-existing.

When your language constructs look rather different and work
slightly different too, you probably have reasons to do so.

To value your new constructs you should present them here.
This way it is possible to see, how your different looking
and working constructs work.

Since Seed7 is extensible, and therefore is able to define
new constructs easily, it would be interesting to emulate
your constructs with it.

BTW: Do you have an interpreter or compiler for your language?
IMHO: Introducing a new super-duper programming language
without the possibility to execute programs is not so great.

As a consequence I am wondering if I should plan for two versions of
the language. A full one plus another which is midway between an
existing language and my design.

I don't consider this a good idea.
I am wondering how far your language design is, when you are
thinking over such a possibility?

I wonder if others have had similar thoughts. Have you made design
changes in order to made to make a new language more familiar and
acceptable? What kind of feedback on unfamiliar characteristics did
you get from users once you had released your language?

IMHO releasing a language has little value compared to
releasing and interpreter or compiler for that language.
Developing an interpreter/compiler together with a new
language leads to a better design of both the language
and it's implementation.

Greetings Thomas Mertes

Seed7 Homepage: http://seed7.sourceforge.net
Seed7 - The extensible programming language: User defined statements
and operators, abstract data types, templates without special
syntax, OO with interfaces and multiple dispatch, statically typed,
interpreted or compiled, portable, runs under linux/unix/windows.
.

Relevant Pages

  • Re: =?ISO-8859-1?Q?Soup=E7on_of_cedilles_and_aper=E7us?=
    ... and a better programming language almost immediately. ... and the inferior design became the "de facto industry ... the committee that designed Algol 58. ...
    (alt.usage.english)
  • Re: Language design evolution vs. revolution
    ... Doubtless it is not possible to design in ... But when I started building a programming ... don't see how a practically usable language can be created without it. ... AIUI the designers started with the list syntax intending to ...
    (comp.lang.misc)
  • Re: Language design evolution vs. revolution
    ... But when I started building a programming ... don't see how a practically usable language can be created without it. ... This is how I would design and implement an algorithm. ... One of my major design goals with PILS, and one I think I achieved ...
    (comp.lang.misc)
  • Re: object system...
    ... for that you need machine language. ... isn't even as fast as other systems programming languages. ... Stroustrup's stated design goal was to enable ... all manner of elegance or abstraction can be sacrificed for speed, ...
    (comp.object)
  • Re: c++ documentation
    ... > more advanced competence in the language. ... > programming and object-oriented programming. ... There's design and design. ... My point was that the books also describe the *use* of those libraries, ...
    (comp.os.linux.development.apps)