I think there's no difference with "C Vs. Pascal" or "Windows Vs. Linux Vs. Mac" threads, a "religious war" that doesn't benefit nobody.Originally Posted by WILL
Why not start another thread about Object Oriented Programming vs. Procedural Programming?
No signature provided yet.
Quite likely...
Come guys, why you need to be that strict? As I see it, there's no sacred war here, the proposal is to learn from different aproachs on the same problem. Any of us can come with a brilliant solution to it, don't you think? Let's work on enlightment instead of senseless fight between us.
The conversation becomes religious when people start to take things to the heart and personally. I think everyone should be aware that it's just a conversation between developers, to help each other with advice and share opinions; it is not an award/diploma/social_status/recognition contest.
In certain occasions I've mentioned Unskilled and Unaware article, but it wasn't to say that someone's stupid, but because it's an interesting read and a useful study that says that we should be careful, especially in areas where we feel more confident in. It has numerous applications, not only in programming, but in life in general: in economy, politics, sports, car driving, gaming and even women!
Procedural approach has its uses, especially in low-level frameworks, and I was not trying to prove that OOP is an answer to everything. However, while developing typical applications, starting from hello world and ending with large enterprise software, OOP is typically used. In fact, some languages would not allow you to work otherwise: C#, for instance, is very class-driven and working strictly procedural can be difficult.
I've seen people, especially those who grew in Fortran age, to incline more into procedural ways and be wary of any modern programming techniques and tools. I myself have worked in procedural and even in assembler quite a lot, but I think you shouldn't fear to leave your comfort zone and try to learn something new. Who knows, you might even have some fun.
That for sure. Some months ago, I find myself explaining the benefits to use an rdms instead of flat tables, my customer grown up working with isam files in times of mainframes, cobol and punched cards. When I show him the virtues of visual development and sql language, he was in shock. Right now (6 months after) he still wonders about why he didn't have this nice tech on his time.I've seen people, especially those who grew in Fortran age, to incline more into procedural ways and be wary of any modern programming techniques and tools. I myself have worked in procedural and even in assembler quite a lot, but I think you shouldn't fear to leave your comfort zone and try to learn something new. Who knows, you might even have some fun.
Learning is a continual process. No matter if you are 80 years old, if you stop learning, you're dead and wasting our time. Sorry if it sounds rude, truth is rude, life shows no mercy for the weak.
This non-sense is going weird.
Same level of shock happens IME when you're trying to explain "NoSQL" and "eventual consistency" to RDBMS users. ;-)
Posting Permissions
Reply With Quote
Bookmarks