Comments on: C# vs Java Part 2: The Platforms (Web)

By: Ivalene

Ivalene — Wed, 14 Dec 2011 21:49:25 +0000

That’s a smart way of thninkig about it.

By: Asad Ali Butt

Asad Ali Butt — Wed, 17 Mar 2010 22:14:31 +0000

My very first job as a java developer was to retractor some application, just because the developers behind open source framework for the old app had scrapped it along time ago. I always wondered, what if the the developers for current framework repeat this ?

are we going to invest and develop a new version for the our Application from scratch !! very sad.

By: Asad Ali Butt

Asad Ali Butt — Wed, 17 Mar 2010 22:13:21 +0000

are we going to invest and develop a new version for the our Application from scratch !! very sad.

By: C# vs Java Part 4: The Tools (Final) « Making the Complex Simple

C# vs Java Part 4: The Tools (Final) « Making the Complex Simple — Fri, 19 Feb 2010 21:59:25 +0000

[...] C# vs Java Part 2: Platforms [...]

By: C# vs Java Part 3: The Frameworks (Network, Reflection, Security, Text) « Making the Complex Simple

Fri, 12 Feb 2010 19:08:52 +0000

[...] C# vs Java Part 2: Platforms [...]

By: C# vs Java Part 2: The Platforms (Desktop and Mobile) « Making the Complex Simple

Mon, 08 Feb 2010 08:02:18 +0000

[...] C# vs Java Part 2: The Platforms (Web) [...]

By: jsonmez

jsonmez — Fri, 05 Feb 2010 14:37:46 +0000

Good point. I have also had some of the best code end up not making it to production, and some of the worst ending up being used way more than I would expect.

I guess my main point here is that when you have many choices off a main branch to choose from, it is more likely that the 1 or 2 your pick will end up dying off, but if you have few choices off a main branch, you are less likely to see that happen.

But definitely I agree with you. A developer should be well versed in several technology choices.

By: Joe

Joe — Fri, 05 Feb 2010 14:34:13 +0000

“One consideration as a developer is specialization. It is not possible to be an expert in every single web platform or framework. If you going the Java route, you’d better pick carefully, because the nature of open source development leads to many dead projects. A considerable investment in learning could be lost.”

This could lead into a discussion about the paradox of choice and how do you go about evaluating the technologies you want to specialize in. There are no guarantees with whatever you choose. Some great technologies have been largely ignored over the years while lesser ones seem to never die.

I heard someone the other day (think it was on the Herding Code podcast) say the best code he ever wrote never made it to production due to business decisions outside of his control. The worst code he ever wrote … is still running today years later.

I think the same could be said for platforms/languages in many cases. Whatever your technology darling is today, it could be an outcast tomorrow. How do you choose wisely?

I think one approach is to specialize in two or three technologies and not just a single one. It’s unrealistic to specialize in 10 different things but I think most developers should be able to handle 2 or 3. Unfortunately, in the .NET space, the majority of the developers I know have tunnel vision and only know one thing.