I just finish my masters in computer science. I am confused which language is to choose. what is difference between PHP, ASP.net and JSP. I have learned somewhat in my course only JSP and little bit servlets. Can anybody make comparison of these languages demand wise and popularity wise and cost wise. What about C# is the demand of c# programmer increasing? I searched on net but there is only competition about .net and java. every person arguiing which he like most. not found an indepedent comparison. Pls make detail comparison as lot of new graudates are still confuse and lack of guidance in Pakistan. I shall be very thankful.
With masters in CS, you should be able to program in all languages. You only need startup info on the syntax. To be a good programmer, you need to be good in theory, algorithms and programming structure. If you know them, learning the syntax in any language should be easy. I would advise that you start programming in the language that is demanded more in Pakistan, which will make it easier to get a job. Peace,
If there was a "Best" there would only be one.... each have their own strengths and weaknesses. (ASP).Net isnt a language but is a framework, .Net can be programmed in C#, VB, J#, C++, IronPython and many more The problem is that whilst in theory people can program in any OOP after learning the theory and it is just a case of learning the syntax the reality is the majority have their preferences and so any review of languages will have the authors bias added
It sounds like you're just looking to work for someone else who already has projects going, in which case you don't get to choose the languages used. So in that case, just do a bit of research. How would people normally find work in Pakistan? Internet job boards? Contacts? Your school? Take a look at the listings you can find to gauge how much in demand each skill set is.
Facebook Best Programming Language <--- the best Language ever group... click to find out what they support ^^.
Funny, I generally consider the rubbish most people with college educations have their heads filled with by professors with nothing but theoretical knowledge makes that piece of paper not even worth as much as a sheet of toilet tissue. (sorry, after three decades in the field - having started before anywhere but Ivy league had computer programs worth a damn...) I would revise that to "the right tool for the right job". Need portability across every platform? Java. Need maximum execution time? Assembly. Need good library support with reasonably fast execution? Pick a high level compiled language like C. Need clarity of code? Pascal/Modula. Though I think you do need to be set straight on something - ASP and ASP.net are NOT programming languages. They are an interface technology to allow other programming languages to write web applications. You can write ASP.net 'code' in Visual Basic, Javascript, J#, C#, C++, any language that can target .net - which means you could even use the latest CodeGear Delphi (Delphi 2k7 added .net support). Personally I like PHP for making web applications because it feels 'closest' to flat markup. This close relationship to what is going to be output can in fact make it faster in a lot of situations than other interpreted languages that have faster code execution. PHP excels at rapid development because of 'no compile time', and while raw execution of logic flow and variable handling is slower than many other languages, when it comes to outputting raw markup it can consume less overhead... Though the easiest way to speed up php code is to actually offload as much processing as possible to it's existing functions and external server software like mySQL. PHP really shines as a quick glue to turn mySQL into markup, but shows it's weakness where any complex data-handling needs to be ground-up coded. Regular ASP is attractive because you are able to use compiled code to make your back-end. NOTHING is going to be faster than that. The problem is that unless you are using one of the better M$ compilers like C, your code is going to end up the same fat bloated mess as every other VB crapplet. You can also make ASP in interpreted languages, which to me defeats the whole point. ASP.net takes all the advantages of ASP and chops it off at the knees - yes, you heard me! It drags it down to Java speed since it's a VM, or as we used to call it a bytecode interpreted language, and no amount of just in time compiling is going to make up for that fact. Still the .net languages are all the rage, and it's still going to be faster than PHP where complex data handling is concerned. As to JavaServer Pages, in terms of syntax everything I've seen done in it has been a maintainers nightmare. Java is a language that flat out was never meant to create html, and it shows the first time you try to use out.print - or the train wreck of nonsense that makes up 'tag libraries'. It reeks of the same problems as XSLT, where the 'tax' of basically writing everything twice in two places cannot possibly be offset by any alleged 'savings' in the output. Well, that and I trust Java about as far as I could throw Rush Limbaugh. Every time I've tried to use java for ANYTHING it's been a train wreck that makes the Great Circus Train Wreck look like a 5mph fender bender. I won't even allow it to be installed on my servers OR my workstations anymore. In my own code I've begun to use PHP more like glue for handling markup, and ASP or even native executables for the more complex code. For example I've written a few apps that needed very complex object tables with very quick execution times lately, and I ended up passing the data from php to Free Pascal. In a way doing this with php is an extension of the old programming addage: "Optimize INSIDE the loop"... 50% extra cycles on code that executes once means nothing compared to 10% extra cycles that is going to iterate ten times. While CGI/BIN is slower than php as a native plugin, once you get the data in there if you need to parse really large data sets (like a server log) native compiled code is going to be hard to beat... Just don't plan on portability. Again, the right tool for the right job... and for my distaste of JSP I will still look at it from time to time to see if I can find a use for it because at the end of the day it's just another tool in the toolbox. Never throw out a tool and never assume the tool you are using is the best for the job. The ability to rapidly change tools to fit the project at hand will serve you far better than mastery of any one.