New Programming Language

So, /prog/

You are in charge of developing a new programming language. You are not the one who has to implement it, you just have to tell the codemonkies what you want.

Some things to think about:

- syntax style
- paradigm
- garbage collection or not
- vm or compiled
- type system
- special features of the compiler or language

>>25
typically
{{weasel}}

You fail to make the distinction between a language and an implementation of it.
Don't worry, it's a common beginner mistake, made for instance by Guido Opossum, Kisama Matsumoto and Larry Thrall.
Anyways, I was about to start coding, and then the bastard beside me goes "I want to make a scripting language".
Who in the world wants to make an interpreter with ad-hoc semantics nowadays, you moron?
I want to ask him, "do you REALLY want to make a shitty interpreter?"
I want to interrogate him. I want to interrogate him for roughly an hour.
Are you sure you don't just want to try saying "scripting language"?
Coming from a PL veteran such as myself, the latest trend among us vets is this, embedded DSLs.
That's right, embedded DSLs. That is the vet's way of coding.
Embedded DSLs mean more macros than functions. But on the other hand you don't reinvent the wheel. This is the key.
And then, it's fast. This is unbeatable.
However, if you do this then there is danger that you'll be marked by the employers from next time on; it's a double-edged sword.
I can't recommend it to amateurs.
What this all really means, though, is that you, >>25, should just stick with today's special.