Linked by Roberto J. Dohnert on Wed 28th Jul 2004 17:23 UTC
Most of us that work in the IT industry have been around for a long time. We started out in our parents basement writing code in some BASIC environment, ussually Commodore BASIC or QBASIC. Do you remember how thrilling it was? Your first program and it was something extremely basic but the point was it worked. Some of us got hooked right away and kept trying to solve problems and added more and more pushing the capabilities of whatever language we used. As we got older the environments progressed and the programming tools progressed and got more complicated.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Oh, it get's much easier. In particular, Kate + GCC lacks any sort of interactor, where you can type in code and have it execute on the fly. A good interactor remove the compilation step from the "edit, compile, debug" cycle, which makes it great for quicky trying out short, but tricky pieces of code. Any Python programmer will tell you that he has one Vim window open editing the code, and a python shell in another trying stuff out.
Now you are comparing apples to oranges. You are talking about the advantages of an interpreted, scripting language, over a compiled language like C++ (which has advantages all it's own). What you are describing is one of the purposes in life for a scripting language. A compiled language, by contrast, is better for fast executing programs, systems programming, games programming, rich GUI interfaces, etc.
Pluses and minuses to both.