> >"but it certainly seems to have you pointing fingers and >yelling at anything you can to apportion blame." >
This was a specific reply to Scotts post. I should probably have made that clear in the first place. >From my experience, people who do this usually do it to >justify themselves >to their employer, or who ever it is that they are complaining >to try and >big note them selves as to say "this is crap. my system is >soo much better >so I am going to use mine" rather then working with what's >there, developing >a solution to the problem at hand and getting on with the job. I think a lot of people do it out of frustration at the situation they find themselves in. Their frustration and anger often need to get vented so they can start to focus and get on with the task at hand. In Scott's case, he's been ranting and venting for the last few weeks and I'm just getting a bit tired of it. > >Personally I have seen allot of problems being posted in >cfaussie, and most >of them are problems that don't need to be problems cause >people try to be >tricky make problems more involved than they need to be. > Yes, the problem is often exacerbated by approaching a problem from taking the wrong approach in the first place. That tends to cloud your ability to see the problem with fresh eyes which can lead to posts to mailing lists where things that were a problem to the poster didn't necessarily need to be a problem when seen with the fresh eyes of the rest of the mailing list members. That's half the point of mailing lists IMO. >As they say, the most effective solutions are usually the simplest. Yep, that's been my experience too. > >So, here is my take on OOP > >Although Coldfusion is on a JAVA base, it is JAVA that is an >OOP language, >where as Coldfusion is not. Macromedia developed Coldfusion as a <TAG> >based language so that from a development perspective, all the grunt >happened behind the scenes, and we, as developers didn't have >to worry about >that side of things as could concentrate on doing what we do, which is >develop. I think the argument you're proposing here is procedural code VS object oriented code. There was some debate about that 15 years ago or so, but nowadays there are very few people who are seriously arguing that procecdural code is better than object oriented code when you have the choice. Up until CFMX there was no reasonable way to write ColdFusion code in an object oriented way so procedural code dominated. Going back 15 years or so there were a lot of C developers around who were starting to write C++ code. They tended to be very much of a procedural coding mindset and wrote a huge amount of procedural C++ code. Over time, the realization dawned on most of them that their programs would be a lot easier to write, debug and maintain if they wrote C++ in an object way instead. I believe that is where we will go with ColdFusion. There will always be a number of die-hard ColdFusion programmers who insist on following the procedural route because they don't have the time or inclination to learn how to do it the OO way, but over time, more and more ColdFusion developers will realize the same things that C++ developers realized a long time ago. > >I still don't know why this OOP thread keeps coming up when >ColdFusion is >NOT an OOP language. Although you may implement some OOP style of >developing your applications, why do people still harp about >Coldfusion not >doing things that OOP languages can do. Well here is your answer. >Coldfusion doesn't do allot of things accustom to OOP >development cause it >isn't an OOP language! Simple I know, but that's the truth of it. > ColdFusion is perfectly capable of supporting some of the core principles of OO programming. The main issue is the lack of interfaces, but that is something that you can work around. >As many of the JAVA guy on here have said, if your gonna try >develop in OOP, >go learn OOP, but in the end you wont be able to develop Coldfusion >applications in OOP, but you will be able to use the >fundamentals of OOP and >its structure to help better define your application >frameworks and help you >more understand application workflows. > I think you're mis-quoting there. The sentiment is more along the lines of: Don't try to learn OOP using only ColdFusion because there are a few things that don't work 100% OO in ColdFusion. Once you understand how OO programming works you shouldn't have too much trouble applying it to ColdFusion. >If you want to develop in OOP, then develop in JAVA or something. I flat out disagree with this. Spike --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
