Hockey wrote:Thats the problem with PHP...because it doesn't take long to get up to speed in developing software, there are an amazing amount of poorly written classes, libraries, etc...
Scenario may be different with different people... live with knowing guys, get good exposure to finer part of things and improve yourself and the way you code. stay holed up and you lag behind with minimal chances of any kinda improvement.
Hockey wrote:I would use someone else authentication library, but they are all either incomplete, dependant on one thing or another or lack flexibility...
for this I would like to say, when you are looking at others' code, you gotta kee pin mind that 90% of the time, such libraries are implemented as modules which are built around certain core classes of that library. Anywhere I have seen, I see vast no. of modules that are dependant on one or the other. Even PEAR classes are dependant on PEAR base system.
If you were to think my way, my way of true portable code will be a peice of code I can put anywhere and it works without any/little modifications. Vut then, there are some trade-offs and everything can't we the way we want. we can make that upto some degree but if we very carefully take care of that while coding. often while coding libraries we implement certain level of abstraction so that coding becomes modular. But that very thing makes the classes dependant on the abstraction layer. Without SQL_Generator class, I can't use the USER class to do the work for me. I has to have that class. so that's one side of the thing.
the flip side is, if we make it truly portable, one size fits all thing, then all it ultimately becomes is bunch of code which works if you know how. which grows with the features and complexity involved. but which you can put anywhere and it does the work for you. without any glitch, without any unwanted dependencies.
So what says you
