Comments on: Red Hat Reacts to SpringSource's Leadership http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/ The voice of SpringSource Wed, 08 Feb 2012 17:31:53 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: VMware and Red Hat: The war for the data center | 云生活/Life In Cloud Computing http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-2/#comment-172566 VMware and Red Hat: The war for the data center | 云生活/Life In Cloud Computing Mon, 10 May 2010 06:59:44 +0000 http://blog.springsource.com/?p=2168#comment-172566 [...] help that SpringSource sees itself as the heir apparent to JBoss in the middleware market and has aggressively marketed itself against JBoss for [...] [...] help that SpringSource sees itself as the heir apparent to JBoss in the middleware market and has aggressively marketed itself against JBoss for [...]

]]> By: Tech Reviews » VMware and Red Hat: The war for the data center http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-172509 Tech Reviews » VMware and Red Hat: The war for the data center Thu, 06 May 2010 17:08:36 +0000 http://blog.springsource.com/?p=2168#comment-172509 [...] help that SpringSource sees itself as the heir apparent to JBoss in the middleware market and has aggressively marketed itself against JBoss for [...] [...] help that SpringSource sees itself as the heir apparent to JBoss in the middleware market and has aggressively marketed itself against JBoss for [...]

]]> By: Jim McLean http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-169226 Jim McLean Fri, 30 Oct 2009 15:36:02 +0000 http://blog.springsource.com/?p=2168#comment-169226 Don't feed the trolls. Don't feed the trolls.

]]> By: Oleg Zhurakousky http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-169225 Oleg Zhurakousky Fri, 30 Oct 2009 15:31:15 +0000 http://blog.springsource.com/?p=2168#comment-169225 @A.J. Segal What is a standard? Hmm... let me look: http://www.thefreedictionary.com/standard 1. "Something, such as a practice or a product, that is widely recognized or employed, especially because of its excellence" 2. " Widely recognized or employed as a model of authority or excellence" 3. "Commonly used or supplied" http://www.merriam-webster.com/dictionary/standard 1. "something established by authority, custom, or general consent as a model or example" http://www.wordreference.com/definition/standard 1. "a basis for comparison; a reference point against which other things can be evaluated" You can clearly see that the words used are: excellence, commonly used, model or example etc. . ., which perfectly fits Spring manifesto ;) The fact that it was so widely adopted by the community as a more superior programming model then J2EE is a perfect testament to that, and because it is so widely adapted by the true community makes it a defacto standard ;) And btw, JCP is not about standards. It is a process that attempts to dictate how things should be done and is heavily influenced by 800 gorillas (to promote their agenda and products) and not the community. @A.J. Segal

What is a standard? Hmm… let me look:
http://www.thefreedictionary.com/standard
1. "Something, such as a practice or a product, that is widely recognized or employed, especially because of its excellence"
2. " Widely recognized or employed as a model of authority or excellence"
3. "Commonly used or supplied"
http://www.merriam-webster.com/dictionary/standard
1. "something established by authority, custom, or general consent as a model or example"
http://www.wordreference.com/definition/standard
1. "a basis for comparison; a reference point against which other things can be evaluated"

You can clearly see that the words used are: excellence, commonly used, model or example etc. . ., which perfectly fits Spring manifesto ;) The fact that it was so widely adopted by the community as a more superior programming model then J2EE is a perfect testament to that, and because it is so widely adapted by the true community makes it a defacto standard ;)
And btw, JCP is not about standards. It is a process that attempts to dictate how things should be done and is heavily influenced by 800 gorillas (to promote their agenda and products) and not the community.

]]> By: A.J. Segal http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-169199 A.J. Segal Thu, 29 Oct 2009 20:31:00 +0000 http://blog.springsource.com/?p=2168#comment-169199 @Rod I'll take standards any day. Seam rules ... no JBoss AS required. Nice hair cut by the way. @Rod

I'll take standards any day. Seam rules … no JBoss AS required. Nice hair cut by the way.

]]> By: 商业趋势 - JBossã€?Spring Framework å’Œ eXo - Technology http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-167357 商业趋势 - JBossã€?Spring Framework å’Œ eXo - Technology Mon, 22 Jun 2009 13:00:55 +0000 http://blog.springsource.com/?p=2168#comment-167357 [...] Framework 的支æŒ?。å?¦è¯·å?‚è§? Press Releaseã€?Rich's note å’Œæ?¥è‡ª The Register 与 Rod Johnson çš„å??应；对于历å?²/更广阔的背景，请回溯 Oracle and [...]

]]> By: Tendências de Negócios - JBoss, Spring Framework, e eXo - Technology http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-167342 Tendências de Negócios - JBoss, Spring Framework, e eXo - Technology Fri, 19 Jun 2009 03:00:54 +0000 http://blog.springsource.com/?p=2168#comment-167342 [...] o Spring Framework. Veja também o Press Release, Rich’s note, e reações do The Register e Rod Johnson; e, para fins históricos / contexto mais amplo, recorde se da Oracle e [...] [...] o Spring Framework. Veja também o Press Release, Rich's note, e reações do The Register e Rod Johnson; e, para fins históricos / contexto mais amplo, recorde se da Oracle e [...]

]]> By: ビジãƒ?ストレンド - JBoss, Spring Framework, eXo - Technology http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-167316 ビジãƒ?ストレンド - JBoss, Spring Framework, eXo - Technology Wed, 17 Jun 2009 08:00:25 +0000 http://blog.springsource.com/?p=2168#comment-167316 [...] ã€? Rich ã?®è¨˜äº‹ã€?The Register ã?¨ Rod Johnson ã?®å??応もã?”確èª?を。歴å?²çš„/広ã?„文脈ã?§ã?¯ã€?Oracle ã?¨ Spring [...]

]]> By: Business Trends - JBoss, Spring Framework, and eXo - Technology http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-167300 Business Trends - JBoss, Spring Framework, and eXo - Technology Mon, 15 Jun 2009 11:01:14 +0000 http://blog.springsource.com/?p=2168#comment-167300 [...] Framework. Also see the Press Release, Rich’s note, and reactions from The Register and Rod Johnson; and, for historical/wider context, recall Oracle and [...] [...] Framework. Also see the Press Release, Rich's note, and reactions from The Register and Rod Johnson; and, for historical/wider context, recall Oracle and [...]

]]> By: Guy Pardon http://blog.springsource.org/2009/06/03/red-hat-reacts-to-springsources-leadership/comment-page-1/#comment-167292 Guy Pardon Sat, 13 Jun 2009 10:46:15 +0000 http://blog.springsource.com/?p=2168#comment-167292 "That license is the standard boilerplate evaluation license that the JCP requires for JSRs." This one seemed different IMO: I have seen numerous Sun licenses but none with Red Hat in it. That is why I didn't proceed (yet) - I like to know what I agree to first, and I just need some time to look into the legal terms first. "Clearly you have some misconceptions about JSR-299, that arise from you not having read the spec." It certainly seems so, doesn't it? However, and again: whatever little I know is based on the abstract that is right there, on the JSR page - maybe it could be improved so that it reflects the nature of the spec? "That license is the standard boilerplate evaluation license that the JCP requires for JSRs."

This one seemed different IMO: I have seen numerous Sun licenses but none with Red Hat in it. That is why I didn't proceed (yet) – I like to know what I agree to first, and I just need some time to look into the legal terms first.

"Clearly you have some misconceptions about JSR-299, that arise from you not having read the spec."

It certainly seems so, doesn't it? However, and again: whatever little I know is based on the abstract that is right there, on the JSR page – maybe it could be improved so that it reflects the nature of the spec?

]]>