hi sir i m study in mca in IGNOU , what is bater java & .net i which side make careers.  

This is not surprising, as Java runs on far more platforms (Mac, Unix, Linux, MS-Windows, etc.) than .NET and C# (MS-Windows only, and arguably Linux but with some major qualifications). The releases of new JDK’s on the different platforms is better coordinated too. These things help companies targeting enterprise and consumer end-user markets alike.

Microsoft’s technologies seem to have a “three year half-life”. What this means is that three years after a technology comes out, Microsoft’s own programmers are already kind of putting down the technology they were coaxing everyone to switch to three years earlier. Because now, they are using their “next big thing” which is incompatible with that and they want to set the mood for another “mass migration”.

Sadly, because of the compatibility gaps they keep encountering so frequently, companies trying to build a long term investment on these programming products get jolt after jolt of bad news from development teams.

Here are a few examples:
Win16=>Win32, Win32=>Win64, MFC=>?, C++=>C#, VB3/4=>VB5, VB5/6=>VB.Net, WFC=>nowhere!, MS-Java=>nowhere!

Since the class libraries and language syntax changes with every other release, and this i going on simultaneously in OS APIs, languages, and frameworks/libraries all the time, companies get bumped for expensive tools with great regularity. Thus, each programmer they hire is more expensive. Not to mention, their products are constantly obsoleted and need to be rewritten. Further, they can be fettered to inappropriate hardware or operating systems by the very language they programmed in.

This does not happen in Java. Java interpreters get ported quickly to each new version of an OS that Java supports. Java IDEs are free, so there is no IDE payroll tax on Java programmers. Further, the power of a Java IDE like Eclipse or NetBeans is unrivaled.

That said, if you want to write extensions to MS-Outlook or custom macros for MS-Word, you are going to have to involve a Microsoft language tool in some way. Though frankly, it is possible to write a bridge in such a tool and do the bulk of your development in Java anyway, if you put some forethought into your analysis/design.
Those are the things you need to weigh. Make your own decision. And remember, the first language you learn does not have to be the last.

Answered by Raksha , an ibibo Master, at 9:19 AM on June 27, 2008

as Java runs on far more platforms (Mac, Unix, Linux, MS-Windows, etc.) than .NET and C# (MS-Windows only, and arguably Linux but with some major qualifications). The releases of new JDK’s on the different platforms is better coordinated too. These things help companies targeting enterprise and consumer end-user markets alike.

Microsoft’s technologies seem to have a “three year half-life”. What this means is that three years after a technology comes out, Microsoft’s own programmers are already kind of putting down the technology they were coaxing everyone to switch to three years earlier. Because now, they are using their “next big thing” which is incompatible with that and they want to set the mood for another “mass migration”.

Sadly, because of the compatibility gaps they keep encountering so frequently, companies trying to build a long term investment on these programming products get jolt after jolt of bad news from development teams.

Here are a few examples:
Win16=>Win32, Win32=>Win64, MFC=>?, C++=>C#, VB3/4=>VB5, VB5/6=>VB.Net, WFC=>nowhere!, MS-Java=>nowhere!

Since the class libraries and language syntax changes with every other release, and this i going on simultaneously in OS APIs, languages, and frameworks/libraries all the time, companies get bumped for expensive tools with great regularity. Thus, each programmer they hire is more expensive. Not to mention, their products are constantly obsoleted and need to be rewritten. Further, they can be fettered to inappropriate hardware or operating systems by the very language they programmed in.

This does not happen in Java. Java interpreters get ported quickly to each new version of an OS that Java supports. Java IDEs are free, so there is no IDE payroll tax on Java programmers. Further, the power of a Java IDE like Eclipse or NetBeans is unrivaled.

That said, if you want to write extensions to MS-Outlook or custom macros for MS-Word, you are going to have to involve a Microsoft language tool in some way. Though frankly, it is possible to write a bridge in such a tool and do the bulk of your development in Java anyway, if you put some forethought into your analysis/design.
Those are the things you need to weigh. Make your own decision. And remember, the first language you learn does not have to be the last.

Answered by Sharad Singh , an ibibo Master, at 6:30 PM on June 05, 2008

I would like to say that JAVA is in more in use please check out the details about it: Java probably has a slight edge here.
Microsoft’s technologies seem to have a “three year half-life”. What this means is that three years after a technology comes out, Microsoft’s own programmers are already kind of putting down the technology they were coaxing everyone to switch to three years earlier. Because now, they are using their “next big thing” which is incompatible with that and they want to set the mood for another “mass migration”.

Sadly, because of the compatibility gaps they keep encountering so frequently, companies trying to build a long term investment on these programming products get jolt after jolt of bad news from development teams.

Here are a few examples:
Win16=>Win32, Win32=>Win64, MFC=>?, C++=>C#, VB3/4=>VB5, VB5/6=>VB.Net, WFC=>nowhere!, MS-Java=>nowhere!

Since the class libraries and language syntax changes with every other release, and this i going on simultaneously in OS APIs, languages, and frameworks/libraries all the time, companies get bumped for expensive tools with great regularity. Thus, each programmer they hire is more expensive. Not to mention, their products are constantly obsoleted and need to be rewritten. Further, they can be fettered to inappropriate hardware or operating systems by the very language they programmed in.

This does not happen in Java. Java interpreters get ported quickly to each new version of an OS that Java supports. Java IDEs are free, so there is no IDE payroll tax on Java programmers. Further, the power of a Java IDE like Eclipse or NetBeans is unrivaled.

That said, if you want to write extensions to MS-Outlook or custom macros for MS-Word, you are going to have to involve a Microsoft language tool in some way. Though frankly, it is possible to write a bridge in such a tool and do the bulk of your development in Java anyway, if you put some forethought into your analysis/design.

Also, someone wrote a few months ago that there was a shortage of C# programmers because even though fewer companies were using it, there were even fewer programmers than they needed that knew it!

Answered by Shobhit , an ibibo Master, at 4:51 PM on June 04, 2008

well Sanket, This is not surprising, as Java runs on far more platforms (Mac, Unix, Linux, MS-Windows, etc.) than .NET and C# (MS-Windows only, and arguably Linux but with some major qualifications). The releases of new JDK’s on the different platforms is better coordinated too. These things help companies targeting enterprise and consumer end-user markets alike.

Microsoft’s technologies seem to have a “three year half-life”. What this means is that three years after a technology comes out, Microsoft’s own programmers are already kind of putting down the technology they were coaxing everyone to switch to three years earlier. Because now, they are using their “next big thing” which is incompatible with that and they want to set the mood for another “mass migration”.

Sadly, because of the compatibility gaps they keep encountering so frequently, companies trying to build a long term investment on these programming products get jolt after jolt of bad news from development teams.

Here are a few examples:
Win16=>Win32, Win32=>Win64, MFC=>?, C++=>C#, VB3/4=>VB5, VB5/6=>VB.Net, WFC=>nowhere!, MS-Java=>nowhere!

Since the class libraries and language syntax changes with every other release, and this i going on simultaneously in OS APIs, languages, and frameworks/libraries all the time, companies get bumped for expensive tools with great regularity. Thus, each programmer they hire is more expensive. Not to mention, their products are constantly obsoleted and need to be rewritten. Further, they can be fettered to inappropriate hardware or operating systems by the very language they programmed in.

This does not happen in Java. Java interpreters get ported quickly to each new version of an OS that Java supports. Java IDEs are free, so there is no IDE payroll tax on Java programmers. Further, the power of a Java IDE like Eclipse or NetBeans is unrivaled.

That said, if you want to write extensions to MS-Outlook or custom macros for MS-Word, you are going to have to involve a Microsoft language tool in some way. Though frankly, it is possible to write a bridge in such a tool and do the bulk of your development in Java anyway, if you put some forethought into your analysis/design.
Those are the things you need to weigh. Make your own decision. And remember, the first language you learn does not have to be the last.

Answered by Romi , an ibibo Master, at 8:34 PM on May 30, 2008

well Sankit, I would like to say that JAVA is in more in use please check out the details about it: Java probably has a slight edge here.
Microsoft’s technologies seem to have a “three year half-life”. What this means is that three years after a technology comes out, Microsoft’s own programmers are already kind of putting down the technology they were coaxing everyone to switch to three years earlier. Because now, they are using their “next big thing” which is incompatible with that and they want to set the mood for another “mass migration”.

Sadly, because of the compatibility gaps they keep encountering so frequently, companies trying to build a long term investment on these programming products get jolt after jolt of bad news from development teams.

Here are a few examples:
Win16=>Win32, Win32=>Win64, MFC=>?, C++=>C#, VB3/4=>VB5, VB5/6=>VB.Net, WFC=>nowhere!, MS-Java=>nowhere!

Since the class libraries and language syntax changes with every other release, and this i going on simultaneously in OS APIs, languages, and frameworks/libraries all the time, companies get bumped for expensive tools with great regularity. Thus, each programmer they hire is more expensive. Not to mention, their products are constantly obsoleted and need to be rewritten. Further, they can be fettered to inappropriate hardware or operating systems by the very language they programmed in.

This does not happen in Java. Java interpreters get ported quickly to each new version of an OS that Java supports. Java IDEs are free, so there is no IDE payroll tax on Java programmers. Further, the power of a Java IDE like Eclipse or NetBeans is unrivaled.

That said, if you want to write extensions to MS-Outlook or custom macros for MS-Word, you are going to have to involve a Microsoft language tool in some way. Though frankly, it is possible to write a bridge in such a tool and do the bulk of your development in Java anyway, if you put some forethought into your analysis/design.

Also, someone wrote a few months ago that there was a shortage of C# programmers because even though fewer companies were using it, there were even fewer programmers than they needed that knew it!

Answered by satyaiitk , an ibibo Master, at 11:36 AM on May 30, 2008

Both of them are good enough . but, Java is mostly used nowadays .

Answered by Hem@nt , an ibibo Master, at 9:58 AM on May 30, 2008

well , I would like to say that JAVA is in more in use please check out the details about it: Java probably has a slight edge here.

Far more development work is being done in Java than C#.

This is not surprising, as Java runs on far more platforms (Mac, Unix, Linux, MS-Windows, etc.) than .NET and C# (MS-Windows only, and arguably Linux but with some major qualifications). The releases of new JDK’s on the different platforms is better coordinated too. These things help companies targeting enterprise and consumer end-user markets alike.

Microsoft’s technologies seem to have a “three year half-life”. What this means is that three years after a technology comes out, Microsoft’s own programmers are already kind of putting down the technology they were coaxing everyone to switch to three years earlier. Because now, they are using their “next big thing” which is incompatible with that and they want to set the mood for another “mass migration”.

Sadly, because of the compatibility gaps they keep encountering so frequently, companies trying to build a long term investment on these programming products get jolt after jolt of bad news from development teams.

Here are a few examples:
Win16=>Win32, Win32=>Win64, MFC=>?, C++=>C#, VB3/4=>VB5, VB5/6=>VB.Net, WFC=>nowhere!, MS-Java=>nowhere!

Since the class libraries and language syntax changes with every other release, and this i going on simultaneously in OS APIs, languages, and frameworks/libraries all the time, companies get bumped for expensive tools with great regularity. Thus, each programmer they hire is more expensive. Not to mention, their products are constantly obsoleted and need to be rewritten. Further, they can be fettered to inappropriate hardware or operating systems by the very language they programmed in.

This does not happen in Java. Java interpreters get ported quickly to each new version of an OS that Java supports. Java IDEs are free, so there is no IDE payroll tax on Java programmers. Further, the power of a Java IDE like Eclipse or NetBeans is unrivaled.

That said, if you want to write extensions to MS-Outlook or custom macros for MS-Word, you are going to have to involve a Microsoft language tool in some way. Though frankly, it is possible to write a bridge in such a tool and do the bulk of your development in Java anyway, if you put some forethought into your analysis/design.

Also, someone wrote a few months ago that there was a shortage of C# programmers because even though fewer companies were using it, there were even fewer programmers than they needed that knew it!

So, from an economic standpoint, if all these things are true, it sounds like today you might have a slightly easier time finding a C# job than a Java job. However, it might pay less since there is essentially a Microsoft tax on your desktop operating system, compiler, and IDE – that a Java shop would not have to pay because Linux, Java, and Eclipse are free. The same economics apply to where ever the code you write eventually ends up running too.

Source Site could give you more information :

www.43things.com/entries/ view/536738

Answered by Saurabh , an ibibo Master, at 8:59 AM on May 30, 2008

java

Answered by sushil , an ibibo Citizen, at 1:18 AM on May 30, 2008

well Sanket; Right, for instance, if you are going to write some code to automate MS-Word you might be well off to do that in C#. After all, Microsoft makes both products.

On the other hand, if you want your code to be portable and look at MS-Word as a sort of a word processing “device”, which in a sense it is, then you could writer a driver for it and do the bulk of your business logic and data-acess logic in Java. That would make your code portable and retargettable as well.

That might turn out to be more work than simply using C# and .NET to do the job. Depends on the immediate requirements and imminent future requirements.

Isolating peculiarities is a standard strategy of good architecture/design. However, keeping things as simple as possible is a hallmark of good coding tactics.

So the situation, and the relative skill of the programmer(s) in each technology will probably be the indicator of which is the best approach . Context is pretty important.
To put my opinions in some kind of coherent perspective, here is an orderly list of my current take on the situation:

1. Java syntax and OOP are the future. We SHOULD teach it in high schools and colleges, precisely because if they don't learn OOP cleanly, when the next gen languages hit, they will need to be ready to jump on the bandwagon. Ammendment: They do need a working knowledge of Pointers, etc

2. Java is a wonderful language for apps on consumer machines.... portable machines, cable boxes, and other systems where people are not so angry about waiting and do not want to learn to intall native-chips from SUN in their brand-new gateway. Java was not created to write pretty GUI applications, or at least that is not where it showed the greatest initial promise (Oak). Due to its portability, it is the currently the middle ground between all sorts of OS factions. That is unfortunate... mostly because they don't seem to get along when they are not sharing apps. Most programmers, also, can't seem to realise that Java's accidental incororation into the WWW was as much a new direction as C's sudden conversion to OOP. Neither was perfect, but we all know that C#/C++.net were designed to be run natively (on Windows AKA 99% of the end-user's machines) and JAVA was designed with an open adapter that can be MOLDED to fit Windows, Linux, Sparc, your TiVo,etc.
Common Question: No SUN ahead of time compiler??? Why bother? It's like using a wrench to turn a screw... why haven't they made adapters to do that? Think about it...

3. Clarification: I do not like .NET. I will give j2SE the following: its as prettier than i could have imagined it would be. .NET still feels like what it is... a way to make windows APPS w/o MFC. Sure, I see the extra utils, the extra classes... i also see VStudio .NET being handed out to college kids like candy (here is the future of programming...?) when they should be learning MFC (in C) and what makes a GIF. Reactionary to Java? I'd bet on it. Dirty? No, not at all. If microsoft can win (by virtue of quality), THAT is where my money will go.

Despite my knowledge that neither J2SE nor .NET is a near perfect solution, i have to say that what i see (here comes opinion, heavy dose) is a gross misunderstanding by converts of JAVAs beauty and charm taking the torches to Microsoft, that old bully, who wrote that mean old operating system. They are not your enemy. There is no politics in Programming when I'm behind the keys.


For more information , please do visit source site:
http://www.oreillynet.c om/pub/wlg/2603

Hope it will help you out.

Answered by Uttam , an ibibo Master, at 8:26 PM on May 29, 2008