.NET Making Gains Against Java, Survey Says

by Stephen Swoyer
30 September 2008

Who’s ahead: Microsoft Corp.’s .NET or Sun Microsystems Inc.’s Java Platform Enterprise Edition (Java EE)?

Five years in and counting, the battle still rages with no clear victor. However, according to a new survey, .NET appears to be widening its lead over Java EE, as the latest revision of the erstwhile Java 2 Enterprise Edition (J2EE) specification is now called. Given the volatility of the .NET/Java EE match-up, that could easily change.

Last year, for example, a survey from development consultancy Evans Data Corp. identified a clear trend in favor of Java development, even though .NET still retained a narrow lead. Thirty-one percent of developers said they planned to tap .NET as their platform of choice for SOA development; 28 percent cited Java.

Evans Data flagged a steep decline in the percentage of developers who expressed a preference for using .NET as a platform for their SOA activities, citing a 20 percent drop in just a six-month period.

This year, the reverse seems to be the case.

According to a new survey from Evans Data, .NET is once again outpacing Java. The survey, which polled 350 developers at enterprise shops with 1,000 or more employees, found that three-fifths (60 percent) of respondents indicated that their .NET investments were growing; fully half said they planned to add additional .NET development personnel.

“These survey results confirm that .NET applications are pervasive in large enterprises and their acceptance and dependability is continuing to increase,” said Mike Allen, director of product management for CA Wily Technology, in a statement. CA Inc. — which markets application performance management (APM) tooling (and which claims that the Evans Data results underscore the importance of effective APM programs) — is a sponsor of the survey.

There might be something to CA’s claims. What’s surprising is how much enterprise IT organizations are spending on their next-gen application architecture investments — particularly for .NET products. More than half of respondents said they’re spending about a quarter of their IT application budgets on .NET development or support, while a staggering one-fifth of respondents say they’re spending between 75 and 100 percent this way.

Also surprising is the non-partisan heterogeneity of today’s enterprise application architectures. Many shops are supporting mixed .NET and Java EE deployments, Evans Data said. A clear majority of respondents said their organizations maintain both .NET and Java groups, for example.

It’s a sign of the times, according to industry veteran Jasmine Noel, a principal with consultancy Ptak, Noel & Associates.

“An increasing number of enterprises are realizing the benefits of deploying applications built on both .NET and Java. However, with those benefits come the challenges of managing a heterogeneous environment coupled with the unique issues of both development architectures,” Noel said in a prepared statement.

Elsewhere, .NET developers are far more likely than Java coders to blame changes — at both the application level and in the back-end — for slowdowns. Java users, on the other hand, disproportionately cite memory leaks and out-of-memory conditions as triggers for application failure.

.NET users were also more likely to cite issues with connectivity to back-end transaction systems, including mainframe systems. Java users, conversely, seem to generate or encounter more bugs. They’re also more likely to find fault with JVM or architecture issues than are .NET users (with the .NET CLR, that is).
You can contact the editors about .NET Making Gains Against Java, Survey Says at editor@reddevnews.com.

Javascript学习笔记–类的继承

最近在看天雪发给我看的一本Javascript的书,是JQuery之父写的,写得很棒,里面推荐的资源也很棒。为了弥补我的差记性,特写下学习笔记。

http://javascript.crockford.com/inheritance.html
这个是讲Js里面的类继承的写法,这个作者太犯贱了,上面的例子都是用自己写的方法,结果方法在最下面才写出来,告诉我们。搞得我一开始以为是内置的方法呢。。。不过他的方法写得太酷了,下面列举一下:

Sugar(作者管他写的方法叫做糖,确实很甜)

To make the examples above work, I wrote four sugar methods. First, the method method, which adds an instance method to a class.
为了上面的例子跑起来,我写了四个很甜的方法。首先,是method方法,它是用来把方法添加到class里的。

This adds a public method to the Function.prototype, so all functions get it by Class Augmentation. It takes a name and a function, and adds them to a function’s prototype object.

It returns this. When I write a method that doesn’t need to return a value, I usually have it return this. It allows for a cascade-style of programming.

Next comes the inherits method, which indicates that one class inherits from another. It should be called after both classes are defined, but before the inheriting class’s methods are added.

Again, we augment Function. We make an instance of the parent class and use it as the new prototype. We also correct the constructor field, and we add the uber method to the prototype as well.

The uber method looks for the named method in its own prototype. This is the function to invoke in the case of Parasitic Inheritance or Object Augmentation. If we are doing Classical Inheritance, then we need to find the function in the parent‘s prototype. The return statement uses the function’s apply method to invoke the function, explicitly setting this and passing an array of parameters. The parameters (if any) are obtained from the arguments array. Unfortunately, the arguments array is not a true array, so we have to use apply again to invoke the array slice method.

Finally, the swiss method.

The swiss method loops through the arguments. For each name, it copies a member from the parent‘s prototype to the new class’s prototype.

才翻译了一个,发现懒得翻译了。。。实在是个懒人啊。。。大家将就着看,我什么时候想到了再来翻译一下好了,其实都是很简单的英语。

开博第一帖

本来在csdn和blogger都有博客的,但终究不是自己的地方,感觉不爽。
现在转移到自己的虚拟主机上,感觉很好,有一种家的感觉,为所欲为的快感。