Tuesday, April 12, 2005

ASP.NET is More Efficient than Java (Here’s why)

This is only one example of how ASP.NET is better than Java. There might be several reasons that Java is better than ASP.NET. These are just my views of a particular situation. I do believe though that ASP.NET for web applications is better source than Java on a Windows machine.

Ok, where I work we are about to switch over to clocking in at our desk instead of going to a designated spot and clocking in and out. This is a good thing to have happen because it will help on productivity because people can work right up to closing time then clock out without having to walk somewhere. This will save money because people won’t be as likely to idle around waiting for time to finish they can keep working. This is a plus to this system, but that is not what I am going to talk about.

This little application that we use is a web based application. It is hosted on a server in our intranet so that all you have to do is go to a web address anywhere in the company and you can clock out. However the problem is, in my opinion, that it is running a Java applet. While this may not be bad to the general user that doesn’t care; It annoys the heck out of me because it takes so long to load and I know of a more efficient way of doing it.

You see what happens is the computer calls the server and the server loads up the web application and the clients browser sees that there is a java applet. So it then calls on the runtime to interpret and run this applet. This takes quite a bit of time, I have clocked it at 5 seconds. While this may not seem like a lot on a large scale this can is a lot of wasted time, and waste of resources because the applet has to run on the clients machine.

Another problem with running the java applet is that the IT department must now spend quite a bit of time going to every computer and installing the java runtime. With a company at well over 100 computers this is an all day project. Not to mention you have to make sure that no one is at the computer, or you have to waste a Saturday coming in and installing it. This will cost a the company money because not only does the company have to pay for the time to get it installed on a computer, but they have to worry about headaches that may arise if he misses a computer or something happens to the runtime, though rare can happen.

Now if the company were to use ASP.NET then it would save time in many ways. Not only would the development life cycle be shorter, but the IT department would not have to go around to the computers and install the java runtime, saving a significant amount of time. What does this mean. Well the application can be cheaper, and you don’t have to pay people to waste time installing a runtime.

With ASP.NET it will display the same thing to you that the java applet will, but run it completely off of the server so that the users browser only has to read the HTML. This is a significant performance advantage because only one program is doing something. Also with the way that IIS 6.0 processes ASP.NET pages there is almost no strain, if any, on the server when running the application.

With significant performance gains lower Total Cost of Ownership of a intranet based web application you can tell that ASP.NET is a better way to go in this case. I hope that maybe I helped you learn something today. Again these are my views enjoy.


At 9:21 PM, April 13, 2005, Blogger Chad said...

Very interesting.. how exactly does the clock out app work (swipe card, pin number, etc)? I whole heartedly agree with you about the slow load times of Java. I often wonder why universities churn out so many Java programmers ever semester...

At 10:16 PM, April 13, 2005, Anonymous Anonymous said...

Nice start to the argument, but...

What about the other factors:

Current technology skillset of the IT staff, cost of migrating from existing server/desktop platform to Microsoft, maintenance, security, updates while using MS .NET?

There are places for .NET and places for the other technologies...

The head honcho of the IT department (CTO) has to take ALL of the variables into account when deciding what, where, when and how to deploy a new solution to a problem...Often there are many factors that (we) developers fail to see because we are on the front lines - there are few who can see the forrest AND the trees.

I do agree that .NET would be a great solution in this case - if and only if the other factors don't take over.

Maybe the 5 second wait time was the caveat that the CTO chose - i.e. the lesser of all of the other evils?


At 9:53 AM, April 14, 2005, Blogger Buddy Lindsey said...

Chad - basically you login hit a button and it records the time in the database. It checks to see if you are clocked in, and if so sets you as clocked out. This is all i have access to, but i will find out more later on other features.

anonymous - Agreed, I was just pointing out one position on this. I can see it from the development company's perspective they have to run the program on both linux and windows based platforms so Java was the optimal choice for them. Basically, in this situation i feel that it would be best, but hey what can you do.


Post a Comment

<< Home