Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
Currently I have two opportunities in two somewhat diverging development paths. One is re-learning Java and the new frameworks, and the other continuing on with my current C# MVC work. My question is which pays more as a contractor and/or which has more demand? I seem to be getting many more job offerings for Java than C#. Will this trend end? C# seems to be gaining ground with Linq/lambda expressions...while Java is very mature. Any thoughts?
I say you re-learn java and accomplish two things at once. First, you will indeed find more jobs looking for Java than C#. Second of all, any java developer can learn c# pretty quickly as the thier sytanx and OOP setup are almost identical. Obviously, there are some minor differences between the two, but a java programmer learning C# shouldn't be too hard, so I say focus on that first.
Java for mobile applications and older server applications and web applications.
C# for web applications, Sharepoint.
Java: Lots and lots of application support needed. Will be easier to find jobs, but pay is lower (lots of Java experts out there).
C#: Sharepoint implementation is huge right now and there's a need for C# developers, but not as many existing applications out there in need of support. So there's not as many jobs for C#, but the pay is a lot higher.
Personally, I'd go with C#, unless you want to go into the mobile space.
Java for mobile applications and older server applications and web applications.
C# for web applications, Sharepoint.
Java: Lots and lots of application support needed. Will be easier to find jobs, but pay is lower (lots of Java experts out there).
C#: Sharepoint implementation is huge right now and there's a need for C# developers, but not as many existing applications out there in need of support. So there's not as many jobs for C#, but the pay is a lot higher.
Personally, I'd go with C#, unless you want to go into the mobile space.
You make a great point, guess I wasn't looking at it form that point of view.
Java for mobile applications and older server applications and web applications.
C# for web applications, Sharepoint.
Java: Lots and lots of application support needed. Will be easier to find jobs, but pay is lower (lots of Java experts out there).
C#: Sharepoint implementation is huge right now and there's a need for C# developers, but not as many existing applications out there in need of support. So there's not as many jobs for C#, but the pay is a lot higher.
Personally, I'd go with C#, unless you want to go into the mobile space.
You make really interesting points. However, aren't mobile devices the future anyway? So then, wouldn't this give an edge to Java?
I've been working in C# for years, and would like to be more marketable. This new opportunity is Java, Spring, Struts work. And, the company is aware of my Java work years ago, so no pressure in having a learning curve. I'm not sure what to do....
You make really interesting points. However, aren't mobile devices the future anyway? So then, wouldn't this give an edge to Java?
I've been working in C# for years, and would like to be more marketable. This new opportunity is Java, Spring, Struts work. And, the company is aware of my Java work years ago, so no pressure in having a learning curve. I'm not sure what to do....
Thanks for all your responses.
I personally think that mobile apps are at their peak now. Going forward, I expect everything to be web apps that run across multiple platforms through web browsers.
Based on my expectations, learning HTML5 would be a good idea.
You make really interesting points. However, aren't mobile devices the future anyway? So then, wouldn't this give an edge to Java?
I've been working in C# for years, and would like to be more marketable. This new opportunity is Java, Spring, Struts work. And, the company is aware of my Java work years ago, so no pressure in having a learning curve. I'm not sure what to do....
Thanks for all your responses.
The only platform that you can do mobile in Java on is Android. Of course Android is gaining a lot of momentum.
Quote:
Originally Posted by NJBest
I personally think that mobile apps are at their peak now. Going forward, I expect everything to be web apps that run across multiple platforms through web browsers.
Based on my expectations, learning HTML5 would be a good idea.
I think there will always be a market for certain kinds of apps, but there are lots of instances where web based is definitely going to be a better option.
I'm getting ready to add mobile portions to a reporting suite that I develop, and I'm going to do it all server side (ASP.NET) so that I don't have to write 3 or 4 different apps for different mobile platforms.
Ha! Didn't get either one... The Java opening wanted immediate contribution, no learning curve...the other one, felt I would not fit into their fast-pased Agile Scrummy env. Oh well.
Just got bad news that my contract will be up due to budget cuts. But, I will have really great references... I'm just confused and tired. This is a new world where everything must be done yesterday and architecture...good coding is insignificant...I got it now.... Sorry, I'm on my pity party.
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.
Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
The Java opening wanted immediate contribution, no learning curve...the other one, felt I would not fit into their fast-pased Agile Scrummy env. Oh well. 
I'm just confused and tired. This is a new world where everything must be done yesterday and architecture...good coding is insignificant...I got it now.... Sorry, I'm on my pity party. 
