I wanted to ask this in a previous thread but I thought it needed it's topic.
Would it be possible to make a compiled language as fast as c and c++, multi paradigm like c++, less complex than them both and can be used like in really complex situations like in making an OS/game engine/IDE etc.
Just wondering (may have mistakes above).
That's a really broad mission statement. Do you have experience making OSs, game engines, or IDEs? If not, how do you hope to design a language for it? What are the problems with existing languages in these domains? Are they the same accross those domains?
I just want to say that designing a good language involves a lot of decisions that aren't even being remotely considered here.
Reducing LOC count is a ridiculous metric for the strength (or quality) of a language. You guys are all arguing about standard library contents and not even anything pertaining to actual language design.
I predict that any attempt at producing a language in this thread will end in tears.
QFT. A lot of the discussion has been about the size of the standard library, which is not something a new language is not going to have any way.
@apochPiQ: that's why i started the thread. You could just talk about some things that are more important.
I can recommend two objectives you should add to your language design:
1) Facilitate features as a library. Boost show the benefits of having features that can be the implemented without a new language. But broadly, the ability to do this in existing languages is limited.
2) High level abstractions that you can peal away. This is the aim of the STL and other libaries. You describe the function, not the implemenation, but the implementation is in the same language, so it can be fine tuned/swapped out when needed.
I need to think more.
There is an old saying I've been told for years that I think applies nicely to that: "Think less, code more."
I disagree with this. Design is an important, especially with a giant project like a compiler. Code is important, to be able to test out features, but Nathan2222 is no where near ready to write any code.
You still don't even know what problem(s) you are trying to solve. Unless and until you can name a concrete area in which your language will be different, you're just scrabbling around in the dark. And unless you can argue convincingly that that language difference is an advantage, nobody will ever care.
I started building a new programming language eight years ago. It still is far from finished and lacks even the most basic tools like a debugger. Granted, I don't spend huge chunks of time on it except for rare occasions, but that should give you some idea of what you're up against. Oh, and I started with a very clear list of things I wanted to solve and why my approaches were advantageous.
I too have a compiler project on the back burner, and believe me it's no small task.
You need to be able to answer the question succinctly: Why should I use your language? You haven't done that in this thread.
Edited by King Mir, 19 February 2014 - 05:20 PM.