Posted: Wed Aug 18, 2004 4:37 pm
I couldn't agree more. I'm currently using their class to make Excel spreadsheets and it suddenly just stopped. No error or anthing. Heed those words!!!McGruff wrote:avoid PEAR like the plague
A community of PHP developers offering assistance, advice, discussion, and friendship.
http://forums.devnetwork.net/
I couldn't agree more. I'm currently using their class to make Excel spreadsheets and it suddenly just stopped. No error or anthing. Heed those words!!!McGruff wrote:avoid PEAR like the plague
PHP does have a massive user base, unmatched for simple web dev. However, it is just a language, and for speedy development, you would want a framework to go with the language. It takes alot of time to make one yourself - so the advantage of ASP.NET over PHP is that it has the huge framework for rapid development, whereas php has none. The disadvantage of ASP.NET is you have to spend some time learning the framework, whereas you can use php for simple things almost immediately - hence its unmatched popularity.pickle wrote:1) PHP.
It's got a much wider support base. If you have any problems, it's much easier to get help (just look at this forum).
It's open source - cheaper to run/upgrade
I'm not sure, but I think it's more powerful in that it has more built-in, useful functions. It has many tie-ins with other libraries as well.
(Honestly, I don't think anyone here will recommend ASP over PHP - this is a PHP forum after all).
You make a compelling point.pickle wrote:5) UML is the devil*.
MySql is a piece of crap. Only use it if you are making something simple. And even then, use anything else if you have the option. It doesn't support much in terms of functionality. Most obviously it doesnt support foreign keys, and I think it only recently built support for views. It is very much feature-deficient. And on top of that, it's not even free for commercial use. The only advantage I can see for mysql is that if youv'e used it before, you don't have to spend time messing around learning some extra things by switching dbms's. Whether this is reason enough to stick with mysql is questionable.pickle wrote:6) MySQL is certainly one of the easiest DB's to administer, from what I've worked on.
Postgres is much more difficult, though that may just be because I don't have as much experience with Postgres.
I'f you've got the resources for Oracle, I'd be tempted to use it. At the very least, you can put on your resume that you've worked with Oracle. However, I don't really think the power of Oracle is needed for a website - really only for organizational intranets and online stores and the ilk. Regardless of which one you pick, I strongly recommend creating a DB abstraction layer so if you decide to change your mind later, you only have to change one class, not every file that accesses the DB.