Enigmastation.com - Responses

Re: What I sort of look like

David Gross — Wed, 10 Dec 2008 00:45:52 GMT

Joe....you need to contact me....We are related!!!!

Re: What I sort of look like

David Gross — Sun, 07 Dec 2008 20:53:07 GMT

You look a lot like your DAD.....I do remember him.....

Re: What I sort of look like

Homestar — Fri, 26 Sep 2008 16:09:00 GMT

You look like yet another satisfied JBoss user Joe!

Re: What I sort of look like

alan — Thu, 25 Sep 2008 17:15:04 GMT

LOL absolutely wonderful - you have axe-murderer written all over your face there! sorry man.

Re: Spring changes its license structure

Joseph B. Ottinger — Wed, 24 Sep 2008 12:37:32 GMT

Actually, yes. And what Spring changed is not the license under which the Spring Framework exists; what they changed was the support and release strategy. There'll be a Q&A with Rod Johnson available soon that goes into some more detail.

Re: Spring changes its license structure

Anonymous — Tue, 23 Sep 2008 15:32:16 GMT

Did you even bother to read the announcement?! It says nothing about a change of the license. Well at least this blog post is consistent with the rest in this blog.

Re: Spring changes its license structure

Anonymous — Sun, 21 Sep 2008 16:22:18 GMT

How is this a licensing change? SpringSource has not changed the licensing of anything. The core Spring Framework and all the projects that were Apache Licensed are still Apache Licensed and will remain Apache licenses. All fixes going into Spring are still going into the open source source repository. All they are doing is stating pretty clearly when and how they will put out packaged distributions, both for the community, and for support customers. Contrast and compare this to your average open source project, where there is no guarantee of anything. I sat around for the better part of a year waiting from one minor Maven release to another for somebody involved with the project to fix a critical bug, and even after that much time nobody touched it. And at the end of the day, why should they? There was nobody involved with the project commercially that cared about the problem. I will take the Spring situation any day, where SpringSource has full time employees working on this stuff, and now has a clearly defined maintenance policy.

Re: I have seeeeeeen the light, brothers and sisters!

Joseph B. Ottinger — Tue, 16 Sep 2008 19:05:05 GMT

Thank goodness! :)

Re: I have seeeeeeen the light, brothers and sisters!

cheeser — Tue, 16 Sep 2008 18:38:08 GMT

If it's any consolation, despite the apparent revelation recorded here, I'll always think of you as dumb.

Re: Is Spring better than EJB?

Anonymous — Fri, 25 Jul 2008 18:13:26 GMT

what happened to the crawl Hall of Fame? it directed me here.

Re: Is Spring better than EJB?

Jason Carreira — Wed, 09 Jul 2008 16:45:31 GMT

Joe, I enjoyed talking to you about DomainProxy, but here you're totally off base. Completely. 100%. Off base.

You said in your last post " if you were silly enough to do everything on the same physical box".... But that's the right way to do it! That's what GigaSpaces SBA is all about! Keep everything as close as you can, limit network hops as much as possible, don't serialize and deserialize things, etc.

EJB's were the wrong solution to the wrong problem. Session beans basically made it easier to locate, manage, and wire up remote interfaces to your application.... Which almost no-one should be doing. What's the first rule of distributed computing? Don't do it! You shouldn't be incurring the cost of remote operations within one application. This was especially true in the era when EJB's were introduced: an era before SOA.

What people really wanted and needed, and Spring provided, was a way to organize, manage, and automatically wire up their application without all of the cruft of hard-wiring static references or using ugly service-locators. We needed a way to manage our components. Add to that the ability to add-on declarative services like transactions and security and you had everything EJB's were providing and more, with a lot less cost in terms of both the weight of the component model (no interface / implementation required, no extending certain interfaces, etc) and less cost of the runtime.

But none of that is really why EJB's failed. EJB's failed because of Entity Beans. They were such a misguided and poorly designed "feature" that they tarnished the whole EJB brand. By the time they brought Entity Beans up to 2/3rds of what Hibernate provided, with EJB3, the damage was done and the fight was over.

Re: Is Spring better than EJB?

David Sims — Wed, 02 Jul 2008 23:24:31 GMT

My main "concern" is that Spring is able to use this sort of self-serving sledgehammer to change the industry... and that they'll do it again.

Perhaps they will. However, if SpringSource does it poorly, they don't have the clout with clients to push adoption of their (potentially) poor implementation out to a significant number of users, like IBM does.

I know that some software stacks that IBM develops are, in my humble opinion, too complex to install and use. However, regardless of what I think personally, I still must use the IBM stack since I have users who use the IBM stack.

I just don't see the same thing happening with SpringSource on the same scale. I think if SpringSource put out a really poor implementation, their (relative) lack of clout would send the enterprise Java industry elsewhere.

Cheers,
David