Linked by MOS6510 on Thu 10th Jan 2013 23:25 UTC
"For years I've tried my damnedest to get away from C. Too simple, too many details to manage, too old and crufty, too low level. I've had intense and torrid love affairs with Java, C++, and Erlang. I've built things I'm proud of with all of them, and yet each has broken my heart. They've made promises they couldn't keep, created cultures that focus on the wrong things, and made devastating tradeoffs that eventually make you suffer painfully. And I keep crawling back to C."
Thread beginning with comment 548454
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-07-26
I sympathize. I have found that prototyping stuff quasi interactively in python and then porting it over to C/C++ can be a very productive way of programming.
Exactly.
Previous generations might have prototyped on paper or a chalk board before "finalizing" the C code.
Thats from a time where it made sense to plan ahead because you might be using punch cards or had to wait your turn for computer time.
Python makes a great prototyping language because it has been described as executable pseudo-code. Not too low or high level.
When I prototype in Python I'm doing the same thing, I'm just using a text editor rather than pad of paper.
Member since:
2009-03-17
I sympathize. I have found that prototyping stuff quasi interactively in python and then porting it over to C/C++ can be a very productive way of programming.
Edited 2013-01-11 22:23 UTC