Type of Language (Server-side / Client-side)

+4 Sheldon Juncker · February 4, 2015
Now, we have a name a GitHub repository, and thanks to Abdullah, we'll soon have a logo and a temporary website.

Abdullah was asking me if the language would be like CoffeeScript or TypeScript. A language like this would be translated to JavaScript.

Originally we'd planned on making a server-side web development language.

Which type of language do you think that we should create?

(Deciding this shouldn't take as long as deciding on a name. :) )

Post a Reply

Replies

- page 2
Oldest  Newest  Rating
0 Daniel Collier · February 4, 2015
i suggest you check out c++11 :) there is some neat stuff
0 Abdullah Nauman · February 4, 2015
Will we be coding a compilier from scratch, or using a framework. I think that the latter option would be better. Also how would we implement that to the web? 
+1 Sheldon Juncker · February 6, 2015
We'll probably be using a framework. Flex and Bison are amazing tools for generating compilers and interpreters.

Here's basically how it would be implemented on the web:

Model A:
--------------------
In HTML code there will be a JavaScript request for a "script.orion" file. It would look like this:
<script src="files/orion/script.o"></script>

When the browser requests the file, the orion compiler will load the file, compile the script, and give the resulting Java file to the client. This is mixing elements of interpreting and compiling. 

The browser would then use the resulting JavaScript file and would never know that it was compiled from Orion.
--------------------


Model B:
--------------------
In HTML, the browser will request a "script.js" file like so:
<script src="files/js/script.js"></script>

Now there will also be a file on the server called "script.orion". When this script is compiled it will create the "script.js" file which will be used by the browser. This is traditional compiling as compilation and code generation only happens once. 
--------------------

Each model has its advantages and disadvantages.

Does that explanation make sense?
0 Abdullah Nauman · February 6, 2015
So basically, we are writing a compilier that will take our language and compile it to JS code. But then we are basically limited to the limitations of JS right. All we can do is make a new syntax.Please correct me if I am wrong. 
0 Sheldon Juncker · February 6, 2015
Yes, you are correct. But also, C++ cannot do anything that Assembly can't. This is the same that Typescript and Coffeescript are doing.
0 Daniel Collier · February 6, 2015
Won't the first option be a lot slower .
+1 Sheldon Juncker · February 6, 2015
Probably by a couple hundredths of a second. :)  

The second option is better performance-wise but it is easier on the developer as code does not have to be manually compiled before being tested.
0 Abdullah Nauman · February 6, 2015
Ok thanks! I'll go do some research on flex, and bison! 
+1 Sheldon Juncker · February 8, 2015
So, is everyone wanting to make a Typescript / Coffeescript type language? Speak now, or forever hold your peace. 
+1 Daniel Collier · February 8, 2015
i agreeee ^ a language that is converted to js would be easier to accomplish 

Orion Programming Language Project

14 followers
About

This forum is for the users on TNB who are working on developing the Orion programming language. Anyone is welcome to take part in this project. More information will be posted soon.

Links
Moderators