llothar wrote:
> Open your eyes man. This is not a speculative argument, i describe
> reality.
I don't deny that yours is certainly a legitimate reality.
Perhaps the number of copies of your editor sold does not
warrant supported copies of ISE's toolsets. Could that be right?
> Smaller business plans or just a secondary solution for smaller
> inhouse stuff
> and simple tools.
GPL Eiffel is not in the way of writing inhouse stuff. In case
inhouse stuff derived from GPLed Eiffel generates profit, then
likely sending some of the profit to ISE (or some GPL project?)
will be in order. At least this is what I think.
> Even larger companies have such requirements. And
> with this
> price tag you have to walk through one or two controller offices to
> get it approved.
I don't think that car makers, banks, insurance companies, hardware
designers etc. have much of a problem with licensing cost;
in a few cases I know there is no such problem. The argument is
obvious: Compare licensing cost to typical wages payed for this
kind of programming (ACID SQL, J2EE, non-junk hard read-time
controller software, ...).
If you imagine the yearly pay plus the cost of a workplace
then the mentioned $$$$ will not make much of a difference.
In fact, how much is VS PRO with MSDN *per* *year* and
seat? I understand this is the most widespread IDE used
when writing MS Windows software.
I'm mentioning hard real-time because there you hear the same
arguments about dead languages and then some. What you call
expensive (and a number of $$$$ tools *is* expensive for many
self-employed or semi-employed programmers) is a normal price
for compilers and tools when it comes to writing programs that
control the brakes of vehicles, robot arms, measurement
instruments and such.
> Without a larger community Eiffel has a hard time as libraries are
> today much more
> important then a nice language. Like it or not but that is the fact.
There is a need for scripting libraries if you want to replace
Python with Eiffel, say. But how are some missing libraries an
"insane thing"?
A lack of libraries is probably not a problem on .NET either,
because .NET is a type library. Eiffel and .NET are well
integrated, Eiffel# being among the first .NET languages,
not surprisingly.
If you look at libraries this way then using C# you won't
get libraries as well, assuming a Mac, say.
> Unbelievable that there are still people out there
> that are
> impossible to do a post mortem analysis.
From what I hear and see, ISE will be needed for years
to come. Now that William Gates is offering Windows using
humanitarian attitudes as a clever vehicle, supporting Eiffel
on .NET for non-glue programming work looks like one financially
viable business plan to me. Maybe this plan would be incompatible
with your business, and probably others' businesses.
Still, I don't see how this sad circumstance could kill Eiffel,
and its existing market.
|
