Board index » delphi » Who needs a .JSP, when .PHP and .ASPX dominate?

2007-04-07 03:57:06 AM
delphi102
With the proliferation of Web applications written in PHP and
the ubiquity of .aspx applications, using the "almighty" C#,
why would anyone want to write Web applications,
using Java? I have not even mentioned Ruby, which
is becoming the hot language in town. Who needs .JSP then?
 

Linux? Of course once Mono catches up to .Net 2, then there will be
less of an argument.
I know PHP runs on Linux, but I think Java and ASP.Net are the two that
are more closely related feature for feature.
I would prefer to write in C# with ASP.Net / Mono and deploy it on Linux
and Apache.
Gbenga A{*word*73}la writes:
Thomas Miller
Chrome Portal Project Manager
CPCUG Programmers SIG Chairperson (formally Delphi)
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork
www.bss-software.com
programmers.cpcug.org/
sourceforge.net/projects/chromeportal/
sourceforge.net/projects/uopl/
sourceforge.net/projects/dbexpressplus
 

Those who want to develope enterprise applications that will run on all
servers available in the market. From desktop PCs to multiprocessor
mainframe level redundant servers. i.e. JSP runs on any OS and any
platform, ASPX does not.
High availability and stability of Unix servers is another big plus.
"Gbenga A{*word*73}la" <XXXX@XXXXX.COM>writes

Gbenga A{*word*73}la writes:
It is not JSP itself per se, but the backend object interoperability
that the Java platform provides that makes the difference.
Try writing COM+ based objects on a AIX, HP-UX, AS400, OS390, Solaris,
or Linux based server.
Try tying into COBOL, C++ objects on Unix, MVS based OSes with DOT.MS.NET.
PHP has good usage for sites where scalability across platforms is not
important. Good, but I see actually no difference between PHP and Java
JSP based applications. The largest difference is that PHP design
patterns are anathema to most Java developers. As a note, I do not agree
with many of the Java purist about this either. I see no problem in
allowing for more tightly coupled JSP and Java Object use in many of the
smaller or more isolated JSP/Servlet patterns, In fact I personally
believe that many of the newer "PURIST" frameworks makes development
much more difficult.
I am not even going to mention NET. NET is basically a MS only
framework. True there is MONO, which usually lags two years or more
behind current MS NET platform releases.
Ruby has many good things to recommend it, especially RAILS. Since rails
can run on any JVM, it is a more viable option, as is Groovy.
Please note, that I am not attempting to denigrate any of these
solutions, platforms, or languages. I am merely attempting to answer the
question of why Java is the more ubiquitous and why. PHP became more
popular due to supposed simplicity, and because Java was not (at that
time) open source. I'd expect to see Java to become more ubiquitous
in the Open Source circles now, since it is now GPL2.
I think the Rails patterns is going to revolutionize many platforms,
including all of the ones mentioned above. Rails makes many common type
Internet/Intranet application development much easier. I wish Java would
have followed this pattern a long time ago, and gotten away from complex
frameworks that can take as much time to learn and adopt as the language
itself.
Of all of those mentioned above Rails type frameworks have more to
commend it than any other mentioned frameworks or languages/patterns to
unseat Java. One is it simplicity, the other is you can still do the
complex and xplatform work in Java and take advantage of the shorter
front end and controller work in Rails.