Karl Seguin

I saw before that they were looking to hire .net developers for non game related projects.  Maybe they couldn't find any good ones but found some java folks.

As far as performance, asp .net screams if you architect a proper solution.  Whenever I hear slow or buggy and .net it points to a development problem, not a framework problem.

I am quite a .Net fan, but I've seen these discussions before, and the thing that I keep coming back to is this.  Why do we end up with so many bad .Net architectures that require re-implementation?  Is it simply bad devs?  Or is it something about .Net that makes it too easy to do things badly (or too hard to do it right?)?  

I haven't done much Java or followed any discussions around it, so you may see the same things on the Java side (poor implementations being scrapped), which would mean that the cause is 99% bad devs.  If there isn't the same failure rate, though, what about .Net causes such poor implementation?

I guess it could be said that Microsoft marketing makes .Net seem so easy and great that PHBs see this, adopt the technology, and hire poor/incompetent devs to do their implementation.  It seems that things on the Java side are a bit more ... formalized.  Like there's more focus on the proper way of doing things.  PHBs drink the MS kool aid and think you can't fail with .Net, maybe.  They hire some schmo who grabs a bunch of CodeProject* and patch things together so they "work".  ("work" meaning things look good on the dev box but all hell breaks lose once the system gets pounded on for 10 minutes)

Thoughts?

(*Disclaimer: I use CodeProject all the time, and its a great resource for some things.  The code there must be taken with a grain of salt, though.)

In my experience, it's all about the devs. A lot (I'd say a huge majority) of people doing .NET are former developers in classic ASP or VB or Java. The rest are MFC/C++ developers who still pretty much do the same thing.

The learning curve for the classic ASP/VB guy is huge - especially if you are self-taught our out of school for a long time. You likely have no actual experience with OO. It *is* too easy to get something up and running in .NET (especially winforms and webforms), so they never even realize they are doing something wrong (what,I'm not supposed to be using on error resume next?!)

The Java guys have their own baggage - maybe they think of the database as a 2nd class citizen...maybe they are OO purists...whatever it is, they seem to have a much harder time transitioning to .NET then they ought to.

Personally I think you can trace this back to a much more fundamental problem in our industry. During the dotcom boom, a lot of people got into programming for the money. A LOT of people. These are people who don't love to program and can't appreciate code as something beautiful. They don't want to learn, it's hard for them to do so, and they don't grasp basic fundamentals.

I find it hard to blame MS for any of it.  VB.NET is too hard? Find another job, you're probably doing a crappy job of programming anyways. As for ASP.NET, that's a different story. A lot of websites out there don't need an enterprise package like .NET built on general purpose languages. All I can suggest for those sites is that they switch to PHP.

I'd posit that they may be simply moving to a more open source platform and that licensing might be a deterrent to some degree. If it was time for an overhaul for a badly designed and implemented system, then you can choose a proprietary system or open source (obviously not the only factors), and I think that Blizzard likes open source these days.

Really, Java and ASP.NET is the same thing when it comes down to it... both viable solutions to solve a problem.

Easter is on its way.To celebrate it ,there is a 7-day promotion .For any gold order,you can get extra 10%  for free ,it will expire on Feb 24(PST),never miss it!

If interested,please visit www.gamenoble.com