We sell power tools and raw materials that you can use to build whatever you want. Our tools in a lot of ways are raw materials. As a company we have evolved to focus more on the developer and this transition might logically lead us to also move to a more OOP approach, so we appreciate the feedback and will definitely be considering that possibility. Our goal is customer education and successful application development, and in the case of OOP there is a real benefit for hand coding and therefor maybe a benefit to successful application development, and a real cost to exposure to the core concepts so there is a cost to educating the customer. I think we still need to weigh the pros and cons of an abstraction layer and consider the cost/benefit of doing that. I can definitely see the benefit of an OOP based architecture, particularly for some of our more advanced users, but we also really like to help newcomers understand the core technologies and sometimes that means putting it in their face rather than abstracting it. One of the things we have always liked to do is to bring those under-workings to the forefront to help people that are new to application development understand the core concepts that may be abstracted away in OOP libraries.

since it adds an abstraction layer above what is actually happening, so when you get really good at using an OOP library you might still not understand the under workings of how things are done behind the scenes. Object Oriented Programming can certainly make the code easier to read and make it a lot easier to hand-code, but as an introductory to php and coding in general it has its drawbacks. Ray Borduin: 9 Years, 6 Days, 7 Hours, 27 Minutes ago Build a responsive shopping cart + checkout

Dreamweaver cc 2017 tutorial