1. Welcome! Please take a few seconds to create your free account to post threads, make some friends, remove a few ads while surfing and much more. ClutchFans has been bringing fans together to talk Houston Sports since 1996. Join us!

[help] ASP.Net vs PHP : pros and cons

Discussion in 'BBS Hangout' started by Stack24, Jan 4, 2007.

  1. Stack24

    Stack24 Member

    Joined:
    Jul 15, 2003
    Messages:
    11,766
    Likes Received:
    1,737
    hey guys I figured I would come to board to get some info on the two of these languages. the company I work for right now has all there DB stuff going through mainly php. we eventually will be expanding and incorporating more data and sending leads we get via our website to the companies that buy the leads. basically ping post system. I'm trying to figure out if we should stay php. or develop all the new sites and DB's in.
     
  2. Omer

    Omer Member

    Joined:
    Mar 25, 2006
    Messages:
    3,933
    Likes Received:
    56
    PHP/MySQL is pretty stable and should work fine.
     
  3. DrLudicrous

    DrLudicrous Member

    Joined:
    May 9, 2002
    Messages:
    3,936
    Likes Received:
    203
    Pretty much anything you can do in one you can do in the other, so in the grand scheme of things both will work. I haven't worked with either extensively but here are my thoughts.

    PHP pros:
    It's free
    Can run on multiple platforms/webservers
    Very common and has good community support

    ASP.Net pros:
    Better error handling/debugging
    Better planned/designed language
    Fully object oriented (this could be overkill if the site isn't very complex)
     
  4. bejezuz

    bejezuz Member

    Joined:
    Jun 26, 2002
    Messages:
    2,772
    Likes Received:
    69
    All of these pros can be negated by using more than just PHP in your Apache environment, say something like Ruby on Rails, Python, or (god forbid) Perl. If you need objects you could even do Java.

    I'd always go Apache and PHP, but I'm a big ol' Unix snob. Stick with what your developers know until you have a real need to go with something else. You're going to have a LOT more flexibility if you stick with Apache, both now and into the future.
     

Share This Page