JSF vs ASP.net
DuncanE asks: "We are looking at migrating an old legacy database application to a newer web
based framework for the front end. For me the two obvious choices are ASP.net vs
Java Server Faces. CodeGuru has
side by side look at both, but does anyone have any real world comparisons? ASP.net appears to be MS only, which is a concern, depending on how mature
mod_mono has become." Which framework would you prefer to use? Under what situations and conditions would you recommend the use of the other?
I'm not very experienced with either (know a bit of java, and used to work with ASP/VB on NT4), but for a project like you're describing, ASP and Java would be the last thing I consider.
Both have a reputation for being slow, insecure, and proprietary. As much as sun is trying to shed the image, Java is still their property.
Generally, it's a decent idea to separate the databse from the application/interface, and it looks like you've already done just that, so you should be pretty much able to pick whatever language you want. I'd be inclined to think that ASP.net supports the microsoft databases the best, and leaves a hazy future as to whether or not it will play nicely with your database. I also wouldn't like to rely on a Windows operating system as your server environment.
I'd shop around..... if this is really *just* a frontend, you could go as far as checking out one of the newer languages like python or php. If you want to possibly speed up development, and play around with a few new technologies, you could also check out ruby and see if it suits your needs.
Look at what other people are using. I'd tend to think that PHP and ASP.Net seem to be the two most popular. ASP.Net does have advantages, and from what I hear, it's leaps and bounds better than the original ASP I worked with on NT4. I personally wouldn't like to be locked down to windows OR mono (if it were to ever be shut down by microsoft for some sort of leagal trouble, you'd be in trouble)
But java....just makes me cringe. I've seen very few well-written java applications that were fast, stable, and functional. It can be done.... but very few are able to
-- If you try to fail and succeed, which have you done? - Uli's moose
"ASP.net, on the other hand, is a Microsoft solution, and you depend on the whims of MS for everything."
Spoken like a true anti-MS bigot.
"It runs on little more than Windows/IIS"
I guess if you consider Linux/Apache "little more" the Windows/IIS then that statement is true.
"and the only serious IDE for it would be Visual Studio.net"
And it's probrably one of the best IDEs available. This is the one categoy that MS really pwns the competition, their IDEs are awesome.
"and good luck trying to run it under mono if you favorite class or function is incomplete or has a bug in its mono implementation"
Yes because when running a completely non-MS related open source solution you will never find a bug or incomplete functionality. If you're going to pimp OS, do so across the board. Not this "OS roxors, except when it deals with Microsoft!" bantor.
Me personally, I prefer ASP.Net. I think Java is a great language for web development, but ASP.Net has a few advantages: 1) The IDE. 2) Availability and Cost of developers. 3) External vendor suport available.
If you already have a shop of Java developers, then 1 and 2 are of little concern. And 3 is a pretty rare requirement.
-Rick
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs