Phoenix Network Forums

Inspired by a previous thread about beginning languages, I began thinking about Python versus the rest of the programming language world.

Recently, one of my Computer Science professors said he thinks that powerful high-level languages, such as Python, will become the norm for most programs written in the future. He also said that C++ and other such compiled languages do have their place, which is in environments where it is either impossible or very impracticle to use an interpreted language, and where speed and/or efficiency is a necessity. Also, he said that as computers get faster and faster, the need for ultra efficient programs for most of the computer world will diminish. Additionally, the main cost factor in making computer products and software today is the programmers, and by using interpreted languages with which programs can be rapidly developed, costs would be greatly reduced, as well as completion times.

I sort of agree with this statement. I do not think that C or C++ will ever go away, if only for embedded systems. I do disagree that Python will become the majority though, but I agree the use of such interpreted languages will increase over the next few years, especially in open source software.

By using Python, programmers can focus on the functionality of the program at hand, without spending too much time developing or learning how to implement different data structures or data formatting mechanisms.

As for myself, I learned C++ in high school, PHP and other web languages on my own, then Python and lots more C++ in College, as well as the related Jython language.

So, my fellow programmers, what do you think of this statements, and does this bode well for us and/or the industry?

I do agree with you that programs will need to be written on the fly, however i think portability will become and already is more of a factor. That is why java grew so fast, its portability between computers, operating systems, and web browsers.

At least for non-free products, interpreted languages are never going to be used. The reason is simple: interpreted languages imply revealing the source code. Even byte-code can be reverse-engineerd easily. However, for open source software it's used where appropriate. Most programs still come in classic C or C++, and that won't change until we have quantum computers.

Currently we have two layers of functionality: the CPU and the op-code. Maybe sometime a third layer, the byte-code layer, will get it's place, but it's too early. For now scripting languages should be used where appropriate, nothing more, nothing less.

I agree with stupergenius's prof. Today, you can see how interpreted languages have a bigger mindshare than they did even five years ago. As these languages mature and get their standard set of supporting libraries, they become very attractive alternatives to compiled languages.

The interpreted languages offer a very quick development time compared to compiled languages.

well i do agree that python has the potential to become the most widely used programming language. The mere simplicity of the language hides it's immense power to do literally anything that can be done under the sun.
And though being an interpreted language it is faster than similar languages like Java. And the best thing is it's free. free as in "freedom". Integrate it with other FLOSS software and you've got something which can put any properietary app. on the run.

And the fact that it's free gives it all the more scope for development.

I believe python will live on as it has. I would not think that any are going the better than the other at the moment cause they are used in different areas. Ive done most lanaguages when it comes to programming and I still think that depending on what you are going to do will be the choice of the language you chose. I would do perl if I was in Linux/Unix or some other script kind of products. Even if you can do perl in Windows too I would not chose that. You can even compile your perl programes into EXE:s and hide your code. Still I wouldnt chose perl since the documentation of the WIN32:GUI package are too much undocumented and I would not want to sit in the MS-DOS prompt. Feels like very old to things. I would ratcher choose visual c++ or csharp. Mostly Csharp since I havent yet seen the limitations of it if there are any. So this is what I have to say about this.

Speaking of portability...
I think it is a problem, how to hide the source, so scripting languages might not have a future in business.
Bytecodes are faster and do not need to publish the source (even though it's easy to get it back) but probably the .NET-like attempts are a true potential.
If I'm correct, the .NET provides binary-portability... this solves quite a lot of problems. (don't think I'm partial, I prefer linux and java, it's just my opinion )

kl223
(my english is bad, sorry)

none, id rather c better than nefing but i would choose python

there are a many applications where interpretive languages will always be too slow. 2 primary examples (there are many others)

1) Live music performance - yes I have tried it with an interpreted language - and it was dismal. I kind of knew it would be before hand, but I just needed something quick to fulfill a specific role. They just don't always seem to manage synthesising complex waveforms whilst spitting it out continuously at 44,100 - 96,000 samples per second per channel (2 to 8 in many cases). With sound even the most minor pause will result in an audible error.

2) Games - games drive computer technology in many aspects. I don't think we will ever see the games industry moving over to python

If you talk to most seasoned C/C++ programmers they will tell you to use a diffrent language more specific to your task. I had a really good link, ah wait found it with a bit of googling. IT basically says c++ was created to make it hard to flood the market with programmers.

http://www.edu-cyberpg.com/Technology/c++.html

~c

I think that the line between interperated languages and compiled languages s getting blured. Python is compiled (rather tokenized) before being executed and the pre-compiled scripts are saved. In this sense it works like a just-in-time (JIT) compiler. You can distribute the compiled .pyo files without the acompaning .py source files.

selket wrote:You can distribute the compiled .pyo files without the acompaning .py source files.

mm_freak wrote:interpreted languages imply revealing the source code. Even byte-code can be reverse-engineerd easily.

btw. PERL and TCL also support binary output. TCL also uses a caching system to cache already compiled stuff.

But my opinion is still, for anything else than a few simple calculations and striong operations you shouldnt use a resources ineffeicient script, but rather a "real" language. C/C++ is preferable because of good portability (with a few preprozessor settings you can compile same code from 32bit windows up to 64bit BSD with the same code). Many companies (and open source communities) do now have trouble converting their assember code for 64bit systems. And honestly... if you are expierient with C you will not need much more effort to write in C, if you stick to proper code formating including chosing wise data types.

Python has emense power in the programming world as is quite flexible. We already have the language D which is combining the power of C and C++ . New languages are continously apearing, one that has caught me by amazment is 'Croma' a language soon to provide less hassle to the web development world.
It will take less lines of code to do the same task in php. i read an article on the apple site recently regarding its power. It has not yet been released, but will be open-source in time.

Well I think everyone could start learning with an easy language like Python which is very powerfull and selfexplaining.
But I think it is important to look how the CPU and memory allocation works afterall, so python is not all. Everyone should look at languages like C, C++ or even asm, to understand what the PC does

mm_freak wrote:At least for non-free products, interpreted languages are never going to be used.

Being interpreted or not does not have to be a property of the language. See e.g. the different implementations of the Scheme programming lanugage, where are both kinds: interpreted and compiled. But even the compiled ones use to come with an additional interpreter. Then you have both advantages: develop in fast cycles using the interpreter, but compile for optimization and delivery.

Thomas