The files themselves look like lisp ...
Every programming language designer ends up reinventing a funny looking Lisp. Why not just use Lisp?
The files themselves look like lisp ...
Every programming language designer ends up reinventing a funny looking Lisp. Why not just use Lisp?
What does Lisp even mean? There's how many dozens of dialects of Lisp?
Certainly, there can be less code involved in Python than in Objective-C. In Python, I can create a property and assign it a value, all in 1 line of code. In Obj-C, I have to declare the property, synthesize it or override the getter method, then set it.
The other thing with Python is you don't have to declare variables. I can runand Python won't care what anobject is, as long as it has a property named "x." In that way, Python makes up for its lack of protocols - I can create a delegate property that is told to run a function, and Python only cares that that function is defined.Code:print anobject.x
I think you're hitting at one of the key features of my language:
The syntax and style is whatever you want it to be. No more complaining about people who don't follow your style rule, or about having to follow someone else's style rule. If you want camel case and your coworker wants snake case, you can each use your own style. Somebody wants no braces around one line ifs and another wants them required, while a third wants significant whitespace like Python, a fourth wants to get lost in Lisp's parentheses, and somebody else thinks a graphical diagram is best for programming? Everyone can be happy.
The files themselves look like lisp (because it's trivial to write a parser for) in a plain text editor without a plugin, but I intend to have plugins for browsers and text editors to properly convert between that syntax and whatever your preferred syntax is (stored in a system wide file). Names and comments can be localized to multiple languages, so sharing code can be easier (granted, someone will need to make a translation.)
The programs that open/save the files are themselves written in the language, so you can write a new syntax using an old one.
Those who don't study the history of programming languages (there are many textbooks on the topic) are condemned to repeat its mistakes.
Let's say you're working on an app that uses an SQL database. For some reason, you'd rather use Java's JDBC interface than any other database connection thing. However, you also like the ease with which you can create loops in Ruby. To further complicate things, there's a portion of the app that you'd like to code in Python. But, your app also does something that's best done in C++. It would be most ideal, then, to be able to use all four languages in the same project.
If you were allowed to use any of the currently-existing programming languages, and you could easily obtain whatever modules/packages/gems you need/want to use for any language, which language would you use and why?
Sounds like a disaster
I am writing a new language....
It's not compiled right now. It has an interpreter written in C. Two reasons:
1 - I've written interpreters before, but never compilers.
2 - The speed increase would just be linear - similar speed gains could be gotten by just increasing the CPU.
why are languages being created this decade hardly any better than them? I had been just sitting on my ideas with the assumption someone else would do it first, until I realized that they won't.
Sounds like a disaster
Maybe. I'm thinking something like this: use a preface to tell the program maker/interpreter what language you are using. For example, you could preface your Python code with "python::," your C code with "c::," your Ruby code with "ruby::," etc.
(This response is tailored to people reading this thread in search for a language they should learn, based on the feedback everyone here is giving)
I've been an ObjC developer for the past 3 years, and I've switched to Swift full-time. I enjoy it a lot.
If you're just starting out, don't waste your time getting into these battles over "the best language". Everyone likes different things. Instead, figure out what *you* would like to write!
If you want to make apps:
Swift for iOS
Java for Android
C# for Windows Phone
If you want to make websites:
HTML/CSS/(some) Javascript are essential for front-end
Ruby on Rails for back-end
Python + Django is another back-end possibility
Javascript + NodeJS is another back-end possibility
Elixir + Phoenix is another back-end possibility (pretty hipster)
The main point is to have fun! I enjoyed Objective-C for the past 3 years, where others despise the language. And Swift is Apple's latest, and I really love it. I never enjoyed Java when I used it in college, and I don't enjoy developing for Android as much as iOS. But if you like Android, and you start picking up Java quickly, then have at it!
It's all up to you - don't let anyone in a forum tell you your preferred language is stupid, because there's a community of millions of developers who enjoy the same language you do.
You missed something. If you're making games, for any platform, Unity is the way to go.
Also, there are many alternatives you can use for the front-end of your website, although those alternatives all compile down to JavaScript.
Unity licensing can be quite expensive.
You only need to license if you're making over $100K/year from your games. If you're making that much money, I don't think you're allowed to complain about the one time fee of $1500 for the tool that makes it all possible - it's almost certainly less than half what you paid for the hardware you're developing on.
Well, it's only the SDK with a limited feature set that's free.
The syntax and style is whatever you want it to be. No more complaining about people who don't follow your style rule, or about having to follow someone else's style rule. If you want camel case and your coworker wants snake case, you can each use your own style. Somebody wants no braces around one line ifs and another wants them required, while a third wants significant whitespace like Python, a fourth wants to get lost in Lisp's parentheses, and somebody else thinks a graphical diagram is best for programming? Everyone can be happy.
I think you just defined debugging hell.
How so? I feel you've misunderstood. Everyone sees and writes the code however they prefer - it translates between the forms for you. They're all equivalent.
Way too much time is wasted on debating over the pros/cons of different syntaxes. It doesn't matter. It's all preference.