Dynamic websites in PHP
- Thread starter DJMK4
- Start date
yeah i'd say either ASP or PHP...
I heard that ASP is what a lot of jobs search for as .Net is getting popular and PHP is good cause of all the opensource / highly available libraries of code on the net.
But the thing I said about ASP was from one person... I would like to hear what other people here have to say tbh
I'm using PHP and MySQL to make my project game in... i'd say yeah start with PHP
I heard that ASP is what a lot of jobs search for as .Net is getting popular and PHP is good cause of all the opensource / highly available libraries of code on the net.
But the thing I said about ASP was from one person... I would like to hear what other people here have to say tbh
I'm using PHP and MySQL to make my project game in... i'd say yeah start with PHP 
Soldato
- Joined
- 27 Dec 2005
- Posts
- 17,316
- Location
- Bristol
On a basic level then PHP is free, ASP isn't. From an amateur level that's the determining factor really...
Associate
- Joined
- 5 Feb 2009
- Posts
- 424
For a start you can code up your own classes which you can then use in Windows Applications if required. In an enterprise environment this sort of thing is a godsend. Try having to create your business rules over and over every time you begin a new application. i.e. the .NET framework is the same (well, similar) if you are writing a windows app or a web app.
ASP.net has a great web forms framework. It's like templating, on roids. Just fantastic.
You can use a lot of languages to create ASP.NET web controls - c++, c#, vb.net, COBOL. It's all possible. Maybe even PHP one day! In an enterprise, where you may have to utilise staff members with a skillset which specialises in languages other than c# or vb.net, this is also useful. I can write part of my ASP.net application in VB.net and it will interface just nicely with part of the application that was written by someone else in another language.
Dev environments for ASP.net are better. If you can afford it, Visual Studio .NET is the dogs balls. Real top class tuff. Even the free Microsoft Web Matrix is supposedly pretty good (better than anything you can get free for developing PHP). The dev environment allows you to debug properly (stepping through code and viewing variable values etc) and it has intellisense, of course - always useful.
ASP.net has a great web forms framework. It's like templating, on roids. Just fantastic.
You can use a lot of languages to create ASP.NET web controls - c++, c#, vb.net, COBOL. It's all possible. Maybe even PHP one day! In an enterprise, where you may have to utilise staff members with a skillset which specialises in languages other than c# or vb.net, this is also useful. I can write part of my ASP.net application in VB.net and it will interface just nicely with part of the application that was written by someone else in another language.
Dev environments for ASP.net are better. If you can afford it, Visual Studio .NET is the dogs balls. Real top class tuff. Even the free Microsoft Web Matrix is supposedly pretty good (better than anything you can get free for developing PHP). The dev environment allows you to debug properly (stepping through code and viewing variable values etc) and it has intellisense, of course - always useful.
Twice as archaic then?
I've coded in php, it's not my prefered language I prefer something like python and Django. I have seen many ameuters using straight php without a framework and get hacked it in 5 seconds because they didn't sercure it. It also reminds me of perl 
Python and Django mainly does all the crap for you and it much better language with more syntatic sugar.
Python and Django mainly does all the crap for you and it much better language with more syntatic sugar.
I'm currently learning the zend framework which I am finding interesting, it's not something you want to jump straight into though. You need some decent background knowledge of PHP or another OOP language such as Java. I think frameworks are a good place to start once you have grasped the language as they put you in a certain mindset about how to structure an application. I know some people don't like frameworks and prefer to write their own but I don't think you can properly attempt that until you have worked with an existing one. Overall I don't think it matters which language you choose, either one will teach you the same sort of concepts.
How is it? Am thinking about looking at Zend. Just messing a bit with CakePHP atm.
It seems okay so far, it is my first framework in PHP and it seems to require a fair bit of infrastructure setup before you get going. I'm using it for my final year project at uni as it offers all of the features I need. The main reason I decided to use Zend was because I have a book which covers it in quite good detail with a running scenario of a blogging system.
Although PHP is open source, it has a large active community which is there to support users of the language; ASP.NET is a product of Microsoft meaning that there is a large amount of online documentation and other community forums where you can get support.
Both these frameworks are good to use as per your requirements. CakePHP is suitable for developers new to MVC and those who require stricter conventions. ZF is a choice for those who need better control over the application design and built-in support for renowned Web services. Both the frameworks are developing fast and the choice is entirely yours.
I was gonna say, considering the rigorous complexity of J2EE patterns (filters -> controllers -> actions -> (DTO's) business delegates -> business service -> DAOs and back again) MVC feels fairly noddy.
But I am just *so* tired of programming object notation and dumping it to a database!!
But I am just *so* tired of programming object notation and dumping it to a database!!
If this is the case, then why does anyone bother with PHP? despite it being free? if it isn't capable of doing any of the stuff?
Even though PHP may be free, surely you get paid more doing ASP than PHP?
A) Not everyone is as materialistic as you.
B) Comparing PHP to .NET is like comparing Cheddar to Roquefort. One is cheese, and is good at being cheese, the other is expensive cheese but may be more to your prefernce of specific taste, great on crackers with a glass of wine - but crap on toast..
and don't be fooled by the "selling point" of ASP's framework. Yes, it has one. Yes, it is robust. No, it is not 'good'. It is very old fashioned and really needs updating, but alas.. Microsoft.
B) Comparing PHP to .NET is like comparing Cheddar to Roquefort. One is cheese, and is good at being cheese, the other is expensive cheese but may be more to your prefernce of specific taste, great on crackers with a glass of wine - but crap on toast..
and don't be fooled by the "selling point" of ASP's framework. Yes, it has one. Yes, it is robust. No, it is not 'good'. It is very old fashioned and really needs updating, but alas.. Microsoft.
Last edited:
Soldato
- Joined
- 12 Apr 2004
- Posts
- 11,788
- Location
- Somewhere
I have to say I agree with this. I haven't used ASP.NET much, but I'm not a fan of its architecture. It tries to emulate client-side Windows Forms behaviour (which is, in itself, outdated) in a web application, which is rather backwards in my opinion.