Wednesday, February 01, 2006
Spring vs. J2EE? Does Spring really suck ? - Let Google decide !!
When faced with a tough business-, architectural- or design decision, why listen to Gartner, Jupiter or any so called analysis company? The solution is as always free, and readily available.
When choosing a middleware or framework, it is crucial that there is a critical mass of users out there, finding & fixing bugs, blogging, producing tutorials etc. This is especially important with open source!
So! One could easily argue that the maturity and quality of a product can be related to the number of people that are currently building software with it. (aka People are not stupid!) One could also easily assume that the more people that are involved with a product, the larger internet footprint as more web pages are produced!
So, let's think. Who is currently number #1 at measuring this? Google is at least a good candidate. I'm therefore introducing a new measuring unit called IGP (Indexed Google pages)
Publicity and published pages and number of pages is not always positive. So let's add another factor to the equation, and introduce yet another TBF called NGP or Negative-Indexed Google pages. The NPG is a measure of how many indexed pages Google has, with the product name in the proximity of a negative word.
First, i tried one of there more obscene curse words I know, with let's say "Interesting results". I ended up using "headache" instead since it produces less explicit results, and bad frameworks often gives us developers a lot of headaches.
Now... Let's put this methodology through the test. Let us put J2EE and the Spring framework Head-to-head!
Since "Spring" is a fairly general word, I am bold enough to state that pages related to the spring framework should contain both the word "Spring" and "Java". I believe this is a reasonable assumption.
Looking closer at the table, we can easily conclude that the J2EE framework is far more mature and holds a level of quality (A factor of 10!) superior to the Spring framework! J2EE has both a higher IGP and lower NGP ratio than Spring. I guess CrazyBob was right after all!
Feel free to use this methodology to put other technologies head to head, and please blog the results! ¶ 6:32 AM
When choosing a middleware or framework, it is crucial that there is a critical mass of users out there, finding & fixing bugs, blogging, producing tutorials etc. This is especially important with open source!
So! One could easily argue that the maturity and quality of a product can be related to the number of people that are currently building software with it. (aka People are not stupid!) One could also easily assume that the more people that are involved with a product, the larger internet footprint as more web pages are produced!
So, let's think. Who is currently number #1 at measuring this? Google is at least a good candidate. I'm therefore introducing a new measuring unit called IGP (Indexed Google pages)
Publicity and published pages and number of pages is not always positive. So let's add another factor to the equation, and introduce yet another TBF called NGP or Negative-Indexed Google pages. The NPG is a measure of how many indexed pages Google has, with the product name in the proximity of a negative word.
First, i tried one of there more obscene curse words I know, with let's say "Interesting results". I ended up using "headache" instead since it produces less explicit results, and bad frameworks often gives us developers a lot of headaches.
Now... Let's put this methodology through the test. Let us put J2EE and the Spring framework Head-to-head!
Since "Spring" is a fairly general word, I am bold enough to state that pages related to the spring framework should contain both the word "Spring" and "Java". I believe this is a reasonable assumption.
| Words and Technologies | IGP | NGP | Ratio |
| J2EE + (headache) | 24,900,000 | 58,400 | 0,0024 |
| Spring Java + (headache) | 9,740,000 | 208 000 | 0,021 |
Looking closer at the table, we can easily conclude that the J2EE framework is far more mature and holds a level of quality (A factor of 10!) superior to the Spring framework! J2EE has both a higher IGP and lower NGP ratio than Spring. I guess CrazyBob was right after all!
Feel free to use this methodology to put other technologies head to head, and please blog the results! ¶ 6:32 AM
Comments:
<< Home
I'm not sure if the methodology is right, but I used it to compare Struts, JSF and WebWork.
Here's the result:
IGP NGP Ratio
Struts + (problem) 7,870,000 1,860,000 0.236340534
JSF + (problem) 2,960,000 543,000 0.183445946
WebWork + (problem) 2,150,000 316,000 0.146976744
Struts + (headache) 7,870,000 61,700 0.007839898
JSF + (headache) 2,960,000 30,000 0.010135135
WebWork + (headache) 2,150,000 730 0.000339535
Here's the result:
IGP NGP Ratio
Struts + (problem) 7,870,000 1,860,000 0.236340534
JSF + (problem) 2,960,000 543,000 0.183445946
WebWork + (problem) 2,150,000 316,000 0.146976744
Struts + (headache) 7,870,000 61,700 0.007839898
JSF + (headache) 2,960,000 30,000 0.010135135
WebWork + (headache) 2,150,000 730 0.000339535
So now all you need is a site like GoogleFight (http://www.googlefight.com) to get these results.
# posted by 
: 5:18 PM
: 5:18 PM
This type of comparison would need to be able to exclude pages that have "we had no problem with..." from "our problem with...". The first is a positive review, the second is negative. Also, the fact that everyone is doing it may indicate successful marketing, not high quality. Take STP auto treatment, whose stock plunged when it was revealed that it was useless and may invalidate some warranties.
Post a Comment
# posted by : 8:24 AM
: 8:24 AM<< Home
