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
It's not just a matter of being able to make mistake using feature X, but people making mistakes often enough that a C++ luminary had to write a book about it.
With great power comes great responsibility.
Taking away feature X for the sake of safety is all fine and good, but then you have a less powerful language. In other words, I will gladly take the potential pitfalls of feature X if feature X will enable me to do things (at least do them well) that other languages would allow me to do (at least do them well).
Stroustrup makes this point on his website:
http://www.research.att.com/~bs/bs_faq.html#remove-from-C++
http://www.research.att.com/~bs/bs_faq2.html#memory-leaks