On Aug 19, 3:50 PM, <a...@[EMAIL PROTECTED]
> wrote:
"if you knew OOP, you'd know you can build a far better, faster,
manageable, scalable content management system"
I happen to know OOP quite well, thank you. My first language was Java,
a language that is strictly OOP. I generally disapprove of OOP
languages because they attempt to model specifics of the real world,
and are hence very limited. I want a framework, not strictly a
management system, that can handle web applications easily. I don't see
an OOP solution as the best. I appreciate the ideals of OOP, they are
indeed great. Encapsulation, polymorphism, and inheritance are all good
ideals for software design, but to successfully implement them as they
were intended, the computer would be required to actually think. The
best OOP language I have seen (and will touch) is Ruby, because of it's
strict adherance to OOP principles. And as for an update, I am no
longer planing to store functions in the database. That was an
inherently bad idea.
The whole reason for avoiding OOP however was directly tied to RDBMSs.
I didn't want a web system that would require tweaking the tables,
adding new ones, or subtracting old ones for maintainance. That is just
a pain and provides room for errors/insecurity. I dont want the need
for new cl***** every time I want to add a new feature. I don't want to
ever touch the source code directly. That is, in fact, very much an
encapsulation ideal. I don't access the data directly, functions (or
methods) do it for me. For me, software should be flexible, extensible,
user-configurable, user-friendly, and efficient. Storing everyting in a
database is not efficient, so I cut it. Do you also reallize that the
reason I'm posting on this usenet is so that people can perhaps lend a
hand?
I was a bit overzealous with the posts earlier. I have since toned it
down, and have found someone whom I am working with. Thank you!
|
