×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 19 Jun 2013 10:09, Nathan Andelin wrote:
<<SNIP>> I don't think it's a question of profitability in this case,
but rather a question of whether whether IBM might be willing to
support both thin (PDM/SEU) and THICK (Rational Developer) interfaces
on the platform.
Your are correct. Profitability is not an issue with regard to
getting additional capabilities in SEU. The issue is considered to be
cost recovery.
My point is that IBM is in effect no longer spending money on SEU, so
any income from the revenue-generating LPP that provides SEU, now goes
directly into funding whatever else they are developing [which is not
SEU]. Thus if someone wants money spent on SEU, then that someone will
have to pay for it; i.e. to finance developer(s) working under a
contract that will justify their employment while providing that change
to SEU instead of providing some other revenue-producing feature, or to
finance developer(s) working to provide a PRPQ for which there is a
presumption that the first sale plus future sales will recoup their
salaried development time. The development time would include both
adding the capabilities and design\develop of the deployment mechanism.
But then there is the additional costs of effective packaging and
delivery, because the code is no longer being delivered within the base
option(s) of the LPP and the associated licensing; under something like
Lab Services, the enhancement could be a bullet-point on a chart of what
is available, and the effective S&H could end up being the
consulting\contracting fees for the IBM consultant to install the
feature beyond whatever else they are providing under the contract.
I put my money on thin interfaces. But if IBM forces
us to the latter,
I thought that direction was already made clear... if only by the
noted freezing of the level of syntax-checking support for SEU.
I'm not going to kick and scream about it.
Little use in pining for it [here] either. The only way to get the
capability is to ask IBM. However as I alluded, I am confident that the
only way to get the function will require a willingness to pay extra, to
directly fund the enhancements.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.