How do people create new programming languages?

[Tasuma]

I was always curious on how people did this? Do they use an already existing code to help create a new one? Is it something in the source code of an operating system that allows them too? 

[Prastupok]

Assembly language... telling the machine language to tell the actual hardware what to do

[minibois]

I was always curious on how people did this? Do they use an already existing code to help create a new one? Is it something in the source code of an operating system that allows them too? 

I know they use the language 'C', but not sure what more.

[Arwanell]

more than this i wonder, how was the first programming/developing software made.

You make programms with ex. Visual Studio or something like that, but how they made first software like this?

[Johannes_Lazor]

A programming language is what is between the binary code and what you want to be displayed.

"01101100 01110110 01101100 00100000 00110101 00100000 01101101 01100001 01100111 01101001 01101011 01100001 01110010 01110000"
Is translated to lvl5 magicarp, But first it has to go through a decoder, The other way around it needs a Encoder, A engine is(usually) both a Encoder and a Decoder.

[paprikman]

All the new programming languages are just a bunch of 'aliases' for their compiller, created with an assembler.

[zonahbear]

I know they use the language 'C', but not sure what more.

 

or assembly

[madknight3]

You create a new programming language by defining all its rules. What will the syntax and semantics be? What is allowed and what isn't? Then to make that programming language useful, you'll need to build a compiler/interpreter for it. Once you have those two things in place, you'll be able to write and run programs with your new language.

 

While there may be some restrictions on the languages you can use to build your compiler, I expect you have plenty of choice (Assembly, C, C++, C#, Java, Python, Ruby, etc). Obviously there are pros and cons to each of them and the languages you use will depend on your goals. If you're just doing a personal project for fun or just want to get a working version finished more quickly, then efficiency might not be a high priority. In that case you can just choose your favourite language which may or may not be amongst the fastest options out there. If you're working on a version that'll be ready for release, you might use a different language where speed and efficiency is a large goal. There's also the option to use different languages for different parts of the compiler.

[SIGSEGV]

In the olden days they wrote poked binary into punch cards, this is stuff the circuitry can understand (so say if you gave it 1001 electricity would be sent on those lines and would go through a load of logic gates then spit out an answer), they used that to make assemblers which translated assembly code into the binary representation directly (kind of like a word by word translator) then they kept making higher and higher level programming languages.

[MatazaNZ]

For a tiny bit of humour, I found this

 

But seriously, it takes a lot to write a language. Usually based on machine code, you then create keywords, classes and such. From there, you build low level functions, and build those into high level functions. You would also need a compiler that turns it into machine code, and makes it an executable file. Not to mention specifications and documentation.