We don't know. And thats a bit dangerous. We were not present in the meetings of the IBM management. You seem to believe that its obvious fact that they decided the way they did, to leave customers Websphere as the only J2EE choice. But maybe there were other reasons. As far as I do rememember they said, that they feared to not be able to cope with the fast release cycles of apache software foundation. And honestly if you really liked Java/J2EE programming, you could have done so. There are quite a few Domino programmers who do so without thinking much about Garnet.
Your Garnet theories reminds me on critical rationalism, cause you base your whole argumentation on a statement non falsifiable.
Henning: That Garnet desicion was to pressure Domino organisation to use Websphere.
IBM manager: It was not.
Henning: It was.
IBM Manager: It was not.
Henning: It was.
IBM Manager: It was not.
The whole thing depends on the task you want to archieve. That's why those language discussions are so funny. The current project I am participating is not a small one. More than 5 developers are adding code on a daily basis. Version control systems come in handy in such situations, especially because we support different releases rolled out in some customer organizations.
My part is kind of providing tools for code generation. The application the customer uses includes complex XForm stuff. My tools help the domain experts (non programmers who are not interested in xml as such) to build those artefacts which define the application. They just document their application in an Excel spreadsheet and this generates big part of the application. You could code it in Domino6 upwards, but its far easier in Java. I truly believe that the many bonus bells-and-whistle apis for xml handling in Java, better OO features, junit, eclipse as tool, eclipse as platform for users, etc. do provide me pragmatic support.
If you build a standard-like Webapp PHP can be a good tool. Or Ruby on Rails.
Notes is for other tasks.
But its getting a bit funny to say: "I am realistic. I concentrate on the real stuff. I am a Domino programmer. The others are crazy zealots, which search for the shiniest newest drug, whereas I do the real work. Domino provides me Workflows."
It could have been the specific situation of some people in certain organisation in some period of time. But all this changes over time and in place. Today I find myself explaining my java programming coworkers some things in Domino. Should they become Domino programmers?
For all those tasks there are frameworks in other programming languages as well. Hani Suleiman has build an openSource package called OSWorkflow. Or JBoss has a project. .NET has huge workflow parts in the Vista release.
Henning: Political desicion?
We don't know. And thats a bit dangerous. We were not present in the meetings of the IBM management. You seem to believe that its obvious fact that they decided the way they did, to leave customers Websphere as the only J2EE choice. But maybe there were other reasons. As far as I do rememember they said, that they feared to not be able to cope with the fast release cycles of apache software foundation. And honestly if you really liked Java/J2EE programming, you could have done so. There are quite a few Domino programmers who do so without thinking much about Garnet.
Your Garnet theories reminds me on critical rationalism, cause you base your whole argumentation on a statement non falsifiable.
Henning: That Garnet desicion was to pressure Domino organisation to use Websphere.
IBM manager: It was not.
Henning: It was.
IBM Manager: It was not.
Henning: It was.
IBM Manager: It was not.
The whole thing depends on the task you want to archieve. That's why those language discussions are so funny. The current project I am participating is not a small one. More than 5 developers are adding code on a daily basis. Version control systems come in handy in such situations, especially because we support different releases rolled out in some customer organizations.
My part is kind of providing tools for code generation. The application the customer uses includes complex XForm stuff. My tools help the domain experts (non programmers who are not interested in xml as such) to build those artefacts which define the application. They just document their application in an Excel spreadsheet and this generates big part of the application. You could code it in Domino6 upwards, but its far easier in Java. I truly believe that the many bonus bells-and-whistle apis for xml handling in Java, better OO features, junit, eclipse as tool, eclipse as platform for users, etc. do provide me pragmatic support.
If you build a standard-like Webapp PHP can be a good tool. Or Ruby on Rails.
Notes is for other tasks.
But its getting a bit funny to say: "I am realistic. I concentrate on the real stuff. I am a Domino programmer. The others are crazy zealots, which search for the shiniest newest drug, whereas I do the real work. Domino provides me Workflows."
It could have been the specific situation of some people in certain organisation in some period of time. But all this changes over time and in place. Today I find myself explaining my java programming coworkers some things in Domino. Should they become Domino programmers?
For all those tasks there are frameworks in other programming languages as well. Hani Suleiman has build an openSource package called OSWorkflow. Or JBoss has a project. .NET has huge workflow parts in the Vista release.