Comments on: IBM Websphere – officially better than anything, ever http://blog.softwhere.org/archives/409 Musings on the world of software from the sharp end of the long tail Mon, 15 Feb 2010 21:19:48 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: Rich Sharples’ Blog » Blog Archive » Websfear EPIC FAIL ! http://blog.softwhere.org/archives/409/comment-page-1#comment-3456 Rich Sharples’ Blog » Blog Archive » Websfear EPIC FAIL ! Mon, 15 Dec 2008 02:28:07 +0000 http://blog.softwhere.org/?p=409#comment-3456 [...] you’re probably already aware - I’m always ready to have a chuckle at IBM’s expense - I have nothing in particular against IBM but if you can’t take the piss out of mammoth [...] [...] you’re probably already aware – I’m always ready to have a chuckle at IBM’s expense – I have nothing in particular against IBM but if you can’t take the piss out of mammoth [...]

]]> By: Alex_G http://blog.softwhere.org/archives/409/comment-page-1#comment-3046 Alex_G Thu, 06 Nov 2008 09:37:34 +0000 http://blog.softwhere.org/?p=409#comment-3046 IBM best? Wow... That says something about the overall quality of application servers.... Seriosly, I'd rather have my dog chew of my penis than having to use WebSphere again... IBM best? Wow… That says something about the overall quality of application servers…. Seriosly, I’d rather have my dog chew of my penis than having to use WebSphere again…

]]> By: Adrian Woodhead http://blog.softwhere.org/archives/409/comment-page-1#comment-2994 Adrian Woodhead Tue, 14 Oct 2008 18:07:29 +0000 http://blog.softwhere.org/?p=409#comment-2994 I worked on a banking project for over 2 years where the applications were deployed to WAS 5. It was slow, it was clunky, it was a bitch to configure, was practically useless for developer use for testing (developers used JBoss locally and the integration tests were done against WAS). Having said all that, it was incredibly stable and in production it was up 24/7. Then we migrated to WAS 6 and I have to admit I was truly impressed. Startup times were reduced, speed increased, the user interface improved. It acually became usable for local testing and I switched from JBoss to it (it was still slower than JBoss but I thought it safer to run the tests against the final production environment). So I have to say that there *are* developers and customers who do like WAS, especially the latest version. I agree with your thoughts about Geronimo though, I haven't come across it being used in any company I've worked for or by anyone I know. I worked on a banking project for over 2 years where the applications were deployed to WAS 5. It was slow, it was clunky, it was a bitch to configure, was practically useless for developer use for testing (developers used JBoss locally and the integration tests were done against WAS). Having said all that, it was incredibly stable and in production it was up 24/7.

Then we migrated to WAS 6 and I have to admit I was truly impressed. Startup times were reduced, speed increased, the user interface improved. It acually became usable for local testing and I switched from JBoss to it (it was still slower than JBoss but I thought it safer to run the tests against the final production environment).

So I have to say that there *are* developers and customers who do like WAS, especially the latest version. I agree with your thoughts about Geronimo though, I haven’t come across it being used in any company I’ve worked for or by anyone I know.

]]> By: Blog Xebia France - Revue de Presse Xebia http://blog.softwhere.org/archives/409/comment-page-1#comment-2992 Blog Xebia France - Revue de Presse Xebia Mon, 13 Oct 2008 17:14:49 +0000 http://blog.softwhere.org/?p=409#comment-2992 [...] étude soulève déjà de nombreuses questions chez les concurrents (comme Rick Sharples, de JBoss), le marketing d’IBM n’allant pas se plaindre d’une si belle vitrine. Rick émet [...] [...] étude soulève déjà de nombreuses questions chez les concurrents (comme Rick Sharples, de JBoss), le marketing d’IBM n’allant pas se plaindre d’une si belle vitrine. Rick émet [...]

]]> By: Yellek http://blog.softwhere.org/archives/409/comment-page-1#comment-2988 Yellek Sun, 12 Oct 2008 22:10:25 +0000 http://blog.softwhere.org/?p=409#comment-2988 Having just done a paper based (i.e. we haven't actually talked to anyone yet) SOA software evaluation let me offer an SOA perspective on this. For environments where a drop in server is what the customer wants WebSphere looks extremely impressive. It ticks all the feature boxes. JBoss on the other hand has gaps in it's feature coverage as well as a lack of implementation partners (at least in the geography we are working in). Sure if you have a development organization and the budget to integrate various third party solutions yourself you can get there but unless all of the feature boxes get ticked JBoss isn't even going to get to the point where the developer experience can be expounded because it won't make the short list. Oracle and BEA, by the way, also have a great feature story. The problem with choosing them at the moment is that the turmoil surrounding their integration challenges means that there is significant risk of product instability over the next year or two which is unpalatable. Having just done a paper based (i.e. we haven’t actually talked to anyone yet) SOA software evaluation let me offer an SOA perspective on this. For environments where a drop in server is what the customer wants WebSphere looks extremely impressive. It ticks all the feature boxes. JBoss on the other hand has gaps in it’s feature coverage as well as a lack of implementation partners (at least in the geography we are working in). Sure if you have a development organization and the budget to integrate various third party solutions yourself you can get there but unless all of the feature boxes get ticked JBoss isn’t even going to get to the point where the developer experience can be expounded because it won’t make the short list. Oracle and BEA, by the way, also have a great feature story. The problem with choosing them at the moment is that the turmoil surrounding their integration challenges means that there is significant risk of product instability over the next year or two which is unpalatable.

]]> By: Jon Bettinger http://blog.softwhere.org/archives/409/comment-page-1#comment-2983 Jon Bettinger Sat, 11 Oct 2008 01:50:22 +0000 http://blog.softwhere.org/?p=409#comment-2983 Having used Weblogic 5-7 and Websphere 6 and 6.1 - I have to say I don't think Websphere is such a horrible product, but RAD 6 and 7 have the worst app server integration I have ever seen. For the life of me, I don't understand how I had better luck with Eclipse and Weblogic integration than I have with RAD and Websphere. Netbeans and Weblogic wasn't bad either, as I recall. Having used Weblogic 5-7 and Websphere 6 and 6.1 – I have to say I don’t think Websphere is such a horrible product, but RAD 6 and 7 have the worst app server integration I have ever seen. For the life of me, I don’t understand how I had better luck with Eclipse and Weblogic integration than I have with RAD and Websphere. Netbeans and Weblogic wasn’t bad either, as I recall.

]]> By: Kit Davies http://blog.softwhere.org/archives/409/comment-page-1#comment-2981 Kit Davies Fri, 10 Oct 2008 15:21:23 +0000 http://blog.softwhere.org/?p=409#comment-2981 Remember that for large enterprises, the cost of developing a business-critical J2EE app is completely dwarfed by a) the cost of provisioning and scaling it in a secure, reliable data center with 24/7 support and b) the cost to their business if it goes down. For that reason, they couldn't care less whether developers find WAS difficult to deal with. It stays up (v6+ at least), and there is plenty of WAS ops & support knowledge available from IBM themselves and others. That's all that matters to them. Remember that for large enterprises, the cost of developing a business-critical J2EE app is completely dwarfed by a) the cost of provisioning and scaling it in a secure, reliable data center with 24/7 support and b) the cost to their business if it goes down.

For that reason, they couldn’t care less whether developers find WAS difficult to deal with. It stays up (v6+ at least), and there is plenty of WAS ops & support knowledge available from IBM themselves and others. That’s all that matters to them.

]]> By: William Louth http://blog.softwhere.org/archives/409/comment-page-1#comment-2979 William Louth Thu, 09 Oct 2008 18:00:15 +0000 http://blog.softwhere.org/?p=409#comment-2979 Operations people tend to like products that do have at least a management console that is integrated and reliable with a distributed deployment/provisioning infrastructure. The IBM user experience has always been lacking from a developer perspective when it comes to their middleware and runtime products. William Operations people tend to like products that do have at least a management console that is integrated and reliable with a distributed deployment/provisioning infrastructure.

The IBM user experience has always been lacking from a developer perspective when it comes to their middleware and runtime products.

William

]]> By: sharps http://blog.softwhere.org/archives/409/comment-page-1#comment-2978 sharps Thu, 09 Oct 2008 12:58:53 +0000 http://blog.softwhere.org/?p=409#comment-2978 @Mike @Inquisitor : https://www.redhat.com/wapps/store/catalog.html 1-866-2REDHAT x45014 :) @Mike @Inquisitor :

https://www.redhat.com/wapps/store/catalog.html

1-866-2REDHAT x45014

:)

]]> By: Inquisitor Jax http://blog.softwhere.org/archives/409/comment-page-1#comment-2976 Inquisitor Jax Thu, 09 Oct 2008 07:07:27 +0000 http://blog.softwhere.org/?p=409#comment-2976 I have never met any developer who liked WebSphere - in fact most of them hated it. I worked for 2 years on the Java J2EE environment, and every few days the experienced Java developers kept trying to convince me that Java is not so bad because WebSphere was such a dud. I even wrote a blog post in the subject: http://inquisitorjax.blogspot.com/2007/08/random-thoughts-ibm-has-best-sales-team.html I have never met any developer who liked WebSphere – in fact most of them hated it. I worked for 2 years on the Java J2EE environment, and every few days the experienced Java developers kept trying to convince me that Java is not so bad because WebSphere was such a dud. I even wrote a blog post in the subject:
http://inquisitorjax.blogspot.com/2007/08/random-thoughts-ibm-has-best-sales-team.html

]]>