PHP vs. ASP vs. ASP.NET
-
Being a neverending argument I just thought this part of the toolbox discussion deserved its own thread ;P I really can't comment on ASP.NET since i've never dealt with it, but i've looked at scripts and it seems a lot more functional than ASP classic. With ASP classic itself i'd say it's usable since i as a web dev can count on seeing it on most Windows servers when they don't have anything else installed and get the job done (now that i know enough of it). I find PERL to be more comfortable than VBScript when i'm working in ASP classic but i rarely see a PERL engine installed, so i often have only one way to go. I've worked with PERL before and that's part of the reason why I prefer PHP. I often find myself reverting to the PHP way of declaring a variable ($var_name) under ASP and then having to go back and correct it... I doubt it'll be an easy transition if i went into ASP.NET so i'm not really sure if i will, but anyways... Roswell:rose:
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CAPHP is fine. i never really got the hang of Perl. C#/ASP.Net is very nice. i'm so happy MS lets IIS execute Javascript on the server side, in situations where ASP.Net can't go, because ASP/VBScript is horrid.
-
Rocky Moore wrote:
One main key to any development is to use tools you know.
Or to recognise the tools you know as inadequate, and factor in time to learn new ones.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
Yep, good point!
Rocky <>< Latest Code Blog Post: ASP.NET HttpException - Cannot use leading "..".. Latest Tech Blog Post: Replacing Vista System HD & New things learned!
-
PHP is fine. i never really got the hang of Perl. C#/ASP.Net is very nice. i'm so happy MS lets IIS execute Javascript on the server side, in situations where ASP.Net can't go, because ASP/VBScript is horrid.
Chris Losinger wrote:
because ASP/VBScript is horrid.
That is sure the truth, was so glad when .NET came along!
Rocky <>< Latest Code Blog Post: ASP.NET HttpException - Cannot use leading "..".. Latest Tech Blog Post: Replacing Vista System HD & New things learned!
-
Being a neverending argument I just thought this part of the toolbox discussion deserved its own thread ;P I really can't comment on ASP.NET since i've never dealt with it, but i've looked at scripts and it seems a lot more functional than ASP classic. With ASP classic itself i'd say it's usable since i as a web dev can count on seeing it on most Windows servers when they don't have anything else installed and get the job done (now that i know enough of it). I find PERL to be more comfortable than VBScript when i'm working in ASP classic but i rarely see a PERL engine installed, so i often have only one way to go. I've worked with PERL before and that's part of the reason why I prefer PHP. I often find myself reverting to the PHP way of declaring a variable ($var_name) under ASP and then having to go back and correct it... I doubt it'll be an easy transition if i went into ASP.NET so i'm not really sure if i will, but anyways... Roswell:rose:
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CA -
ASP.NET is good, and I think it's easy to learn and use.
========================================= 中国，昆明
I think that ASP is just crap. It’s not as flexible and fast as PHP. In ASP you use an ODBC connection which isn’t always stable. Also, some internet sites based on ASP are not working on anything else but Internet Explorer, which is a bad thing. PHP is an open source, with a worldwide spread community while ASP is just a Microsoft thing and like I told you before: it isn’t as flexible as PHP. In ASP you even have to program form buttons, because everything is an object in ASP. Writing a ‘hello world’ script in PHP is very short :
”; ?> While in ASP the same script would be : <%@ Page Language="C#" Debug="true" %> <% Response.Write("Hello world:"); %> And it becomes more complicated when using variables etc.
-
I think that ASP is just crap. It’s not as flexible and fast as PHP. In ASP you use an ODBC connection which isn’t always stable. Also, some internet sites based on ASP are not working on anything else but Internet Explorer, which is a bad thing. PHP is an open source, with a worldwide spread community while ASP is just a Microsoft thing and like I told you before: it isn’t as flexible as PHP. In ASP you even have to program form buttons, because everything is an object in ASP. Writing a ‘hello world’ script in PHP is very short :
”; ?> While in ASP the same script would be : <%@ Page Language="C#" Debug="true" %> <% Response.Write("Hello world:"); %> And it becomes more complicated when using variables etc.
I went from doing almost no web development, to bieng the companies main web guy, and all we use is ASP.NET/c#. I picked up the basics in a matter of weeks and could do just about anything you wanted in it before we hired a new web dev(who also hadnt used ASP.NET, but had used PHP and PERL) and he picked it up just as quickly as i did, and likes ASP a lot better than PHP and PERL. i had to convert a php site to run w/ our databases and on our servers once, and while i picked up what little php i had to use, it just seemed like more of a mess than ASP, of course we use code behind pages for everything and almost never have any inline script. it may not be as fast, but i've never had a problem w/ our database connection, and if a site doesnt work on anything but IE thats the designers problem, our site doesnt work in opera or safari, but FireFox and IE display it fine.
-
I think that ASP is just crap. It’s not as flexible and fast as PHP. In ASP you use an ODBC connection which isn’t always stable. Also, some internet sites based on ASP are not working on anything else but Internet Explorer, which is a bad thing. PHP is an open source, with a worldwide spread community while ASP is just a Microsoft thing and like I told you before: it isn’t as flexible as PHP. In ASP you even have to program form buttons, because everything is an object in ASP. Writing a ‘hello world’ script in PHP is very short :
”; ?> While in ASP the same script would be : <%@ Page Language="C#" Debug="true" %> <% Response.Write("Hello world:"); %> And it becomes more complicated when using variables etc.
I don't think asp may be crap (neither php) I'd like to know in which way is php more flexible since you have to declare everything in a raw html file instead of thinking as objects and separate all the logic into layers in order to enhance your productivity. the Internet Explorer issue is not an asp.net problem (because all the content is rendered as the usual html) but a lack of css design. A lot a asp.net developers point to firefox to test their pages. Although microsoft is an propietary software company, .net is a free distribution framework, and also their express enviroments (Visual Studio express) so you can develop an app without worrying about it. and finally, that's the advantage why most developers go for asp.net: the Object Oriented programing. if you think everything as objects, everything becomes more intuitive(it's like talking!). Using variables allows you to know what are you working on imho. regards
O.o rodri
-
Being a neverending argument I just thought this part of the toolbox discussion deserved its own thread ;P I really can't comment on ASP.NET since i've never dealt with it, but i've looked at scripts and it seems a lot more functional than ASP classic. With ASP classic itself i'd say it's usable since i as a web dev can count on seeing it on most Windows servers when they don't have anything else installed and get the job done (now that i know enough of it). I find PERL to be more comfortable than VBScript when i'm working in ASP classic but i rarely see a PERL engine installed, so i often have only one way to go. I've worked with PERL before and that's part of the reason why I prefer PHP. I often find myself reverting to the PHP way of declaring a variable ($var_name) under ASP and then having to go back and correct it... I doubt it'll be an easy transition if i went into ASP.NET so i'm not really sure if i will, but anyways... Roswell:rose:
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CAI have used all three of these languages at one point or another. PHP happens to be my favorite simply because, combined with C++, I can do anything with it. ASP.net is a huge step forward in terms of speed and functionality. I am comfortable using PHP and ASP.NET, But PHP would definitely be a better skill to learn first as a developer. It can be used on almost any web server that you will work on and is straight forward whenever you need it to be. Also In terms of security a Apache/PHP solution will always beat a IIS/ASP one. (Please note: I am not insinuating that either languages are better built in terms of security and I understand that the reason Microsoft products get hacked a lot is because they happen to piss off a lot of programmers who want to bring nothing but pain and suffering to the people who killed Word Perfect.) Disclaimer: The writer of this post (me) in no way intended to begin a Flame and could I please not have my Linux servers cracked so you can prove a point.
Brad Australian Save the Glass House (Fill in the complaint form to the ABC) Glass House Home Page (May as well get hooked while you still can)
-
I think that ASP is just crap. It’s not as flexible and fast as PHP. In ASP you use an ODBC connection which isn’t always stable. Also, some internet sites based on ASP are not working on anything else but Internet Explorer, which is a bad thing. PHP is an open source, with a worldwide spread community while ASP is just a Microsoft thing and like I told you before: it isn’t as flexible as PHP. In ASP you even have to program form buttons, because everything is an object in ASP. Writing a ‘hello world’ script in PHP is very short :
”; ?> While in ASP the same script would be : <%@ Page Language="C#" Debug="true" %> <% Response.Write("Hello world:"); %> And it becomes more complicated when using variables etc.
cynthia_1968 wrote:
”; ?> While in ASP the same script would be : <%@ Page Language="C#" Debug="true" %> <% Response.Write("Hello world:
"); %>
Perhaps it is my own ignorance, but I was under the impression that in php you had to include html tags as well, making this an inflated argument against ASP. "echo" and "Response.Write" are essentially the same, in practice, with their obvious syntactical differences. There are a whole slue of other things that do along with Response that make the relative length of the command justifiable. While I respect your opinion of ASP being crap I wouldn't pin the not-working-on-anything-other-than-IE on the development environment, that's just poor coding. I see stuff written in php that only works on firefox. In almost every instance it's because of javascript, and the developer's lack of finding a cross-browser way of accomplishing the same feat. Moreover, I don't care about flexibility. In my full time job I spend about 50% of my time in COBOL(with the remaining half in ASP/VBScript), so when I get into an environment with any objects or being able to write a function for anything that I have done more than once, it's all gravy to me. I don't think any one development language is any better than another, it simply depends on what you are trying to do and how familiar you are with it. That being said, I am still learning php and ASP.NET because I am a new programmer and still can't get enough of learning new things.
"If you really want something in this life, you have to work for it. Now, quiet! They're about to announce the lottery numbers..." - Homer Simpson
-
I think that ASP is just crap. It’s not as flexible and fast as PHP. In ASP you use an ODBC connection which isn’t always stable. Also, some internet sites based on ASP are not working on anything else but Internet Explorer, which is a bad thing. PHP is an open source, with a worldwide spread community while ASP is just a Microsoft thing and like I told you before: it isn’t as flexible as PHP. In ASP you even have to program form buttons, because everything is an object in ASP. Writing a ‘hello world’ script in PHP is very short :
”; ?> While in ASP the same script would be : <%@ Page Language="C#" Debug="true" %> <% Response.Write("Hello world:"); %> And it becomes more complicated when using variables etc.
In fact, It seems that example is kind of poorly formulated. The equivalent in ASP would be:
<%="Hello world <br><br>"%>So, in fact, the ASP code even has less characters... and don't get me wrong, I despise classic ASP (although I have done my share of coding for that platform), but just as another poster said, the examples are essentially the same, with their obvious syntactical differences. Also I disagree with the "opensource = great software" principle. Sometimes it is, but sometimes it's just a pain in the ass. And last, ASP is a server based language. If some ASP-based website runs only on IE, that's because the developers made it so (maybe by poor design and developing, maybe they just didn't care). ASP does not, per-se, force any web browser. So, my position is that before making any statements, first do a little research. If you don't like ASP (as I don't either), you are in your full rights, but don't manipulate the data to make it appear even worse (it's not necessary, it manages to be very bad on it's own). Finally, just to answer the original question, between ASP, ASP.Net and PHP, my ranking would be 1-ASP.Net (it's one of the best platforms for web-based apps), 2-PHP (it's very nice and has support for lots of systems), 3-ASP (use it only if you have no other option).Enhance the trance
-
RoswellNX wrote:
really can't comment on ASP.NET since i've never dealt with it
One main key to any development is to use tools you know.
RoswellNX wrote:
I doubt it'll be an easy transition if i went into ASP.NET so i'm not really sure if i will, but anyways...
There is no other way to put than a drastic difference in development. ASP classic and PHP are more focused at page scripting and less on application level development. ASP.NET is a application development framework (.NET with all its programming languages and technologies) wrapped around a stateless web type structure. It is common to see n-tier application structure in ASP.NET development. The focus is on an "application" and not just a web page. I started working with CGI modules back in 1996 (or somewhere right around there). Moved on to PHP for about a year or year and then to ASP classic for a few years until ASP.NET arrived and all my development switched to it. There are tons of features in ASP.NET that would require considerable extra work in other technologies and more are added every year. Now, you can take advantage of .NET 3.0 with all its features throught a web application, you have the complete power of the framework at your finger tips. While it takes a while to get comfortable with ASP.NET (mostly changing your view of a web site to an application and how the components work together), it is a very flexible and power filled technology. Also, in today's world, most hosts have ASP.NET available and can be as cheap as just a few $$ per month.
Rocky <>< Latest Code Blog Post: ASP.NET HttpException - Cannot use leading "..".. Latest Tech Blog Post: Replacing Vista System HD & New things learned!
-
Being a neverending argument I just thought this part of the toolbox discussion deserved its own thread ;P I really can't comment on ASP.NET since i've never dealt with it, but i've looked at scripts and it seems a lot more functional than ASP classic. With ASP classic itself i'd say it's usable since i as a web dev can count on seeing it on most Windows servers when they don't have anything else installed and get the job done (now that i know enough of it). I find PERL to be more comfortable than VBScript when i'm working in ASP classic but i rarely see a PERL engine installed, so i often have only one way to go. I've worked with PERL before and that's part of the reason why I prefer PHP. I often find myself reverting to the PHP way of declaring a variable ($var_name) under ASP and then having to go back and correct it... I doubt it'll be an easy transition if i went into ASP.NET so i'm not really sure if i will, but anyways... Roswell:rose:
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CAAll three can manage most of the time and for 90% of what most people want to do. ASP however tends to be left behind with ASP.NET. The main advantage however is that .NET has the VS monster elegantly hiding behind the '.NET' word, so unwillingly (we think) it monopolises the minds of developers. Has anyone (except me) tried cross-breeding a .NET application with a PHP site on APACHE?
-
All three can manage most of the time and for 90% of what most people want to do. ASP however tends to be left behind with ASP.NET. The main advantage however is that .NET has the VS monster elegantly hiding behind the '.NET' word, so unwillingly (we think) it monopolises the minds of developers. Has anyone (except me) tried cross-breeding a .NET application with a PHP site on APACHE?
Another example: To make a DNS connection with a MS-Access file in PHP with an SQL statement: you can write something like this:
$AppPath = $PATH_TRANSLATED; $DbFile = dirname ($AppPath). "\\\VAS lokaal.mdb"; // $file is set to "/etc" $Provider = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=$DbFile"; $conn = new COM("ADODB.Connection") or die("Cannot start ADO"); // Microsoft Access connection string. $conn->Open("DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=D:\\Webs\\vakantiepunten.nl\\databases\\VAS lokaal.mdb"); $conn->Open($Provider); // SQL statement to build recordset. $rs = $conn->Execute("SELECT * FROM VpSparen WHERE Status='Live'");PHP can use ODBC less connections, or use ODBC connections, and is therefore more flexible (because you can move the access file to a different directory). When doing something in ASP you should see something like this:<% Dim rsSparen Set rsSparen = CreateObject("ADODB.RecordSet") SQL = "SELECT VpSparen.*" SQL = SQL & " FROM VpSparen" SQL = SQL & " WHERE SpaarCategorieID=" & Session("SpaarCategorieID") SQL = SQL & " AND Waar = 'SparenLinks' AND Livetot > #" & Now & "# AND Status = 'Live'" SQL = SQL & " ORDER BY Sort" rsSparen.Open SQL, Conn, 2, 3 %>The ASP script looks small doesn't it? And it works fine too (when there's nothing wrong with the ODBC settings), but when you want to move your MS-Access file, you'll receive a message like this: Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified ASP depends on various external objects, while PHP doesn't. Without ODBC the PHP script still works . . . It is also possible to do some OOP programming in PHP too . . . and it is simple to include them in your PHP file . . . Another great thing is that PHP supports a wide range of databases with MySQL on top.... And last but not least: PHP also uses different libraries and works fine in a Linux environment and in a MS-Windows environment. It is possible to write your own PHP classes too . . . :cool: -
Rocky Moore wrote:
One main key to any development is to use tools you know.
Yeah and the exact reason for at least half the crappy projects out there: the developer only knew how to use a hammer when a screwdriver would have sufficed. ;)
I blame documentation for that. In many cases I find myself wanting to do something but I can't find decent documentation on the class objects that I think should do it. Searching for help using Google can lead to mixed results - especially when I'm not sure of the exact phrasing I should use for what I'm looking for.
-
I went from doing almost no web development, to bieng the companies main web guy, and all we use is ASP.NET/c#. I picked up the basics in a matter of weeks and could do just about anything you wanted in it before we hired a new web dev(who also hadnt used ASP.NET, but had used PHP and PERL) and he picked it up just as quickly as i did, and likes ASP a lot better than PHP and PERL. i had to convert a php site to run w/ our databases and on our servers once, and while i picked up what little php i had to use, it just seemed like more of a mess than ASP, of course we use code behind pages for everything and almost never have any inline script. it may not be as fast, but i've never had a problem w/ our database connection, and if a site doesnt work on anything but IE thats the designers problem, our site doesnt work in opera or safari, but FireFox and IE display it fine.
:rolleyes: I agree. I struggled to learn Perl, PHP, and ASP during college. And everything I knew before is now a haze in my memory. I am fascinated, delirious even, with the advent of ASP.Net. Everything is a breeze. rexlallatajr aka rexpogi
as the water rises, so must the boat
-
I blame documentation for that. In many cases I find myself wanting to do something but I can't find decent documentation on the class objects that I think should do it. Searching for help using Google can lead to mixed results - especially when I'm not sure of the exact phrasing I should use for what I'm looking for.
holywhippet wrote:
I blame documentation for that.
Here Here As a learner, I am so frustrated with MSDN - you need to be an expert programmer to understand what they are saying. Then I go googling and find most help I can. What really pissed me of recently was when I asked a question here in Codeproject and some smart %$#@ told me to look it up on MSDN :mad: Thank god for Codeproject :-D
Glen Harvy