Comments on: At This Point, I’d Prefer Java Developers Over .NET Developers

By: Java Developer

Java Developer — Thu, 10 May 2012 23:35:00 +0000

I have never interviewed .NET profiles before, though never had a lot of good experience with recent java screenings either.

Nice to know about your experience.

By: Stuart

Stuart — Fri, 10 Feb 2012 10:47:00 +0000

that is the future… I want to learn it asap, because I want a related job.

http://www.tatvasoft.co.uk/microsoft-dot-net-development.php

By: Technical Related Notes » Blog Archive » links for 2009-05-30

Technical Related Notes » Blog Archive » links for 2009-05-30 — Mon, 18 Apr 2011 09:41:55 +0000

[...] At This Point, I’d Prefer Java Developers Over .NET Developers | The Inquisitive Coder – Davy Brio… (tags: .net java programming) [...]

By: tomklaasen

tomklaasen — Sat, 19 Mar 2011 09:56:00 +0000

Nice points that you’re making.

There was a time when Java also had more than 5 IoC frameworks. When one had finally seen the value of IoC, his next dilemma was ‘which framework am I going to use?’

And then, one of them got it _just right_. All of a sudden, every Java developer had the same vocabulary. People working with IoC all referenced the Spring framework. Powers were combined, Spring has only grown from then on, it became the de-facto basis on which to build applications. As a result, every Java developer now knows about IoC.

Counterintuitively, having multiple options isn’t always an advantage.

By: Glenn Block

Glenn Block — Fri, 18 Feb 2011 06:37:00 +0000

May be you are just talking to the wrong people. There are plenty of folks in the .NET community that care about these things, plenty of folks practicing TDD, caring about separation of concerns, and yes using IoC containers and AOP to get there. There community of OSS solutions continually grows.

Case in point, Castle Windsor, one of the most popular IoC in .NET and which includes Castle Dynamic Proxy, YES an AOP framework. Over 1 million downloads.

patterns & practices: Unity, over 2 miliion downloads

As a matter of fact, compare to Java I’d argue the .NET world is actually AHEAD when it comes to IoC. The richness of IoC options across .NET dwarfs Java, here’s a few for you to look into in addition to Windsor and Unity: StructureMap, Autofac, Ninject, LinFu, Func, just a few.

Now let’s look at Mocking frameworks: We have about 5

xUnit type frameworks: At least 5

Refactoring tools: 3 or more.

MVVM Frameworks: More than you can count

ORM: More than you can count

I do agree that in general I have found more java developers aware of patterns, but the number of .net devs that care about these things has grown dramatically over the past few years. The numbers are not insignificant.

Glenn

By: Wayne Molina

Wayne Molina — Mon, 03 Jan 2011 22:55:22 +0000

Spot on. The problem is there are too many “Mort” developers in .NET who don’t care to learn proper software development but hack shit together without a care. If there were Java jobs in my area I would have made the switch long ago but I live in a city domianted by .NET to the tune of, basically, 99:1 so I have little choice but to use .NET, and sadly 99% of the companies I’ve worked at don’t understand basic software principles but think WebForms+CodeBehind+Typed DataSets is the way to go with app development even through the modern day. Try mentioning something like ASP.NET MVC to them and you get blank stares. Mention a mature ORM or the SOLID principles or Testing (not even TDD, I mean Unit Tests in general!) and you get a look and a response of “We don’t use here”

By: Dr. Archi

Dr. Archi — Tue, 28 Dec 2010 15:52:14 +0000

I fully agree with this article. The lack of good design practices in the .Net community have let me decide to move, after 7 years, from .Net to Java, since I like design, not drag and drop.

By: amit rawat

amit rawat — Tue, 21 Dec 2010 12:57:43 +0000

it’s true .net takes less time to build application and java more.but after building applications in java its easy to maintain Ur application if u are using good design architecture…

By: amit rawat

amit rawat — Tue, 21 Dec 2010 12:52:19 +0000

i am even hardly 5 month exp but i know very well IOC,DI,AOP etc.

By: taso

taso — Fri, 12 Nov 2010 21:45:30 +0000

On the flip side of this, a junior developer can get up to speed and start building powerful .NET applications far more quickly than Java. Whether through complex architecture or simple prototypes, all that matters is getting a product out quickly in many cases. If your team consists of junior developers, they will be able to implement far more sophisticated functionality using .NET than a team made up of only junior Java developers.

By: Cvecara Beograd

Cvecara Beograd — Wed, 14 Jul 2010 13:25:22 +0000

- Java develops way of thinking
- Java is not so comfort as .Net
- Java have started with all story about patterns end enterprise software little earlier

So, at the end, who was involved in Java, can fast accept and better use .Net then ones with only .Net knowledge

By: tcmaster

tcmaster — Wed, 14 Jul 2010 08:04:50 +0000

I’d say from some of the comments, I can see why your statements stands.

By: Depois eu leio » Rails Summit 2009

Depois eu leio » Rails Summit 2009 — Sun, 30 May 2010 17:52:14 +0000

[...] o Hibernate e o Spring, IDEs diversas, e principalmente, uma grande base de desenvolvedores que sabem o que estão [...]

By: sp

sp — Wed, 10 Mar 2010 22:49:45 +0000

Davy, you are right, Java developers know more about design as that’s part of how the Java world is, its mostly used in big corporations where interoperability is important and applications seem to span across the enterprise, so naturally Java developers learn these. .NET on the other hand isn’t used as much on enterprise applications and hence the lack of awareness.

On the other hand, .NET developers are more aware of speed, memory, threading, synchronization, networking etc. as they write more desktop applications. If you ask a Java developer about Threading or Networking, they’d probably know very little as they don’t deal with it often.

So in the end, your knowledge is oriented towards your needs and experiences you go through.

I have programmed in both Java and .NET and the main difference I see is in .NET you can program at all levels from pointers to IOC, DI or any acronym you throw, but can’t with Java. And there is a misconception that coupling is outright bad. Sometimes coupling/tight integration is good if the involved systems are all of the same platform.

By: Spring Persistence with Hibernate - The Developer Day

Spring Persistence with Hibernate - The Developer Day — Wed, 17 Feb 2010 01:06:02 +0000

[...] Not surprisingly lot’s of innovation comes from the Java world. I believe it is because Java developers know a lot more about proper design principles and coding practices than an average developer of let’s say [...]

By: sharmabhabho

sharmabhabho — Thu, 11 Feb 2010 06:57:38 +0000

Quite an interesting post. I am a Java developer and i am very eager to create some new, innovative application some day.Waiting to see what happens at the Sun Tech Days 2010 conference in Hyderabad. Experts are going to share ideas on new technologies there. lets see what happens.

By: Paul Thiel

Paul Thiel — Thu, 03 Dec 2009 02:47:41 +0000

Could there be a reason you had 4 Java developers looking for a job and 1 .Net developer looking for work?

Over my career, I’ve been everything from help desk to network admin to developer to CIO. I have done contract work in both Java and .Net. I have seen outstanding and horrific development in both.

I find .Net developers are (in general) more interested in solving business problems (and making money) than building technical towers.

In times of recession, this matters more than knowing 1001 design patterns.

By: fakeslikeUs

fakeslikeUs — Sun, 29 Nov 2009 02:05:35 +0000

Has anyone on this blog worked at one place for 3 years or more. Yet we call ourselves Programmer Architect. Hmm, wonder what that means. Thanks

By: yougotit

yougotit — Fri, 27 Nov 2009 15:22:49 +0000

“IOC and AOP are wonderful new guns to shoot yourself in the foot with. They are the antithesis of KISS, and introduce new and exciting ways to make your program incomprehensible and buggy.”

You’re 100% right.

Any “interviewer” who asked me about AoP would get my reply “AoP is almost always a bad idea”.

If he’s running things at the company, you can be sure they’re spending gobs of ca$h getting nowhere fast.

By: Goh

Goh — Thu, 05 Nov 2009 11:23:54 +0000

I am .Net developer and used to work in a java-based company. I heard a lot of complain about microsoft and .net everyday from java developers. I think sometime they just too bias. What we really need is an application which really work regardless of what design pattern we are using. I left the java based company after a year and developed my own application (similar solution) which is running fully in ASP.Net. Now I have more than thousands companies using my application in a single server. My ex-company? still struggling on how to process the transactions faster. The fact is, my application is developed by my friend (now my partner) and I, and my ex-company application is developed with more than 10 java developers and 1 of them already have 13 years experience in java. I had proven .net can be better than java and it really depends on how you design the system. Bear in mind, i am just a 2 years experience .net developer that time and i know very little about the design concept as mentioned by Brion.